[Xen-ia64-devel] RE: Implementing both (was: Xen/ia64 - global or per VP VHPT)

["Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>]

Oops, accidentally hit reply instead of reply-to-all.

> Hi Eddie --
> 
> Could you explain again what the foreignmap is?
> Is it mappings for other domains (e.g. for domainA
> to access memory in domainB)?  Or is it for
> the hypervisor to access domainA space?  Or
> something else?
> 
> Since the current implementation doesn't have
> this, I just want to ensure I understand it.
> (And it would probably be useful for others
> on the mailing list too!)
> 
> Thanks,
> Dan 
> 
> > -----Original Message-----
> > From: Dong, Eddie [mailto:eddie.dong@xxxxxxxxx] 
> > Sent: Monday, May 02, 2005 10:38 PM
> > To: Magenheimer, Dan (HP Labs Fort Collins); Munoz, Alberto J
> > Cc: ipf-xen; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: RE: Implementing both (was: Xen/ia64 - global or 
> per VP VHPT)
> > 
> > Magenheimer, Dan (HP Labs Fort Collins) wrote:
> > > I _was_ proposing that both mechanisms be present at run time,
> > > but not necessarily permanently -- just to allow easier
> > > testing/comparison during development. By the time we have
> > > real users doing lots of domains, I would hope we would
> > > have enough data to make a decision.
> > > 
> > > Compile-time option would be OK too, but I suspect it
> > > will lead to a debate about what the distribution-default
> > > should be :-) or it will keep changing back and forth
> > > depending on who did the last checkin :-)
> > > 
> > > Either way is OK with me.
> > > 
> > So you have thought of a way to support foreignmap?
> > Eddie
> > 
> 

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