From: Waiman Long <longman@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: x86@kernel.org, virtualization@lists.linux-foundation.org,
kvm@vger.kernel.org, xen-devel@lists.xenproject.org,
linux-kernel@vger.kernel.org, "Juergen Gross" <jgross@suse.com>,
"Alok Kataria" <akataria@vmware.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Waiman Long" <longman@redhat.com>
Subject: [PATCH-tip v2 0/2] x86/paravirt: Enable users to choose PV lock type
Date: Wed, 1 Nov 2017 16:58:52 -0400 [thread overview]
Message-ID: <1509569934-4919-1-git-send-email-longman@redhat.com> (raw)
v1->v2:
- Make pv_spinlock_type a bit mask for easier checking.
- Add patch 2 to deprecate xen_nopvspin
v1 - https://lkml.org/lkml/2017/11/1/381
Patch 1 adds a new pvlock_type parameter for the administrators to
specify the type of lock to be used in a para-virtualized kernel.
Patch 2 deprecates Xen's xen_nopvspin parameter as it is no longer
needed.
Waiman Long (2):
x86/paravirt: Add kernel parameter to choose paravirt lock type
x86/xen: Deprecate xen_nopvspin
Documentation/admin-guide/kernel-parameters.txt | 11 ++++---
arch/x86/include/asm/paravirt.h | 9 ++++++
arch/x86/kernel/kvm.c | 3 ++
arch/x86/kernel/paravirt.c | 40 ++++++++++++++++++++++++-
arch/x86/xen/spinlock.c | 17 +++++------
5 files changed, 65 insertions(+), 15 deletions(-)
--
1.8.3.1
next reply other threads:[~2017-11-01 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 20:58 Waiman Long [this message]
2017-11-01 20:58 ` [PATCH-tip v2 1/2] x86/paravirt: Add kernel parameter to choose paravirt lock type Waiman Long
2017-11-01 20:58 ` [PATCH-tip v2 2/2] x86/xen: Deprecate xen_nopvspin Waiman Long
2017-11-01 22:01 ` Boris Ostrovsky
2017-11-02 13:25 ` Waiman Long
2017-11-02 13:28 ` Juergen Gross
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=1509569934-4919-1-git-send-email-longman@redhat.com \
--to=longman@redhat.com \
--cc=akataria@vmware.com \
--cc=boris.ostrovsky@oracle.com \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).