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

RE: [Xen-ia64-devel] [RFC][PATCH] [RESEND] support special guestoptimisations in the hypervisor


  • To: "Alex Williamson" <alex.williamson@xxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Fri, 6 Jul 2007 11:05:42 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 05 Jul 2007 20:03:39 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: Ace/biGAHeVmSPB9QqqMbv1RIAa8nAADELJQ
  • Thread-topic: [Xen-ia64-devel] [RFC][PATCH] [RESEND] support special guestoptimisations in the hypervisor

>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>Sent: 2007年7月6日 9:36
>To: Xu, Anthony
>Cc: Dietmar Hahn; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] [RFC][PATCH] [RESEND] support special
>guestoptimisations in the hypervisor
>
>On Fri, 2007-07-06 at 09:01 +0800, Xu, Anthony wrote:
>> 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.
>
>Hi Anthony,
>
>   From a maintenance perspective, it's much nicer to use the same
>interface for both PV and HVM.  In this case, it seems like it's even
>fairly easy to do so.  Do you have any specific objections to using a
>feature bit versus an OS identifier?  Personally I like the idea of
>tuning based on a property of the guest OS instead of the type of guest
>OS.  It's also more self explanatory in the code that a guest has
>feature X, therefore we can optimize Y.  Tuning based on IS_WINDOWS() is
>more opaque.

Ok, I agree.

- Anthony

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