From: Peter Zijlstra <peterz@infradead.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: like.xu.linux@gmail.com, jmattson@google.com, eranian@google.com,
santosh.shukla@amd.com, pbonzini@redhat.com, seanjc@google.com,
wanpengli@tencent.com, vkuznets@redhat.com, joro@8bytes.org,
mingo@redhat.com, alexander.shishkin@linux.intel.com,
tglx@linutronix.de, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, kvm@vger.kernel.org, x86@kernel.org,
linux-perf-users@vger.kernel.org, ananth.narayan@amd.com,
kim.phillips@amd.com
Subject: Re: [PATCH v3] perf/amd: Implement erratum #1292 workaround for F19h M00-0Fh
Date: Thu, 10 Feb 2022 09:46:13 +0100 [thread overview]
Message-ID: <YgTQ1UQUcBKzqUk+@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <b775ab2d-c293-d8f0-a436-1ec19c6315d8@amd.com>
On Thu, Feb 10, 2022 at 09:35:14AM +0530, Ravi Bangoria wrote:
> Peter, On subsequent tests, I found that this 'fix' is still not
> optimal. Please drop this patch from your queue for now. Really
> sorry for the noise.
Just in time, and done.
next prev parent reply other threads:[~2022-02-10 8:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 5:57 [PATCH] KVM: x86/pmu: Clear reserved bit PERF_CTL2[43] for AMD erratum 1292 Like Xu
2022-02-02 4:28 ` [PATCH] perf/amd: Implement errata #1292 workaround for F19h M00-0Fh Ravi Bangoria
2022-02-02 5:27 ` Stephane Eranian
2022-02-02 6:02 ` Ravi Bangoria
2022-02-02 6:16 ` Stephane Eranian
2022-02-02 6:32 ` Ravi Bangoria
2022-02-02 10:51 ` [PATCH v2] perf/amd: Implement erratum " Ravi Bangoria
2022-02-02 14:36 ` Peter Zijlstra
2022-02-02 15:32 ` Ravi Bangoria
2022-02-03 9:58 ` [PATCH v3] " Ravi Bangoria
2022-02-09 12:51 ` Peter Zijlstra
2022-02-10 4:05 ` Ravi Bangoria
2022-02-10 8:46 ` Peter Zijlstra [this message]
2022-02-03 4:09 ` [PATCH v2] " Jim Mattson
2022-02-03 5:18 ` Ravi Bangoria
2022-02-03 17:55 ` Jim Mattson
2022-02-04 9:32 ` Ravi Bangoria
2022-02-04 13:01 ` Jim Mattson
2022-02-09 10:18 ` Like Xu
2022-02-09 21:40 ` Jim Mattson
2022-02-10 4:06 ` Ravi Bangoria
2022-02-10 13:56 ` Like Xu
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=YgTQ1UQUcBKzqUk+@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kim.phillips@amd.com \
--cc=kvm@vger.kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=ravi.bangoria@amd.com \
--cc=santosh.shukla@amd.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--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;
as well as URLs for NNTP newsgroup(s).