[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1604212051020.3941@nanos>
Date: Thu, 21 Apr 2016 20:55:38 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Borislav Petkov <bp@...en8.de>
cc: Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
vince@...ter.net, eranian@...gle.com,
Arnaldo Carvalho de Melo <acme@...radead.org>,
Mathieu Poirier <mathieu.poirier@...aro.org>
Subject: Re: [PATCH v1 2/5] perf/x86/intel/pt: IP filtering register/cpuid
bits
On Thu, 21 Apr 2016, Borislav Petkov wrote:
> > +#define MSR_IA32_RTIT_ADDR0_A 0x00000580
> > +#define MSR_IA32_RTIT_ADDR0_B 0x00000581
> > +#define MSR_IA32_RTIT_ADDR1_A 0x00000582
> > +#define MSR_IA32_RTIT_ADDR1_B 0x00000583
> > +#define MSR_IA32_RTIT_ADDR2_A 0x00000584
> > +#define MSR_IA32_RTIT_ADDR2_B 0x00000585
> > +#define MSR_IA32_RTIT_ADDR3_A 0x00000586
> > +#define MSR_IA32_RTIT_ADDR3_B 0x00000587
>
> So can we not turn msr-index.h a dumping ground for MSRs pls?
>
> If those are only PT-relevant, why not define them all in pt.h?
I have to disagree here. The MSRs itself can really go into msr-index.h while
the bit definitions might go elsewhere. What's wrong with having all MSRs at a
central place?
Thanks,
tglx
Powered by blists - more mailing lists