Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp3878270ybi; Fri, 19 Jul 2019 10:36:09 -0700 (PDT) X-Google-Smtp-Source: APXvYqzSl4BPbbdPs4EJ8neZgSDEmkvCVPqckasUIN0wquEU1K+0FH2HtwbrONQSgQ9GtvyP7N0m X-Received: by 2002:a63:9dcb:: with SMTP id i194mr9590099pgd.444.1563557769487; Fri, 19 Jul 2019 10:36:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1563557769; cv=none; d=google.com; s=arc-20160816; b=QaJa1gcAhFFhJHXPN1bvLVLKIgXKbnqZu/Q5x45hvSHkkFHtURGgb6eBqg4QagXyxu 37ePbBkQYGyETuihMSma1KGeuqwSzCrS+ljiZ9qWNdAolhf5wB3pPNjrHByhShdyRuiw nctWyTPH0LyNAbYP8MpQgYNW5+fg5y9g7oHsKAC/MUx2AHE4eOkrp9/Zzie+EEpfLISP zgQRWKE+Q7yW1Ulou5h+2zrvMLzJu4FcPtWT7HI8X2RMdUXFG6OPbi1lfc0UveSSwdF4 bSr+8fsY+bIlrR6y2gRMWXqMxRFgmVbeQXz6qNoLBhU7inJwAqmjg74hqhih4J0gwkgw 5q+w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:openpgp:from:references:cc:to:subject; bh=e6CLIOKxxHQ60CyDNUesfrqwN5wWOdGDSUFSJX50UpA=; b=kW8/1QOk2anByrjfFEeNTDoHnhi7qZQH7tBsZ2Mc2xqOfGbDKtsYk7gw9nYMXHJ72/ 9NBK0O04vjJQo6UwIwGGxz2Hp2aN/oH1rtjPFCz/l5Tkfxq3P30xreR0Iy7eaGnb+j1Y A2/KfHsJbnVg+Fc24tgL7VMTHcGmt9pK6qSJp6RwHN8o/eZuZqbgKzhV4kwqdEgZNZsG a1JbPO/yHxKfNRW/LldGFsLm27MzJVCxi9oRuQwvmEttu7jaSv4SNXLAf3/mZh4RSWy8 1QjTjzCSsaYYlfJALWUSEYQ4Xwf5sehyuRwuM5tKMfrB0EMUIO0RCFw0D+Ag7NWOcGRx QwpQ== 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 1si299786pfe.271.2019.07.19.10.35.52; Fri, 19 Jul 2019 10:36:09 -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 S1729232AbfGSRSg (ORCPT + 99 others); Fri, 19 Jul 2019 13:18:36 -0400 Received: from mail-wr1-f68.google.com ([209.85.221.68]:37403 "EHLO mail-wr1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727602AbfGSRSf (ORCPT ); Fri, 19 Jul 2019 13:18:35 -0400 Received: by mail-wr1-f68.google.com with SMTP id n9so7910433wrr.4 for ; Fri, 19 Jul 2019 10:18:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=e6CLIOKxxHQ60CyDNUesfrqwN5wWOdGDSUFSJX50UpA=; b=dfzXMkfZaml06i9z8TRKJGRBKFEcood4+B3+/tLgAeig0oq0fND8gV/TtGSz+OLQYL t9gk234Z4D5FmkG9FasjJIImbIS04/eiZyKrBf19R5VV8ZIrGB3J04J0yYnIcMIiMPJj loR7lRO8tZ0zfSzrh8CWzDAHnrTmxMQB1XZ/xJ+83cMx4CbKi8J1jSI9txPt1JqKq4Yq DKijbttkwwUbc42KIi8CgHqCjSznRvR9R+p5UMPQJ9biXTHMaj2g6qNzFLXJu4nPBgPa 6PTwFZiq2XnIGSURjvb/O5kwNk4N3bYn+DY4amnsVCIcQa8Ikxpp9MgfsoSyUMjh/nHu pTbA== X-Gm-Message-State: APjAAAU2CSc4ewxAGRkJt3kFCSrN4Dqf0GXiTJ0hp0GVzdAsEJTqTtJH RexoRIbBXZILMIAWKyoMvk5dyA== X-Received: by 2002:adf:8364:: with SMTP id 91mr57058267wrd.13.1563556713168; Fri, 19 Jul 2019 10:18:33 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:8501:6b03:f18c:74f8? ([2001:b07:6468:f312:8501:6b03:f18c:74f8]) by smtp.gmail.com with ESMTPSA id w14sm23627591wrk.44.2019.07.19.10.18.32 (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Fri, 19 Jul 2019 10:18:32 -0700 (PDT) Subject: Re: [PATCH v8 0/3] KVM: x86: Enable user wait instructions To: Tao Xu , rkrcmar@redhat.com, sean.j.christopherson@intel.com, corbet@lwn.net, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, hpa@zytor.com Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, fenghua.yu@intel.com, xiaoyao.li@linux.intel.com, jingqi.liu@intel.com References: <20190716065551.27264-1-tao3.xu@intel.com> From: Paolo Bonzini Openpgp: preference=signencrypt Message-ID: Date: Fri, 19 Jul 2019 19:18:31 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 19/07/19 08:31, Tao Xu wrote: > Ping for comments :) Hi, I'll look at it for 5.4, right after the merge window. Paolo > On 7/16/2019 2:55 PM, Tao Xu wrote: >> UMONITOR, UMWAIT and TPAUSE are a set of user wait instructions. >> >> UMONITOR arms address monitoring hardware using an address. A store >> to an address within the specified address range triggers the >> monitoring hardware to wake up the processor waiting in umwait. >> >> UMWAIT instructs the processor to enter an implementation-dependent >> optimized state while monitoring a range of addresses. The optimized >> state may be either a light-weight power/performance optimized state >> (c0.1 state) or an improved power/performance optimized state >> (c0.2 state). >> >> TPAUSE instructs the processor to enter an implementation-dependent >> optimized state c0.1 or c0.2 state and wake up when time-stamp counter >> reaches specified timeout. >> >> Availability of the user wait instructions is indicated by the presence >> of the CPUID feature flag WAITPKG CPUID.0x07.0x0:ECX[5]. >> >> The patches enable the umonitor, umwait and tpause features in KVM. >> Because umwait and tpause can put a (psysical) CPU into a power saving >> state, by default we dont't expose it to kvm and enable it only when >> guest CPUID has it. If the instruction causes a delay, the amount >> of time delayed is called here the physical delay. The physical delay is >> first computed by determining the virtual delay (the time to delay >> relative to the VM’s timestamp counter). >> >> The release document ref below link: >> Intel 64 and IA-32 Architectures Software Developer's Manual, >> https://software.intel.com/sites/default/files/\ >> managed/39/c5/325462-sdm-vol-1-2abcd-3abcd.pdf >> >> Changelog: >> v8: >>     Add vmx_waitpkg_supported() helper (Sean) >>     Add an accessor to expose umwait_control_cached (Sean) >>     Set msr_ia32_umwait_control in vcpu_vmx u32 and raise #GP when >>     [63:32] is set when rdmsr. (Sean) >>     Introduce a common exit helper handle_unexpected_vmexit (Sean) >> v7: >>     Add nested support for user wait instructions (Paolo) >>     Use the test on vmx->secondary_exec_control to replace >>     guest_cpuid_has (Paolo) >> v6: >>     add check msr_info->host_initiated in get/set msr(Xiaoyao) >>     restore the atomic_switch_umwait_control_msr()(Xiaoyao) >> >> Tao Xu (3): >>    KVM: x86: Add support for user wait instructions >>    KVM: vmx: Emulate MSR IA32_UMWAIT_CONTROL >>    KVM: vmx: Introduce handle_unexpected_vmexit and handle WAITPKG vmexit >> >>   arch/x86/include/asm/vmx.h      |  1 + >>   arch/x86/include/uapi/asm/vmx.h |  6 ++- >>   arch/x86/kernel/cpu/umwait.c    |  6 +++ >>   arch/x86/kvm/cpuid.c            |  2 +- >>   arch/x86/kvm/vmx/capabilities.h |  6 +++ >>   arch/x86/kvm/vmx/nested.c       |  5 ++ >>   arch/x86/kvm/vmx/vmx.c          | 83 ++++++++++++++++++++++++++------- >>   arch/x86/kvm/vmx/vmx.h          |  9 ++++ >>   arch/x86/kvm/x86.c              |  1 + >>   9 files changed, 101 insertions(+), 18 deletions(-) >> >