public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Joao Martins <joao.m.martins@oracle.com>,
	linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH v4 2/3] x86/xen/time: setup vcpu 0 time info page
Date: Wed, 27 Sep 2017 16:18:36 +0200	[thread overview]
Message-ID: <cf4ff98b-2691-2731-5dc7-d5a905ea5a1c@suse.com> (raw)
In-Reply-To: <20170927134623.3147-3-joao.m.martins@oracle.com>

On 27/09/17 15:46, Joao Martins wrote:
> In order to support pvclock vdso on xen we need to setup the time
> info page for vcpu 0 and register the page with Xen using the
> VCPUOP_register_vcpu_time_memory_area hypercall. This hypercall
> will also forcefully update the pvti which will set some of the
> necessary flags for vdso. Afterwards we check if it supports the
> PVCLOCK_TSC_STABLE_BIT flag which is mandatory for having
> vdso/vsyscall support. And if so, it will set the cpu 0 pvti that
> will be later on used when mapping the vdso image.
> 
> The xen headers are also updated to include the new hypercall for
> registering the secondary vcpu_time_info struct.
> 
> Signed-off-by: Joao Martins <joao.m.martins@oracle.com>

Reviewed-by: Juergen Gross <jgross@suse.com>


Juergen

  reply	other threads:[~2017-09-27 14:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 13:46 [PATCH v4 0/3] x86/xen: pvclock vdso support Joao Martins
2017-09-27 13:46 ` [PATCH v4 1/3] x86/pvclock: add setter for pvclock_pvti_cpu0_va Joao Martins
2017-09-27 13:46 ` [PATCH v4 2/3] x86/xen/time: setup vcpu 0 time info page Joao Martins
2017-09-27 14:18   ` Juergen Gross [this message]
2017-09-27 14:40   ` Boris Ostrovsky
2017-09-27 15:26     ` Joao Martins
2017-09-27 20:22       ` Boris Ostrovsky
2017-09-27 20:57         ` Joao Martins
2017-09-27 22:44           ` Boris Ostrovsky
2017-09-27 23:46             ` Joao Martins
2017-09-28 10:16               ` Joao Martins
2017-09-27 13:46 ` [PATCH v4 3/3] MAINTAINERS: xen, kvm: track pvclock-abi.h changes Joao Martins
2017-09-27 16:06   ` Konrad Rzeszutek Wilk
2017-09-28 10:56     ` Paolo Bonzini

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=cf4ff98b-2691-2731-5dc7-d5a905ea5a1c@suse.com \
    --to=jgross@suse.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=hpa@zytor.com \
    --cc=joao.m.martins@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.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