From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NjUWM-0006qx-Jg
	for qemu-devel@nongnu.org; Mon, 22 Feb 2010 04:24:06 -0500
Received: from [199.232.76.173] (port=53933 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NjUWL-0006qe-MS
	for qemu-devel@nongnu.org; Mon, 22 Feb 2010 04:24:05 -0500
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <avi@redhat.com>) id 1NjUWK-0000YV-T9
	for qemu-devel@nongnu.org; Mon, 22 Feb 2010 04:24:05 -0500
Received: from mx1.redhat.com ([209.132.183.28]:21366)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1NjUWK-0000Y6-68
	for qemu-devel@nongnu.org; Mon, 22 Feb 2010 04:24:04 -0500
Message-ID: <4B824D25.1020003@redhat.com>
Date: Mon, 22 Feb 2010 11:23:49 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] [PATCH] QEMU e820 reservation patch
References: <4B79857A.1030808@redhat.com>
	<4B7EFC74.10209@codemonkey.ws>	<4B817117.1020700@redhat.com>
	<20100221191351.GA30303@morn.localdomain>
In-Reply-To: <20100221191351.GA30303@morn.localdomain>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>, QEMU Developers <qemu-devel@nongnu.org>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>

On 02/21/2010 09:13 PM, Kevin O'Connor wrote:
>
>> 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.
>>      
> What parts of the memory map do you envision qemu managing?
>    

Not a lot.  SeaBIOS should manage hardware devices memory requirements, 
as it does with PCI and HPET.  That leaves non-hardware memory 
requirements.  The kvm reserved areas fall into this category, but I 
don't think there are others.

-- 
error compiling committee.c: too many arguments to function