[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <568A9A88.8060702@oracle.com>
Date: Mon, 4 Jan 2016 11:15:04 -0500
From: Boris Ostrovsky <boris.ostrovsky@...cle.com>
To: David Vrabel <david.vrabel@...rix.com>,
Joao Martins <joao.m.martins@...cle.com>,
linux-kernel@...r.kernel.org, xen-devel@...ts.xen.org
Cc: x86@...nel.org, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [Xen-devel] [PATCH RFC 3/3] xen/Kconfig: add XEN_TIME_VSYSCALL
option
On 01/04/2016 11:12 AM, David Vrabel wrote:
> 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.
I agree. xen_setup_vsyscall_time_info() will (harmlessly) fail if
PVCLOCK_TSC_STABLE_BIT is not set.
-boris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists