Add Andi who is our PMU expert. He will give some insight into this issue.
Thanks
Kevin
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Thursday, December 03, 2015 11:45 PM
>
> On 12/03/2015 06:02 AM, Jan Beulich wrote:
> On 03.12.15 at 11:46,
I'm not aware of that specific quirk on Nehalem. Standard perf has a workaround
for the errata below, but it sounds different from what you have.
But if it's a NHM/WSM problem your model numbers are certainly not enough.
You always need some kind of limiter for the PMI because it is possible
On 12/07/2015 04:24 PM, Kleen, Andi wrote:
I'm not aware of that specific quirk on Nehalem. Standard perf has a workaround
for the errata below, but it sounds different from what you have.
But if it's a NHM/WSM problem your model numbers are certainly not enough.
That's exactly the problem
>>> On 03.12.15 at 07:16, wrote:
>> From: Dietmar Hahn [mailto:dietmar.h...@ts.fujitsu.com]
>> Sent: Wednesday, December 02, 2015 5:21 PM
>>
>> Am Mittwoch 02 Dezember 2015, 02:20:49 schrieb Tian, Kevin:
>> > > From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
>> >
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, December 03, 2015 6:36 PM
>
> >>> On 03.12.15 at 07:16, wrote:
> >> From: Dietmar Hahn [mailto:dietmar.h...@ts.fujitsu.com]
> >> Sent: Wednesday, December 02, 2015 5:21 PM
> >>
> >> Am Mittwoch 02 Dezember
On 12/03/2015 06:02 AM, Jan Beulich wrote:
On 03.12.15 at 11:46, wrote:
From: Jan Beulich [mailto:jbeul...@suse.com]
Sent: Thursday, December 03, 2015 6:36 PM
On 03.12.15 at 07:16, wrote:
From: Dietmar Hahn
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Thursday, December 03, 2015 11:45 PM
>
> On 12/03/2015 06:02 AM, Jan Beulich wrote:
> On 03.12.15 at 11:46, wrote:
> >>> From: Jan Beulich [mailto:jbeul...@suse.com]
> >>> Sent: Thursday, December
Am Mittwoch 02 Dezember 2015, 02:20:49 schrieb Tian, Kevin:
> > From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> > Sent: Wednesday, December 02, 2015 12:50 AM
> >
> > * Limit VPMU support to PMU versions 2, 3 and 4 (emulated at version 3
> > level)
> > * Always implement family 6 VPMU
> From: Dietmar Hahn [mailto:dietmar.h...@ts.fujitsu.com]
> Sent: Wednesday, December 02, 2015 5:21 PM
>
> Am Mittwoch 02 Dezember 2015, 02:20:49 schrieb Tian, Kevin:
> > > From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> > > Sent: Wednesday, December 02, 2015 12:50 AM
> > >
> > > *
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Wednesday, December 02, 2015 12:50 AM
>
> * Limit VPMU support to PMU versions 2, 3 and 4 (emulated at version 3 level)
> * Always implement family 6 VPMU quirk.
> ==> Intel folks: is the quirk needed for all family 6
* Limit VPMU support to PMU versions 2, 3 and 4 (emulated at version 3 level)
* Always implement family 6 VPMU quirk.
==> Intel folks: is the quirk needed for all family 6 processors or can we
limit it to certain models?
* Update (or rather restore) arch VPMU files
11 matches
Mail list logo