From: Eduardo Valentin <eduval@amazon.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Eduardo Valentin <eduval@amazon.com>,
Paolo Bonzini <pbonzini@redhat.com>, <rkrcmar@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
<x86@kernel.org>, Waiman Long <longman@redhat.com>,
<kvm@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
"Jan H . Schoenherr" <jschoenh@amazon.de>,
Anthony Liguori <aliguori@amazon.com>
Subject: Re: [PATCH 1/1] locking/qspinlock/x86: Avoid test-and-set when PV_DEDICATED is set
Date: Tue, 24 Oct 2017 08:37:56 -0700 [thread overview]
Message-ID: <20171024153756.GA5007@u40b0340c692b58f6553c.ant.amazon.com> (raw)
In-Reply-To: <20171024081345.GK3165@worktop.lehotels.local>
Hello Peter,
On Tue, Oct 24, 2017 at 10:13:45AM +0200, Peter Zijlstra wrote:
> On Mon, Oct 23, 2017 at 05:44:27PM -0700, Eduardo Valentin wrote:
> > @@ -46,6 +48,8 @@ static inline bool virt_spin_lock(struct qspinlock *lock)
> > if (!static_cpu_has(X86_FEATURE_HYPERVISOR))
> > return false;
> >
> > + if (kvm_para_has_feature(KVM_FEATURE_PV_DEDICATED))
> > + return false;
> > /*
> > * On hypervisors without PARAVIRT_SPINLOCKS support we fall
> > * back to a Test-and-Set spinlock, because fair locks have
>
> This does not apply. Much has been changed here recently.
>
I checked against Linus master branch before sending. Which tree/branch are you referring to / should I based this?
--
All the best,
Eduardo Valentin
next prev parent reply other threads:[~2017-10-24 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 0:44 Eduardo Valentin
2017-10-24 8:13 ` Peter Zijlstra
2017-10-24 15:37 ` Eduardo Valentin [this message]
2017-10-24 16:07 ` Waiman Long
2017-10-24 16:26 ` Eduardo Valentin
2017-10-24 11:18 ` Radim Krčmář
2017-10-31 17:02 ` Eduardo Valentin
2017-11-08 18:41 ` Radim Krčmář
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=20171024153756.GA5007@u40b0340c692b58f6553c.ant.amazon.com \
--to=eduval@amazon.com \
--cc=aliguori@amazon.com \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=jschoenh@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--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 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®