Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp1827949imm; Thu, 20 Sep 2018 03:38:42 -0700 (PDT) X-Google-Smtp-Source: ANB0VdbR0BynG1Zy61Nwd3Gmn9gtGnGfMS/oTBQGzCjq1a+wezslVbVOCra5+zUhZsoJ0/RqEG+/ X-Received: by 2002:a62:3184:: with SMTP id x126-v6mr40344847pfx.49.1537439922316; Thu, 20 Sep 2018 03:38:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537439922; cv=none; d=google.com; s=arc-20160816; b=X7g3bFijwMcEUpRJPLaPW6CpKv5yYjCPHW/J84iGeiUD86Sjyhh2nKr63zJ33nS80o bWDQe3NUhMTpQ9oQm9NHOUXLRKTnmZ0GnSJdpb1J6CKIbaEJRvcjFYB+Ym0fNNAa0ITJ Ts44N+F3eBpqbn3q/qVj0j6PI4dcsK3hIIwN3/Rh8PtNV5nu3QD7yaChV6xgeuNaUOCh 2Xb50/HB9mohvCeSfuqJVRgX/+wxTFUELeWmSAkYUmo9s+xes1+YeEnU+5q12PjqdwK6 qZb2c/umtVLLm10HWqR97vohoAjyKqaoxbLMQ55U0F2IMXY57CkuXnQBJmedwuWQztEz hU1Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=Up7O6MCZeDBno91dmBjN6emNp2J2hVR6//I5rx1ur0s=; b=OhnGiDCGFaN4hR5HUgdQrcGhkD6Yqa0VHwuWcGJvXO5idV4gb988f+kEGOxMGnZrzE wLHTb5Yw9OpJv/hRs8JxeShHTQRTcDEocqhluXP9Z5efb2orjqUOkcMREYuNovFWTxOH N0PFqWgjTyvQlNSUyAgBSeL+O9YMIPU7QyxWuQ9kRBig6iOUu6e/8fFQ7rblRQ1TyDbi Synmj7ER+UU8HppSYCbQT5fi+gKoWNhaH3qoJtKZCMWhX+pU9CTI99o85YSiRxVdc9Nj AVFEeafeh0xPtInEN5SaWngcYGqvyQ0n498EbRD7+imweXqeur/Kn5ciyZgYn8wzjSWI 0h0Q== 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id gn18si24497093plb.500.2018.09.20.03.38.27; Thu, 20 Sep 2018 03:38:42 -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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2387424AbeITQT5 (ORCPT + 99 others); Thu, 20 Sep 2018 12:19:57 -0400 Received: from mga12.intel.com ([192.55.52.136]:59584 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726177AbeITQT5 (ORCPT ); Thu, 20 Sep 2018 12:19:57 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Sep 2018 03:37:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.53,398,1531810800"; d="scan'208";a="74796067" Received: from devel-ww.sh.intel.com ([10.239.48.110]) by orsmga008.jf.intel.com with ESMTP; 20 Sep 2018 03:36:30 -0700 From: Wei Wang To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, pbonzini@redhat.com, ak@linux.intel.com Cc: kan.liang@intel.com, peterz@infradead.org, mingo@redhat.com, rkrcmar@redhat.com, like.xu@intel.com, wei.w.wang@intel.com, jannh@google.com, arei.gonglei@huawei.com Subject: [PATCH v3 0/5] Guest LBR Enabling Date: Thu, 20 Sep 2018 18:05:54 +0800 Message-Id: <1537437959-8751-1-git-send-email-wei.w.wang@intel.com> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Last Branch Recording (LBR) is a performance monitor unit (PMU) feature on Intel CPUs that captures branch related info. This patch series enables this feature to KVM guests. Here is a conclusion of the fundamental methods that we use: 1) the LBR feature is enabled per guest via QEMU setting of KVM_CAP_X86_GUEST_LBR; 2) the LBR stack is passed through to the guest for direct accesses after the guest's first access to any of the lbr related MSRs; 3) When the guest uses the LBR feature with the user callstack mode, the host will help save/resotre the LBR stack when the vCPU is scheduled out/in. ChangeLog: v2->v3: - replaces the pv approach with a lazy save approach to saving the lbr stack on vCPU switching; - destroy the host side perf event if the guest is torn down; - remove the unnecessary event->pmu->stop() before calling perf_event_release_kernel(). v1->v2: - add the per guest LBR capability, KVM_CAP_X86_GUEST_LBR; - save/restore the LBR stack conditionally on the vCPU thread context switching, instead of on VMX transitions; - expose MSR_IA32_PERF_CAPABILITIES to the guest. Like Xu (1): KVM/x86/vPMU: Add APIs to support host save/restore the guest lbr stack Wei Wang (4): perf/x86: add a function to get the lbr stack KVM/x86: KVM_CAP_X86_GUEST_LBR KVM/x86: expose MSR_IA32_PERF_CAPABILITIES to the guest KVM/x86/lbr: lazy save the guest lbr stack arch/x86/events/intel/lbr.c | 49 ++++++++++++- arch/x86/events/perf_event.h | 1 + arch/x86/include/asm/kvm_host.h | 7 ++ arch/x86/include/asm/perf_event.h | 22 ++++++ arch/x86/kvm/cpuid.c | 2 +- arch/x86/kvm/pmu.h | 8 +++ arch/x86/kvm/pmu_intel.c | 41 +++++++++++ arch/x86/kvm/vmx.c | 144 ++++++++++++++++++++++++++++++++++++++ arch/x86/kvm/x86.c | 10 +++ include/uapi/linux/kvm.h | 1 + 10 files changed, 281 insertions(+), 4 deletions(-) -- 2.7.4