From: David Vrabel <david.vrabel@citrix.com>
To: Joao Martins <joao.m.martins@oracle.com>,
<linux-kernel@vger.kernel.org>, <xen-devel@lists.xen.org>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>, <x86@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
David Vrabel <david.vrabel@citrix.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Xen-devel] [PATCH RFC 3/3] xen/Kconfig: add XEN_TIME_VSYSCALL option
Date: Mon, 4 Jan 2016 16:12:10 +0000 [thread overview]
Message-ID: <568A99DA.6000705@citrix.com> (raw)
In-Reply-To: <1451339557-24473-4-git-send-email-joao.m.martins@oracle.com>
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
next prev parent reply other threads:[~2016-01-04 16:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-28 21:52 [PATCH RFC 0/3] x86/xen: pvclock vdso support Joao Martins
2015-12-28 21:52 ` [PATCH RFC 1/3] x86/pvclock: add setter for pvclock_pvti_cpu0_va Joao Martins
2015-12-28 23:45 ` Andy Lutomirski
2015-12-29 12:50 ` Joao Martins
2015-12-29 13:03 ` Andy Lutomirski
2015-12-28 21:52 ` [PATCH RFC 2/3] x86/xen/time: setup vcpu 0 time info page Joao Martins
2016-01-04 16:07 ` Boris Ostrovsky
2016-01-04 20:41 ` Joao Martins
2016-01-04 21:34 ` Boris Ostrovsky
2016-01-05 12:20 ` Joao Martins
2015-12-28 21:52 ` [PATCH RFC 3/3] xen/Kconfig: add XEN_TIME_VSYSCALL option Joao Martins
2016-01-04 16:12 ` David Vrabel [this message]
2016-01-04 16:15 ` [Xen-devel] " Boris Ostrovsky
2016-01-04 20:41 ` Joao Martins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=568A99DA.6000705@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=joao.m.martins@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).