From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NZWQI-0008I3-4i for qemu-devel@nongnu.org; Mon, 25 Jan 2010 16:24:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NZWQC-0008F6-PN for qemu-devel@nongnu.org; Mon, 25 Jan 2010 16:24:37 -0500 Received: from [199.232.76.173] (port=55475 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NZWQC-0008F2-Hi for qemu-devel@nongnu.org; Mon, 25 Jan 2010 16:24:32 -0500 Received: from mx1.redhat.com ([209.132.183.28]:38764) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NZWQB-0006CM-Jk for qemu-devel@nongnu.org; Mon, 25 Jan 2010 16:24:32 -0500 Message-ID: <4B5E0C07.6000906@redhat.com> Date: Mon, 25 Jan 2010 22:24:23 +0100 From: Jes Sorensen MIME-Version: 1.0 References: <4B5DCAF2.3010105@redhat.com> <4B5DCB93.7050007@redhat.com> <4B5DCC53.508@redhat.com> <2CE27313-0F43-4A93-905F-3DF4815BC0B5@suse.de> <4B5DD13F.5060105@redhat.com> <04C75D06-9153-410E-8D91-474F2A92D265@suse.de> <4B5DD8DE.7050100@redhat.com> <4B5DFBA7.9080100@codemonkey.ws> <4B5E077C.2040602@redhat.com> <64A8D2C1-0FAA-48EB-B82C-9C3ED44AE7B0@suse.de> In-Reply-To: <64A8D2C1-0FAA-48EB-B82C-9C3ED44AE7B0@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] QEMU - provide e820 reserve through qemu_cfg List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Anthony Liguori , KVM General , QEMU Developers , Kevin O'Connor , Avi Kivity On 01/25/10 22:08, Alexander Graf wrote: > > On 25.01.2010, at 22:05, Jes Sorensen wrote: >> Only problem is that we don't really have a way to pass back info >> saying 'you messed up trying to pinch an area that the BIOS wants >> for itself'. > > Eh - the BIOS shouldn't even try to use regions that are declared as reserved using this interface. > I guess we're mostly talking about DMI and ACPI tables. They can be anywhere in RAM. What I had in mind with the above was the situation where a user tries to reserve a region that is hardcoded into the BIOS, such as the address of the BIOS text/data etc. I don't think it would be a real problem anyway, if some user wants to play with it, they have to take the risk of shooting themself in the foot :) Cheers, Jes