[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [NEO 1:1] Nativedom 1:1 Mapping


  • To: Guy Zana <guy@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Tue, 25 Sep 2007 16:18:16 +0100
  • Delivery-date: Tue, 25 Sep 2007 08:14:04 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acf7nOHWOm+J+TgmQSWCP5gB/ehOoAAjI5gIAGo1EYAAbUHRWw==
  • Thread-topic: [Xen-devel] [NEO 1:1] Nativedom 1:1 Mapping

On 25/9/07 16:05, "Guy Zana" <guy@xxxxxxxxxxxx> wrote:

> I sent the patch for review (not for inclusion).
> I know you are not very fond of the E820_1TO1 addition.
> 
> You mean it would be cleaner to mark these 1:1 chunks as reserved? Or do you
> suggest to do that completely differently?
> Can you elaborate on that please?

Firstly, yes: I would mark the region as reserved or remove it completely,
rather than marking it with a newly-invented type code. Secondly I would
think you only need to modify boot_e820, probably using the helper function
reserve_in_boot_e820(), because that will suffice to hide the memory from
the normal memory allocator. And that's all you're trying to do, right?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.