[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-ia64-devel] [RFC][PATCH] [RESEND] support special guest optimisations in the hypervisor
>From: Dietmar Hahn [mailto:dietmar.hahn@xxxxxxxxxxxxxxxxxxx] >Sent: 2007年7月5日 18:33 >To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx >Cc: Xu, Anthony; Alex Williamson >Subject: Re: [Xen-ia64-devel] [RFC][PATCH] [RESEND] support special guest >optimisations in the hypervisor > >Am Donnerstag, 5. Juli 2007 schrieb Dietmar Hahn: >> Am Donnerstag, 5. Juli 2007 schrieb Xu, Anthony: >> > I think you can do this way. >> > >> > A little concern, >> > For dom0 & domU, pgprot and key are provided by guest, it is natural. >> > While for HVM , pgprot and key are provided Xen, it is a little strange. >> >> Ok I understand, I will prepare a new patch. >> Thanks. >While thinking about the HVM part: should I only create an opt_feature >#define OPTF_IDENT_MAP_HVM_REG4_5 >and simply replace the >if (GOS_WINDOWS(v) >by >if (opt_feature & OPTF_IDENT_MAP_HVM_REG4_5) >or should I do it the same way like on PV with setting pgprot and key >(maybe this is overkill?) in the struct arch_domain and use these values >during the optimization? >Thanks. Hi Dietmar, I can understand you want to use the same interface for special guest Optimizations. While I think it is OK to use different interfaces for HVM and domU. So I suggest HVM still use interface like GOS_WINDOWS(v), while domU uses opt_feature interface. Thanks, Anthony _______________________________________________ Xen-ia64-devel mailing list Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-ia64-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |