From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933757AbdKAWAn (ORCPT ); Wed, 1 Nov 2017 18:00:43 -0400 Received: from userp1040.oracle.com ([156.151.31.81]:47834 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933807AbdKAWAl (ORCPT ); Wed, 1 Nov 2017 18:00:41 -0400 Subject: Re: [PATCH-tip v2 2/2] x86/xen: Deprecate xen_nopvspin To: Waiman Long , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Jonathan Corbet References: <1509569934-4919-1-git-send-email-longman@redhat.com> <1509569934-4919-3-git-send-email-longman@redhat.com> 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 , Alok Kataria , Rusty Russell , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , Peter Zijlstra From: Boris Ostrovsky Message-ID: <5c36ed18-e59e-1ea3-28e0-414f88965761@oracle.com> Date: Wed, 1 Nov 2017 18:01:10 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <1509569934-4919-3-git-send-email-longman@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Source-IP: userv0022.oracle.com [156.151.31.74] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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); > -