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

RE: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix


  • To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Wed, 4 Jan 2006 23:08:22 +0800
  • Delivery-date: Wed, 04 Jan 2006 15:14:01 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcYRPAJZIZgfBETgQqSYCAJ57rDDmwABIfgA
  • Thread-topic: [Xen-ia64-devel] [PATCH] Another important Xen/ia64 domU/vbd fix

>From: Tristan Gingold [mailto:Tristan.Gingold@xxxxxxxx]
>Sent: 2006年1月4日 23:34
>
>Le Mercredi 04 Janvier 2006 13:26, Tian, Kevin a écrit :
>> Hi, Dan,
>>      Attached is another important Xen/ia64 fix to enable domU/vbd
>> working on system with >1G hole in dom0's memory layout. Once memmap of
>> dom0 is virtualized, there's no way for dom0 to access machine frames
>> (like from domU) which is outside of EFI memory layout known by dom0,
>> because of no mapping. So we have to disable CONFIG_VIRTUAL_MEM_MAP
>> explicitly, to ensure dom0 constructing a physical memmap array.
>[...]
>Hmm, this side effect is very interesting.
>
>If Xen requires virtual_mem_map, then dom0 will require it too.
>Since dom0 can't work yet with virtual_mem_map, enabling it in Xen is moot,
>isn't it ?
>
>Tristan.

Seems like that. If we add phys2mach (p!=m) concept into dom0, that's not the 
issue then. ;-)

Thanks,
Kevin

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


 


Rackspace

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