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 0/5] x86: KVM vdso and clock improvements
Date: Wed, 9 Dec 2015 15:12:08 -0800 [thread overview]
Message-ID: <cover.1449702533.git.luto@kernel.org> (raw)
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.)
Andy Lutomirski (5):
x86/kvm: On KVM re-enable (e.g. after suspend), update clocks
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 ------
arch/x86/kvm/x86.c | 75 +----------------
10 files changed, 110 insertions(+), 191 deletions(-)
--
2.5.0
WARNING: multiple messages have this Message-ID (diff)
From: Andy Lutomirski <luto@kernel.org>
To: x86@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>
Subject: [PATCH 0/5] x86: KVM vdso and clock improvements
Date: Thu, 10 Dec 2015 19:20:17 -0800 [thread overview]
Message-ID: <cover.1449702533.git.luto@kernel.org> (raw)
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.)
Andy Lutomirski (5):
x86/kvm: On KVM re-enable (e.g. after suspend), update clocks
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 ------
arch/x86/kvm/x86.c | 75 +----------------
10 files changed, 110 insertions(+), 191 deletions(-)
--
2.5.0
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2015-12-09 23:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 23:12 Andy Lutomirski [this message]
2015-12-11 3:20 ` [PATCH 0/5] x86: KVM vdso and clock improvements Andy Lutomirski
2015-12-09 23:12 ` [PATCH 1/5] x86/kvm: On KVM re-enable (e.g. after suspend), update clocks Andy Lutomirski
2015-12-11 3:20 ` Andy Lutomirski
2015-12-14 8:16 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2015-12-14 10:18 ` Paolo Bonzini
2016-03-16 22:06 ` [PATCH 1/5] " Radim Krcmar
2016-03-16 22:15 ` Andy Lutomirski
2016-03-16 22:59 ` Radim Krcmar
2016-03-16 23:07 ` Andy Lutomirski
2016-03-17 15:10 ` Radim Krcmar
2016-03-17 18:22 ` Andy Lutomirski
2016-03-17 19:58 ` Radim Krcmar
2015-12-09 23:12 ` [PATCH 2/5] x86, vdso, pvclock: Simplify and speed up the vdso pvclock reader Andy Lutomirski
2015-12-11 3:20 ` Andy Lutomirski
2015-12-10 9:09 ` Paolo Bonzini
2015-12-11 7:52 ` Ingo Molnar
2015-12-11 8:42 ` Paolo Bonzini
2015-12-11 18:03 ` Andy Lutomirski
2015-12-14 8:16 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2015-12-09 23:12 ` [PATCH 3/5] x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap Andy Lutomirski
2015-12-11 3:20 ` Andy Lutomirski
2015-12-10 9:09 ` Paolo Bonzini
2015-12-14 8:17 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2015-12-09 23:12 ` [PATCH 4/5] x86/vdso: Remove pvclock fixmap machinery Andy Lutomirski
2015-12-11 3:20 ` Andy Lutomirski
2015-12-10 9:09 ` Paolo Bonzini
2015-12-11 8:06 ` [PATCH] x86/platform/uv: Include clocksource.h for clocksource_touch_watchdog() Ingo Molnar
2015-12-11 8:06 ` Ingo Molnar
2015-12-11 17:33 ` Andy Lutomirski
2015-12-14 8:17 ` [tip:x86/asm] x86/vdso: Remove pvclock fixmap machinery tip-bot for Andy Lutomirski
2015-12-09 23:12 ` [PATCH 5/5] x86/vdso: Enable vdso pvclock access on all vdso variants Andy Lutomirski
2015-12-11 3:20 ` Andy Lutomirski
2015-12-10 9:10 ` Paolo Bonzini
2015-12-14 8:17 ` [tip:x86/asm] " tip-bot for Andy Lutomirski
2015-12-11 3:20 ` [PATCH 1/5] x86/kvm: On KVM re-enable (e.g. after suspend), update clocks Andy Lutomirski
2015-12-11 3:20 ` [PATCH 2/5] x86, vdso, pvclock: Simplify and speed up the vdso pvclock reader Andy Lutomirski
2015-12-11 3:20 ` [PATCH 3/5] x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap Andy Lutomirski
2015-12-11 3:20 ` [PATCH 4/5] x86/vdso: Remove pvclock fixmap machinery Andy Lutomirski
2015-12-11 3:20 ` [PATCH 5/5] x86/vdso: Enable vdso pvclock access on all vdso variants Andy Lutomirski
2015-12-11 3:21 ` [PATCH 0/5] x86: KVM vdso and clock improvements Andy Lutomirski
2015-12-11 3:21 ` Andy Lutomirski
-- strict thread matches above, loose matches on Subject: below --
2015-12-11 3:20 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.1449702533.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.