From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NjFre-0004Mk-NZ for qemu-devel@nongnu.org; Sun, 21 Feb 2010 12:45:06 -0500 Received: from [199.232.76.173] (port=53152 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NjFre-0004MH-Bo for qemu-devel@nongnu.org; Sun, 21 Feb 2010 12:45:06 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NjFrd-0007ad-Fz for qemu-devel@nongnu.org; Sun, 21 Feb 2010 12:45:06 -0500 Received: from mx1.redhat.com ([209.132.183.28]:24201) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NjFrd-0007Zg-1b for qemu-devel@nongnu.org; Sun, 21 Feb 2010 12:45:05 -0500 Message-ID: <4B817117.1020700@redhat.com> Date: Sun, 21 Feb 2010 18:44:55 +0100 From: Jes Sorensen MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] QEMU e820 reservation patch References: <4B79857A.1030808@redhat.com> <4B7EFC74.10209@codemonkey.ws> In-Reply-To: <4B7EFC74.10209@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Kevin O'Connor , QEMU Developers , Stefano Stabellini On 02/19/10 22:02, Anthony Liguori wrote: > Acked-by: Anthony Liguori > > Would be nice to use git-send-email in the future as your attachments > are often rendered poorly by mail clients. Just switching over from quilt to git, and still having issues with git-send-email. It does some things nicely, other things are a pain in the b**t with it, especially for single patch submissions. > I noticed that you use this for the TSS page with EPT but you don't use > this interface for the rest of memory. I'm curious what you think the > right long term split is? If QEMU is not managing the full e820 table, > can we reasonable add entries on our own? I'd like to have QEMU handle more, I picked the TSS page because we changed the location of that in the past and it was the one that triggered my patch in the first place. Now we have the infrastructure, it will be easier to add more. Cheers, Jes