Received: from eggs.gnu.org ([2001:4830:134:3::10]:37337) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z57XG-0003Ad-Jo for qemu-devel@nongnu.org; Wed, 17 Jun 2015 03:13:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z56ty-00025i-3w for qemu-devel@nongnu.org; Wed, 17 Jun 2015 02:33:52 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49298) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z56tx-00025S-Rh for qemu-devel@nongnu.org; Wed, 17 Jun 2015 02:32:45 -0400 From: Markus Armbruster References: Date: Wed, 17 Jun 2015 08:32:42 +0200 In-Reply-To: (Peter Crosthwaite's message of "Sun, 24 May 2015 14:20:39 -0700") Message-ID: <87ioamj14l.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PATCH v2 0/2] monitor+disas: Remove uses of ENV_GET_CPU List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Crosthwaite Cc: rth@twiddle.net, lcapitulino@redhat.com, qemu-devel@nongnu.org, afaerber@suse.de, Peter Crosthwaite Peter Crosthwaite writes: > Neither the monitor or disassembly core has a good reason to navigate from an > env pointer to a cpu pointer. Disas should not need env awarness at all, that > is removed in P2. > > The monitor is trickier, the env is still needed by some #ifdef switched target > specific code but all common code only needs to trade in CPU pointers. As the > monitor always has access to a CPU pointer naturally, remove ENV_GET_CPU usages > (P1). > > This is related to my multi-arch work, where the goal is to minimise use of > architecture defined global definitions, ENV_GET_CPU being a major headache in > that whole effort. The longer term goal is to limit ENV_GET_CPU use to genuinely > architecture specific code. > > But I think these two patches stand in their own right, so sending ahead of the > motherload series. This brings both modules closer to common-oby-y'ification. > > First RFC for multi arch is avaiable here: > > https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg01771.html > > The two patches are done together to avoid a conflict with monitor_disas which > is touched by both patches. If one patch gets acked, the other nacked then > either can be merged independently with trivial edits. Applied to my (badly named) qapi-next branch, thanks!