mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joao Martins <joao.m.martins@oracle.com>
To: linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: Joao Martins <joao.m.martins@oracle.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Juergen Gross <jgross@suse.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Andy Lutomirski <luto@amacapital.net>
Subject: [PATCH v8 0/5] x86/xen: pvclock vdso support
Date: Wed,  8 Nov 2017 17:19:53 +0000	[thread overview]
Message-ID: <20171108171958.23921-1-joao.m.martins@oracle.com> (raw)

Hey,

This is take 8 for vdso for Xen. PVCLOCK_TSC_STABLE_BIT can be set starting Xen
 4.8 which is required for vdso time related calls. In order to have it on, you
need to have the hypervisor clocksource be TSC e.g. with the following boot
params "clocksource=tsc tsc=stable:socket".

Series is structured as following:

Patch 1 probes for kvm guest in ptp_kvm in the event having
        pvclock_pvti_cpu0_va() moved to common pvclock (on the next patch)
Patch 2 streamlines pvti page get/set in pvclock for both of its users
Patch 3,4 registers the pvti page on Xen and sets it in pvclock accordingly
Patch 5 adds a file to KVM/Xen maintainers for tracking pvclock ABI changes.

All patches appear to be Acked by its respective maintainers.

The difference to v7 is adding the Acks on patches 1 and 2 plus the adjustment
from Thomas to rename the getter function. (Changelog in individual patches)

Thanks,
Joao

Joao Martins (5):
  ptp_kvm: probe for kvm guest availability
  x86/pvclock: add setter for pvclock_pvti_cpu0_va
  x86/xen/time: set pvclock flags on xen_time_init()
  x86/xen/time: setup vcpu 0 time info page
  MAINTAINERS: xen, kvm: track pvclock-abi.h changes

 MAINTAINERS                    |  2 +
 arch/x86/entry/vdso/vma.c      |  2 +-
 arch/x86/include/asm/pvclock.h | 19 +++++----
 arch/x86/kernel/kvmclock.c     |  7 +--
 arch/x86/kernel/pvclock.c      | 14 ++++++
 arch/x86/xen/suspend.c         |  4 ++
 arch/x86/xen/time.c            | 97 ++++++++++++++++++++++++++++++++++++++++++
 arch/x86/xen/xen-ops.h         |  2 +
 drivers/ptp/ptp_kvm.c          |  5 ++-
 include/xen/interface/vcpu.h   | 42 ++++++++++++++++++
 10 files changed, 177 insertions(+), 17 deletions(-)

-- 
2.11.0

             reply	other threads:[~2017-11-08 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 17:19 Joao Martins [this message]
2017-11-08 17:19 ` [PATCH v8 1/5] ptp_kvm: probe for kvm guest availability Joao Martins
2017-11-08 17:19 ` [PATCH v8 2/5] x86/pvclock: add setter for pvclock_pvti_cpu0_va Joao Martins
2017-11-08 17:19 ` [PATCH v8 3/5] x86/xen/time: set pvclock flags on xen_time_init() Joao Martins
2017-11-08 17:19 ` [PATCH v8 4/5] x86/xen/time: setup vcpu 0 time info page Joao Martins
2017-11-08 17:19 ` [PATCH v8 5/5] MAINTAINERS: xen, kvm: track pvclock-abi.h changes Joao Martins
2017-11-09 20:21 ` [PATCH v8 0/5] x86/xen: pvclock vdso support Boris Ostrovsky

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=20171108171958.23921-1-joao.m.martins@oracle.com \
    --to=joao.m.martins@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=hpa@zytor.com \
    --cc=jgross@suse.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

all inboxes | Powered by JetHome®