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

Re: [Xen-devel] [PATCH RFC 3/3] xen/Kconfig: add XEN_TIME_VSYSCALL option

To: Joao Martins <joao.m.martins@xxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxx>
From: David Vrabel <david.vrabel@xxxxxxxxxx>
Date: Mon, 4 Jan 2016 16:12:10 +0000
Cc: x86@xxxxxxxxxx, Ingo Molnar <mingo@xxxxxxxxxx>, David Vrabel <david.vrabel@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Delivery-date: Mon, 04 Jan 2016 16:12:29 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 28/12/15 21:52, Joao Martins wrote:
> This option enables support for pvclock vsyscall/vdso
> support on Xen. Default is off, since Xen doesn't
> expose yet the PVCLOCK_TSC_STABLE_BIT flag.

Do we need a Kconfig option for this?  I think this should always be
enabled.

The kernel support won't be merged until the hypervisor changes have
been accepted.

David

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

Follow-Ups:
- Re: [Xen-devel] [PATCH RFC 3/3] xen/Kconfig: add XEN_TIME_VSYSCALL option
  - From: Boris Ostrovsky

Prev by Date: Re: [Xen-devel] [PATCH RFC 2/3] x86/xen/time: setup vcpu 0 time info page
Next by Date: Re: [Xen-devel] [PATCH 1/3] checkpatch.pl: add missing memory barriers
Previous by thread: Re: [Xen-devel] [PATCH RFC 2/3] x86/xen/time: setup vcpu 0 time info page
Next by thread: Re: [Xen-devel] [PATCH RFC 3/3] xen/Kconfig: add XEN_TIME_VSYSCALL option
Index(es):
- Date
- Thread

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