From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54282) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WD0fn-0000ZK-5W for qemu-devel@nongnu.org; Mon, 10 Feb 2014 18:54:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WD0fe-00077a-OS for qemu-devel@nongnu.org; Mon, 10 Feb 2014 18:53:59 -0500 Received: from mail-qc0-x22a.google.com ([2607:f8b0:400d:c01::22a]:59810) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WD0fe-00077W-Ic for qemu-devel@nongnu.org; Mon, 10 Feb 2014 18:53:50 -0500 Received: by mail-qc0-f170.google.com with SMTP id e9so11893468qcy.15 for ; Mon, 10 Feb 2014 15:53:50 -0800 (PST) Date: Tue, 11 Feb 2014 09:53:15 +1000 From: "Edgar E. Iglesias" Message-ID: <20140210235315.GB25819@xsjedgari30.xlnx.xilinx.com> References: <1391420690-23745-1-git-send-email-edgar.iglesias@gmail.com> <52F7834B.8060004@suse.de> <20140210231055.GA25819@xsjedgari30.xlnx.xilinx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] [PATCH v4 00/22] Steps towards per CPU address-spaces List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers , Blue Swirl , Anthony Liguori , pcrost@xilinx.com, Paolo Bonzini , Andreas =?iso-8859-1?Q?F=E4rber?= , Aurelien Jarno , Richard Henderson On Mon, Feb 10, 2014 at 11:42:35PM +0000, Peter Maydell wrote: > On 10 February 2014 23:10, Edgar E. Iglesias wrote: > > My thinking was in terms of trying to minimize the amount of > > AS structures we create in cases were the nr of master outnumber > > the nr of ASs. But there might be ways to achieve being light > > even if we dont explicitely pass AS refs around. Will try to get > > a chance to look at a MemoryRegion based interface instead > > (if no one beats me to it). > > Is there that much overhead to creating an AS per master? I guess > you end up recalculating the same memory flatview for every AS > when a memory region gets mapped or unmapped. > In any case, if it's OK to share AddressSpaces between masters > then we can relatively easily do so, since there's already a list > of all AddressSpaces that you can run through to find the one > whose root MemoryRegion is the one you want. (Probably needs > a refcount in the AddressSpace struct as well.) Right, something like that might be worthwhile. It might not make much difference until we start ramping things up significantly (in terms of amount of masters). Cheers, Edgar