From: Peter Zijlstra <peterz@infradead.org>
To: Fernand Sieber <sieberf@amazon.com>
Cc: abusse@amazon.de, bp@alien8.de, dave.hansen@linux.intel.com,
dwmw@amazon.co.uk, hborghor@amazon.de, hpa@zytor.com,
jschoenh@amazon.de, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
nh-open-source@amazon.com, nsaenz@amazon.com,
pbonzini@redhat.com, seanjc@google.com, stable@vger.kernel.org,
tglx@linutronix.de, x86@kernel.org
Subject: Re: [PATCH] KVM: x86/pmu: Do not accidentally create BTS events
Date: Wed, 10 Dec 2025 12:16:55 +0100 [thread overview]
Message-ID: <20251210111655.GB3911114@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251210101147.139674-1-sieberf@amazon.com>
On Wed, Dec 10, 2025 at 12:11:47PM +0200, Fernand Sieber wrote:
> > Does something like so work? It is still terrible, but perhaps slightly
> > less so.
> >
> > diff --git a/arch/x86/events/perf_event.h b/arch/x86/events/perf_event.h
> > index 2b969386dcdd..493e6ba51e06 100644
> > --- a/arch/x86/events/perf_event.h
> > +++ b/arch/x86/events/perf_event.h
> > @@ -1558,13 +1558,22 @@ static inline bool intel_pmu_has_bts_period(struct perf_event *event, u64 period
> > struct hw_perf_event *hwc = &event->hw;
> > unsigned int hw_event, bts_event;
> >
> > - if (event->attr.freq)
> > + /*
> > + * Only use BTS for fixed rate period==1 events.
> > + */
> > + if (event->attr.freq || period != 1)
> > + return false;
> > +
> > + /*
> > + * BTS doesn't virtualize.
> > + */
> > + if (event->attr.exclude_host)
> > return false;
> >
> > hw_event = hwc->config & INTEL_ARCH_EVENT_MASK;
> > bts_event = x86_pmu.event_map(PERF_COUNT_HW_BRANCH_INSTRUCTIONS);
> >
> > - return hw_event == bts_event && period == 1;
> > + return hw_event == bts_event;
> > }
> >
> > static inline bool intel_pmu_has_bts(struct perf_event *event)
>
> Hi Peter,
>
> I've pulled your changes and confirmed that they address the original
> bug report.
>
> The repro I use is running on host, with a guest running:
> `perf record -e branches:u -c 2 -a &`
> `perf record -e branches:u -c 2 -a &`
> Then I monitor the enablement of BTS on the host and verify that without
> the change BTS is enabled, and with the change it's not.
>
> This looks good to me, should we go ahead with your changes then?
Yeah, I suppose. Please stick a coherent changelog on and repost.
next prev parent reply other threads:[~2025-12-10 11:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 14:23 Fernand Sieber
2025-12-01 14:45 ` Woodhouse, David
2025-12-02 9:35 ` Peter Zijlstra
2025-12-02 9:59 ` Fernand Sieber
2025-12-02 2:19 ` Like Xu
2025-12-02 10:03 ` Peter Zijlstra
2025-12-02 12:44 ` Peter Zijlstra
2025-12-02 16:03 ` Sean Christopherson
2025-12-10 10:11 ` Fernand Sieber
2025-12-10 11:16 ` Peter Zijlstra [this message]
2025-12-11 18:36 ` [PATCH v2] perf/x86/intel: Do not enable BTS for guests Fernand Sieber
2026-01-14 17:25 ` David Woodhouse
2026-01-21 13:57 ` Fernand Sieber
2026-01-21 15:31 ` Peter Zijlstra
2026-01-21 15:50 ` [tip: perf/urgent] " tip-bot2 for Fernand Sieber
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=20251210111655.GB3911114@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=abusse@amazon.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=hborghor@amazon.de \
--cc=hpa@zytor.com \
--cc=jschoenh@amazon.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nh-open-source@amazon.com \
--cc=nsaenz@amazon.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=sieberf@amazon.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®