From: Fernand Sieber <sieberf@amazon.com>
To: <dwmw2@infradead.org>, <peterz@infradead.org>, <seanjc@google.com>
Cc: <abusse@amazon.de>, <bp@alien8.de>, <dave.hansen@linux.intel.com>,
<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>, <sieberf@amazon.com>,
<stable@vger.kernel.org>, <tglx@linutronix.de>, <x86@kernel.org>
Subject: Re: [PATCH v2] perf/x86/intel: Do not enable BTS for guests
Date: Wed, 21 Jan 2026 15:57:13 +0200 [thread overview]
Message-ID: <20260121135713.214711-1-sieberf@amazon.com> (raw)
In-Reply-To: <ff49b3013a4ff7626c6f6ac574f85348c35ccc42.camel@infradead.org>
Hi Peter,
Could you please take another look and see if you are happy to pull in v2 which
implements the approach that you suggested?
Thanks,
--Fernand
Amazon Development Centre (South Africa) (Proprietary) Limited
29 Gogosoa Street, Observatory, Cape Town, Western Cape, 7925, South Africa
Registration Number: 2004 / 034463 / 07
next prev parent reply other threads:[~2026-01-21 13:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-01 14:23 [PATCH] KVM: x86/pmu: Do not accidentally create BTS events Fernand Sieber
2025-12-01 14:26 ` kernel test robot
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
2025-12-11 18:36 ` [PATCH v2] perf/x86/intel: Do not enable BTS for guests Fernand Sieber
2025-12-11 18:38 ` kernel test robot
2026-01-14 17:25 ` David Woodhouse
2026-01-21 13:57 ` Fernand Sieber [this message]
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=20260121135713.214711-1-sieberf@amazon.com \
--to=sieberf@amazon.com \
--cc=abusse@amazon.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--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=peterz@infradead.org \
--cc=seanjc@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.