From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Waiman Long <longman@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: "Juergen Gross" <jgross@suse.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
xen-devel@lists.xenproject.org,
"Alok Kataria" <akataria@vmware.com>
Subject: Re: [PATCH-tip v2 2/2] x86/xen: Deprecate xen_nopvspin
Date: Wed, 1 Nov 2017 18:01:10 -0400 [thread overview]
Message-ID: <5c36ed18-e59e-1ea3-28e0-414f88965761@oracle.com> (raw)
In-Reply-To: <1509569934-4919-3-git-send-email-longman@redhat.com>
On 11/01/2017 04:58 PM, Waiman Long wrote:
> +/* TODO: To be removed in a future kernel version */
> static __init int xen_parse_nopvspin(char *arg)
> {
> - xen_pvspin = false;
> + pr_warn("xen_nopvspin is deprecated, replace it with \"pvlock_type=queued\"!\n");
> + if (!pv_spinlock_type)
> + pv_spinlock_type = locktype_queued;
Since we currently end up using unfair locks and because you are
deprecating xen_nopvspin I wonder whether it would be better to set this
to locktype_unfair so that current behavior doesn't change. (Sorry, I
haven't responded to your earlier message before you posted this). Juergen?
I am also not sure I agree with making pv_spinlock an enum *and* a
bitmask at the same time. I understand that it makes checks easier but I
think not assuming a value or a pattern would be better, especially
since none of the uses is on a critical path.
(For example, !pv_spinlock_type is the same as locktype_auto, which is
defined but never used)
-boris
> return 0;
> }
> early_param("xen_nopvspin", xen_parse_nopvspin);
> -
next prev parent reply other threads:[~2017-11-01 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1509569934-4919-1-git-send-email-longman@redhat.com>
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
[not found] ` <1509569934-4919-3-git-send-email-longman@redhat.com>
2017-11-01 22:01 ` Boris Ostrovsky [this message]
2017-11-02 13:25 ` Waiman Long
[not found] ` <2fb79da7-4c95-160a-a626-670c536f490a@redhat.com>
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=5c36ed18-e59e-1ea3-28e0-414f88965761@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=akataria@vmware.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=longman@redhat.com \
--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