Re: [Xen-devel] [RFC][PATCH 04/13] tools/libxl: detect and avoid conflicts with RDM

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

> From: Ian Jackson [mailto:Ian.Jackson@xxxxxxxxxxxxx]
> Sent: Wednesday, April 15, 2015 9:10 PM
> 
> Tiejun Chen writes ("[RFC][PATCH 04/13] tools/libxl: detect and avoid 
> conflicts
> with RDM"):
> > While building a VM, HVM domain builder provides struct hvm_info_table{}
> > to help hvmloader. Currently it includes two fields to construct guest
> > e820 table by hvmloader, low_mem_pgend and high_mem_pgend. So we
> should
> > check them to fix any conflict with RAM.
> 
> I'm not really qualified to understand all of this, because I'm not an
> x86 expert - I don't even know what RDM is.  But this does all seem
> very complicated.  Can I have a second opinion from an x86 expert ?

[Patch 00/13] provides some background for necessary changes. In a nutshell,
the goal is to reserve ACPI reported reserved memory (through RMRR table,
but renamed to Reserved Device Memory (RDM) as a general user space
term here) in gfn space. There are various options to do reservation and 
handle potential conflicts, and based on long discussion people agreed that 
putting that logic centrally in libxl looks a cleaner way to go. That's why 
this 
patch is a bit complex being a core logic of this patch set. I'd expect other 
maintainers to also review this part carefully.

Thanks
Kevin

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel