Re: [PATCH v3 00/21] Update uncore topics, 1x event updates, 2x new archs.

[Arnaldo Carvalho de Melo]

On April 14, 2023 8:14:54 PM GMT-03:00, Ian Rogers <irogers@xxxxxxxxxx> wrote:
>On Fri, Apr 14, 2023 at 1:20 AM Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
>>
>> On Thu, Apr 13, 2023 at 11:04:05AM -0300, Arnaldo Carvalho de Melo wrote:
>> > Em Thu, Apr 13, 2023 at 06:29:28AM -0700, Ian Rogers escreveu:
>> > > Update the uncore PMUs and topic classification as created by:
>> > > https://github.com/intel/perfmon/pull/70
>> > >
>> > > Event updates stem from:
>> > > https://github.com/intel/perfmon/pull/68
>> > > impacting alderlake, icelakex and sapphirerapids.
>> > >
>> > > Grand Ridge and Sierra Forest events stem from:
>> > > https://github.com/intel/perfmon/pull/69
>> > >
>> > > Changes generated by with PR70 in place:
>> > > https://github.com/intel/perfmon/blob/main/scripts/create_perf_json.py
>> > >
>> > > v3. Rebase over the update of alderlake and icelakex events.
>> > > v2. Adds improvements to uncore topics, uncore PMU name fixes and
>> > >     fixes a trigraph issue from ??? being in the json.
>> >
>> > b4 isn't liking it:
>>
>> Fwiw, the way I've set up b4 it takes the patches from my local
>> mailstore and it doesn't matter what made it out to lkml. Specifically,
>> I pipe the patches from mutt directly into b4.
>>
>> I think there's some information in the b4 docs on how to set that up,
>> but let me know if you want more info.
>
>Thanks Peter! I'm using gmail for everything and I suspect I won't be
>able to reproduce your setup easily. I think the right thing is for me
>to set up a public git repository. I got about half-way through the
>kernel.org documentation before getting distracted. I should finish it
>off :-) Perhaps Arnaldo can use the set up though.


Yeah, thanks for the info, I use mutt and will try Peter's B4 setup.

- Arnaldo 
>Thanks,
>Ian