Received: by 2002:ac0:aa62:0:0:0:0:0 with SMTP id w31-v6csp2447386ima; Mon, 22 Oct 2018 09:53:46 -0700 (PDT) X-Google-Smtp-Source: ACcGV63WCSnpNodlflPnttEM/60dXqd/qMUz80rP2cnPWTAjRM66pjxG4n0D8Mpervs7xU+dTiHt X-Received: by 2002:a63:9409:: with SMTP id m9-v6mr42143056pge.93.1540227226929; Mon, 22 Oct 2018 09:53:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540227226; cv=none; d=google.com; s=arc-20160816; b=upaqDH3JYz59SYXXFtGZiy9mBBk8ez116h9uBIIHOtk+TwH5uFx9A3/WYwMaYCSx/K 4mcbECcbhcow06UcBDVTULJlhe9r6aNeMNjPV0Azo0vPqpPeUMvAh5tMWp9sSXZLftNy Jp3UmeZOcKMnmezQoAikN/lhAyo/ABfRLMEIe5ZcqmaeGrwjvCdudN+Qa4LzjhEEqkD3 3zfael335sg0/xlAibO4MMnGRwgOGflHi0nSUwjqiqQDZPujt/5fIoA1cEpYmY5x9SW+ YMum8J7oAzO5z3kZLt/bufmamohiS4JpvP8t+4kjsPFN2z0wCDWIwamYZN/WVs3joC9L tcyg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject; bh=VEYMMKGWL0NURLs6nBaWsrVMR07F3c3Wcir67Pnk3Vg=; b=S7Vk0T6qFCwJ+ShXGHCshrxL6eDIgsccSwcSDYqlcZ503Q+VKcRxR5FIU7hXNZpD5Q ywwu7nqsMJwYx5i5kPBhaHsJgOAVL9+ObGxTbr5hpixP8xVLtSAz8U2Q6NXBxgZtY3uV 9XUfg4ORrUwetQvtZNa32i1l+yCCUN3jqhqKlumb71NZ5/WyvSYRxT1QDZrY1HCLWczf Q1pyfMI04goj7Rhu/WqvObKDiOZSHkv7FBsrHudEoVWSABnAga6UNWDWWmQmNIyByjwA H1R4aIxuH+VmmLrTzLhlYI3nqkFByX6qcXRxw2/v+DSXgG1N2ZEfftKS1FwtAHKSxyU+ WVwQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 204-v6si35345639pfx.155.2018.10.22.09.53.14; Mon, 22 Oct 2018 09:53:46 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728319AbeJWAu7 convert rfc822-to-8bit (ORCPT + 99 others); Mon, 22 Oct 2018 20:50:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57948 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727218AbeJWAu7 (ORCPT ); Mon, 22 Oct 2018 20:50:59 -0400 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id B5A59308FEC4; Mon, 22 Oct 2018 16:31:47 +0000 (UTC) Received: from llong.remote.csb (dhcp-17-8.bos.redhat.com [10.18.17.8]) by smtp.corp.redhat.com (Postfix) with ESMTP id 242BE1057044; Mon, 22 Oct 2018 16:31:45 +0000 (UTC) Subject: Re: [PATCH v1 2/2] x86/hyperv: make HvNotifyLongSpinWait hypercall To: Juergen Gross , Yi Sun Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de, chao.p.peng@intel.com, chao.gao@intel.com, isaku.yamahata@intel.com, michael.h.kelley@microsoft.com, tianyu.lan@microsoft.com, "K. Y. Srinivasan" , Haiyang Zhang , Stephen Hemminger , Peter Zijlstra , "mingo@redhat.com" , Will Deacon References: <1539954835-34035-1-git-send-email-yi.y.sun@linux.intel.com> <1539954835-34035-3-git-send-email-yi.y.sun@linux.intel.com> <20181022015342.GK11769@yi.y.sun> <2e0d62cb-b706-a5b4-65f7-982a913fb32b@suse.com> From: Waiman Long Organization: Red Hat Message-ID: Date: Mon, 22 Oct 2018 12:31:45 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 In-Reply-To: <2e0d62cb-b706-a5b4-65f7-982a913fb32b@suse.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Content-Language: en-US X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.49]); Mon, 22 Oct 2018 16:31:48 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/22/2018 03:32 AM, Juergen Gross wrote: > On 22/10/2018 03:53, Yi Sun wrote: >> On 18-10-19 16:20:52, Juergen Gross wrote: >>> On 19/10/2018 15:13, Yi Sun wrote: >> [...] >> >>>> diff --git a/kernel/locking/qspinlock_paravirt.h b/kernel/locking/qspinlock_paravirt.h >>>> index 0130e48..9e88c7e 100644 >>>> --- a/kernel/locking/qspinlock_paravirt.h >>>> +++ b/kernel/locking/qspinlock_paravirt.h >>>> @@ -7,6 +7,8 @@ >>>> #include >>>> #include >>>> >>>> +#include >>>> + >>>> /* >>>> * Implement paravirt qspinlocks; the general idea is to halt the vcpus instead >>>> * of spinning them. >>>> @@ -305,6 +307,10 @@ static void pv_wait_node(struct mcs_spinlock *node, struct mcs_spinlock *prev) >>>> wait_early = true; >>>> break; >>>> } >>>> +#if defined(CONFIG_X86_64) && defined(CONFIG_PARAVIRT_SPINLOCKS) && IS_ENABLED(CONFIG_HYPERV) >>>> + if (!hv_notify_long_spin_wait(SPIN_THRESHOLD - loop)) >>>> + break; >>>> +#endif >>> I don't like that. Why should a KVM or Xen guest call into a hyperv >>> specific function? >>> >>> Can't you move this to existing hyperv specific paravirt hooks? >>> >> hv_notify_long_spin_wait() must be called in this loop but it seems >> there is no appropriate existing paravirt hook here. So, can I add >> one more hook in pv_lock_ops to do this notification? > vcpu_is_preempted() is already part of this loop. And this is a paravirt > hook. Can't you make use of that? This might require adding another > parameter to this hook, but I'd prefer that over another pv-spinlock > hook. > > Adding some more locking maintainers and Waiman to the Cc: list. > > > Juergen > I agree with Juergen on that. I would suggest rename the vcpu_is_preempted hook into a more generic vcpu_stop_spinning, perhaps, so different hypervisors can act on the information accordingly. Adding an extra parameter is fine. Cheers, Longman