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

[Xen-devel] Hypervisor cpuid time leaf

To: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>
From: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
Date: Wed, 3 May 2017 09:57:48 -0400
Cc: Juergen Gross <jgross@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>
Delivery-date: Wed, 03 May 2017 13:58:08 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

Is there a reason why we don't document hypervisor time leaf (3, or is
it 4?) in public/arch-x86/cpuid.h?

We have a regression in Linux where there is a window when
vcpu_time_info data is not yet available and one possibility is to use
this leaf. But I'd like to be sure it is part of a stable ABI.

-boris

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

Follow-Ups:
- Re: [Xen-devel] Hypervisor cpuid time leaf
  - From: Andrew Cooper

Prev by Date: Re: [Xen-devel] [PATCH 3/7] x86/mm: Further restrict permissions on some virtual mappings
Next by Date: Re: [Xen-devel] Hypervisor cpuid time leaf
Previous by thread: Re: [Xen-devel] [early RFC] ARM PCI Passthrough design document
Next by thread: Re: [Xen-devel] Hypervisor cpuid time leaf
Index(es):
- Date
- Thread

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