From: "Wang, Wei W" <wei.w.wang@intel.com>
To: "Li, Xiaoyao" <xiaoyao.li@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
"Namhyung Kim" <namhyung@kernel.org>, "Christopherson,,
Sean" <seanjc@google.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: "linux-perf-users@vger.kernel.org"
<linux-perf-users@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: RE: [RFC PATCH 0/2] KVM: VMX: Fix VM entry failure on PT_MODE_HOST_GUEST while host is using PT
Date: Thu, 8 Sep 2022 08:53:06 +0000 [thread overview]
Message-ID: <CY5PR11MB6365DFC5D715E87E951A63F0DC409@CY5PR11MB6365.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3b78a0c7-de8f-fe44-ec58-bcc4e231191b@intel.com>
On Thursday, September 8, 2022 3:26 PM, Li, Xiaoyao wrote:
> > +
> > +struct perf_event *pt_get_curr_event(void) {
> > + struct pt *pt = this_cpu_ptr(&pt_ctx);
>
> Wei,
>
> I'm not sure if we can use pt->handle.event instead or not.
>
> > + return pt->event;
Yes, I think we could reuse that.
next prev parent reply other threads:[~2022-09-08 8:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 8:56 [RFC PATCH 0/2] KVM: VMX: Fix VM entry failure on PT_MODE_HOST_GUEST while host is using PT Xiaoyao Li
2022-08-25 8:56 ` [RFC PATCH 1/2] perf/x86/intel/pt: Introduce intel_pt_{stop,resume}() Xiaoyao Li
2022-08-25 15:23 ` Sean Christopherson
2022-08-25 8:56 ` [RFC PATCH 2/2] KVM: VMX: Stop/resume host PT before/after VM entry when PT_MODE_HOST_GUEST Xiaoyao Li
2022-08-25 15:34 ` Sean Christopherson
2022-08-25 15:45 ` Xiaoyao Li
2022-08-25 15:59 ` Sean Christopherson
2022-08-26 6:32 ` Xiaoyao Li
2022-08-26 15:08 ` Sean Christopherson
2022-08-29 7:49 ` [RFC PATCH 0/2] KVM: VMX: Fix VM entry failure on PT_MODE_HOST_GUEST while host is using PT Wang, Wei W
2022-08-29 17:33 ` Sean Christopherson
2022-08-30 6:02 ` Wang, Wei W
2022-09-08 7:25 ` Xiaoyao Li
2022-09-08 8:53 ` Wang, Wei W [this message]
2022-09-14 4:15 ` Xiaoyao Li
2022-09-14 6:16 ` Wang, Wei W
2022-09-14 20:25 ` Liang, Kan
2022-09-15 2:46 ` Wang, Wei W
2022-09-15 13:54 ` Liang, Kan
2022-09-15 14:39 ` Wang, Wei W
2022-09-15 15:42 ` Liang, Kan
2022-09-16 2:30 ` Wang, Wei W
2022-09-16 13:27 ` Liang, Kan
2022-09-19 13:46 ` Wang, Wei W
2022-09-19 14:41 ` Liang, Kan
2022-09-19 15:22 ` Wang, Wei W
2022-09-19 15:55 ` Liang, Kan
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=CY5PR11MB6365DFC5D715E87E951A63F0DC409@CY5PR11MB6365.namprd11.prod.outlook.com \
--to=wei.w.wang@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=xiaoyao.li@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).