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

RE: [Xen-ia64-devel] [PATCH] fix INVALID_M2P_ENTRY and INVALID_M2P macro


  • To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Mon, 6 Mar 2006 09:26:26 -0800
  • Delivery-date: Mon, 06 Mar 2006 17:27:06 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZBFbPEahiCi6D5TrmxLYaV5EYlVQALPa+g
  • Thread-topic: [Xen-ia64-devel] [PATCH] fix INVALID_M2P_ENTRY and INVALID_M2P macro

Could you explain what you are planning to use the mpt_table
for?  I think I understand that this is needed for x86
(especially shadow mode) but don't see where it will be used
for ia64, regardless of the memory model.  And if it IS needed
later, won't it need to be per-domain (or at least will need
to return both a phys mapping and a domain)?

Thanks,
Dan 

> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Isaku Yamahata
> Sent: Monday, March 06, 2006 5:00 AM
> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-ia64-devel] [PATCH] fix INVALID_M2P_ENTRY and 
> INVALID_M2P macro
> 
> 
> fix INVALID_M2P_ENTRY and INVALID_M2P macro definitions
> 
> -- 
> yamahata
> 

_______________________________________________
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®.