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

Re: [Xen-devel] [PATCH] replace rdtsc emulation-vs-native xen boot option with per-domain (hypervisor part)


  • To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Fri, 06 Nov 2009 07:01:49 +0000
  • Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 05 Nov 2009 23:02:21 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcpeOt5nebt7pqybQLieaVFjktsg0wAdCQ7n
  • Thread-topic: [Xen-devel] [PATCH] replace rdtsc emulation-vs-native xen boot option with per-domain (hypervisor part)

On 05/11/2009 17:08, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> For a PV, I'm thinking about adding them to the
> domctl_getdomaininfo struct rather than add additional
> domctls for each.  Is this the proper place or will
> changes to this struct result in backward compatibility
> problems or ??

It would be fine as we provide no compatibility guarantees for any domctl or
sysctl across consecutive major Xen releases.

 -- Keir



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


 


Rackspace

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