Sean Christopherson writes:
On Tue, Aug 13, 2024, Colton Lewis wrote:
Sean Christopherson writes:
> On Tue, Aug 13, 2024, Colton Lewis wrote:
> > (I was positive I had sent this already, but I couldn't find it on
the
> > mailing list to reply to and ask for reviews.)
> You did[*], it
On Tue, Aug 13, 2024, Colton Lewis wrote:
> Sean Christopherson writes:
>
> > On Tue, Aug 13, 2024, Colton Lewis wrote:
> > > (I was positive I had sent this already, but I couldn't find it on the
> > > mailing list to reply to and ask for reviews.)
>
> > You did[*], it's sitting in my todo fold
Sean Christopherson writes:
On Tue, Aug 13, 2024, Colton Lewis wrote:
(I was positive I had sent this already, but I couldn't find it on the
mailing list to reply to and ask for reviews.)
You did[*], it's sitting in my todo folder. Two things.
1. Err on the side of caution when potential
On Tue, Aug 13, 2024, Colton Lewis wrote:
> (I was positive I had sent this already, but I couldn't find it on the
> mailing list to reply to and ask for reviews.)
You did[*], it's sitting in my todo folder. Two things.
1. Err on the side of caution when potentially resending, and tag everything
(I was positive I had sent this already, but I couldn't find it on the
mailing list to reply to and ask for reviews.)
Extend pmu_counters_test to AMD CPUs.
As the AMD PMU is quite different from Intel with different events and
feature sets, this series introduces a new code path to test it,
speci