All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
	Radim Krcmar <rkrcmar@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	Alexander Graf <agraf@suse.de>, Andy Lutomirski <luto@kernel.org>
Subject: [PATCH v2 0/4] x86: KVM vdso and clock improvements
Date: Sun, 20 Dec 2015 03:05:40 -0800	[thread overview]
Message-ID: <cover.1450561424.git.luto@kernel.org> (raw)

x86: KVM vdso and clock improvements

NB: patch 1 doesn't really belong here, but it makes this a lot
easier for me to test.  Patch 1, if it's okay at all, should go
though the kvm tree.  The rest should probably go through
tip:x86/vdso once they're reviewed.

I'll do a followup to enable vdso pvclock on 32-bit guests.
I'm not currently set up to test it.  (The KVM people could also
do it very easily on top of these patches.)

Changes from v1:
 - Dropped patch 1
 - Added Paolo's review and acks
 - Fixed a build issue on some configs

Andy Lutomirski (4):
  x86, vdso, pvclock: Simplify and speed up the vdso pvclock reader
  x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap
  x86/vdso: Remove pvclock fixmap machinery
  x86/vdso: Enable vdso pvclock access on all vdso variants

 arch/x86/entry/vdso/vclock_gettime.c  | 151 ++++++++++++++++------------------
 arch/x86/entry/vdso/vdso-layout.lds.S |   3 +-
 arch/x86/entry/vdso/vdso2c.c          |   3 +
 arch/x86/entry/vdso/vma.c             |  14 ++++
 arch/x86/include/asm/fixmap.h         |   5 --
 arch/x86/include/asm/pvclock.h        |  14 ++--
 arch/x86/include/asm/vdso.h           |   1 +
 arch/x86/kernel/kvmclock.c            |  11 ++-
 arch/x86/kernel/pvclock.c             |  24 ------
 9 files changed, 107 insertions(+), 119 deletions(-)

-- 
2.5.0


             reply	other threads:[~2015-12-20 11:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20 11:05 Andy Lutomirski [this message]
2015-12-20 11:05 ` [PATCH v2 1/4] x86, vdso, pvclock: Simplify and speed up the vdso pvclock reader Andy Lutomirski
2016-01-04 20:26   ` Marcelo Tosatti
2016-01-04 22:33     ` Andy Lutomirski
2016-01-04 22:59       ` Marcelo Tosatti
2016-01-04 23:14         ` [PATCH] x86/vdso/pvclock: Protect STABLE check with the seqcount Andy Lutomirski
2016-01-07 21:02           ` Marcelo Tosatti
2016-01-07 21:13             ` Andy Lutomirski
2016-01-07 21:47               ` Paolo Bonzini
2016-01-08 14:04               ` Marcelo Tosatti
2016-01-12 19:48                 ` Andy Lutomirski
2016-01-13 10:46                   ` Ingo Molnar
2016-01-14  9:07           ` [tip:x86/urgent] " tip-bot for Andy Lutomirski
2015-12-20 11:05 ` [PATCH v2 2/4] x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap Andy Lutomirski
2015-12-20 11:05 ` [PATCH v2 3/4] x86/vdso: Remove pvclock fixmap machinery Andy Lutomirski
2015-12-20 11:05 ` [PATCH v2 4/4] x86/vdso: Enable vdso pvclock access on all vdso variants Andy Lutomirski

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=cover.1450561424.git.luto@kernel.org \
    --to=luto@kernel.org \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.