From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Oscar Salvador <osalvador@suse.de>
Cc: Ingo Molnar <mingo@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH resend] x86,kvm: Add a kernel parameter to disable PV spinlock
Date: Mon, 4 Sep 2017 15:32:39 -0400 [thread overview]
Message-ID: <e0217f29-7807-fbdb-a2f6-fb8705aa4f73@redhat.com> (raw)
In-Reply-To: <20170904144011.gp7hpis6usjehbuf@hirez.programming.kicks-ass.net>
On 09/04/2017 10:40 AM, Peter Zijlstra wrote:
> On Mon, Sep 04, 2017 at 04:28:36PM +0200, Oscar Salvador wrote:
>> This is just a resend of Waiman Long's patch.
>> I could not find why it was not merged to upstream, so I thought
>> to give it another chance.
>> What follows is what Waiman Long wrote.
>>
>> Xen has an kernel command line argument "xen_nopvspin" to disable
>> paravirtual spinlocks. This patch adds a similar "kvm_nopvspin"
>> argument to disable paravirtual spinlocks for KVM. This can be useful
>> for testing as well as allowing administrators to choose unfair lock
>> for their KVM guests if they want to.
> For testing its trivial to hack your kernel and I don't feel this is
> something an Admin can make reasonable decisions about.
I almost forgot about this patch that I sent quite a while ago. I was
sending this patch out mainly to maintain consistency between KVM and
Xen. This patch is not that important to me, and that is why I didn't
push it further.
Cheers,
Longman
next prev parent reply other threads:[~2017-09-04 19:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 14:28 Oscar Salvador
2017-09-04 14:40 ` Peter Zijlstra
2017-09-04 19:32 ` Waiman Long [this message]
2017-09-04 22:21 ` Davidlohr Bueso
2017-09-05 6:28 ` Juergen Gross
2017-09-05 6:57 ` Oscar Salvador
2017-09-05 8:07 ` Peter Zijlstra
2017-09-05 6:58 ` Peter Zijlstra
2017-09-05 7:35 ` Juergen Gross
2017-09-05 8:10 ` Peter Zijlstra
2017-09-05 8:14 ` Juergen Gross
2017-09-05 8:28 ` Peter Zijlstra
2017-09-05 8:52 ` Juergen Gross
2017-09-05 9:03 ` Peter Zijlstra
2017-09-05 9:11 ` 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=e0217f29-7807-fbdb-a2f6-fb8705aa4f73@redhat.com \
--to=longman@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=osalvador@suse.de \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome