On Thu, 8 Sep 2016, Alexander Shishkin wrote:
> Vince Weaver writes:
>
> > On the skylake machine with the original 5 patches I got this after
> > continuing to fuzz. Sorry about the lack of frame pointer, next
x> > compile will have it enabled.
> >
> > If it matters, prior to this I hit the u
Vince Weaver writes:
> On the skylake machine with the original 5 patches I got this after
> continuing to fuzz. Sorry about the lack of frame pointer, next
> compile will have it enabled.
>
> If it matters, prior to this I hit the unrelated
> [25510.278199] WARNING: CPU: 1 PID: 25405 at kernel
Ingo Molnar writes:
> * Alexander Shishkin wrote:
>
>> Ingo Molnar writes:
>>
>> > * Alexander Shishkin wrote:
>> >
>> >> Hi,
>> >>
>> >> There were more bugs since the previous version, plus the BTS barriers
>> >> got
>> >> fixed. With these patches, my testcase keeps running and no spuri
* Ingo Molnar wrote:
> Yeah, please re-send it - and please also Vince's Reported-by tag to all
> commits
^--- add
> that would explain failures that Vince reported.
Thanks,
Ingo
* Alexander Shishkin wrote:
> Ingo Molnar writes:
>
> > * Alexander Shishkin wrote:
> >
> >> Hi,
> >>
> >> There were more bugs since the previous version, plus the BTS barriers got
> >> fixed. With these patches, my testcase keeps running and no spurious NMI
> >> warnings pop up any more.
On Wed, 7 Sep 2016, Alexander Shishkin wrote:
> Vince Weaver writes:
>
> > On Wed, 7 Sep 2016, Alexander Shishkin wrote:
> >
> >> Sure. And yes, I did catch a warning, which calls for one more patch
> >> (below). Also one unrelated thing in PEBS that Peter fixed.
> >
> > Does that fix this which
Vince Weaver writes:
> On Wed, 7 Sep 2016, Alexander Shishkin wrote:
>
>> Sure. And yes, I did catch a warning, which calls for one more patch
>> (below). Also one unrelated thing in PEBS that Peter fixed.
>
> Does that fix this which I just got on my skylake machine (4.8-rc5 with
> your other 5
On Wed, Sep 07, 2016 at 11:36:48AM -0400, Vince Weaver wrote:
> On Wed, 7 Sep 2016, Alexander Shishkin wrote:
>
> > Also one unrelated thing in PEBS that Peter fixed.
---
Subject: perf,x86: Fix PEBSv3 record drain
From: Peter Zijlstra
Date: Wed Sep 7 14:42:55 CEST 2016
Alexander hit the WARN_O
On Wed, 7 Sep 2016, Alexander Shishkin wrote:
> Sure. And yes, I did catch a warning, which calls for one more patch
> (below). Also one unrelated thing in PEBS that Peter fixed.
Does that fix this which I just got on my skylake machine (4.8-rc5 with
your other 5 patches applied)
[ 5351.822559]
Ingo Molnar writes:
> * Alexander Shishkin wrote:
>
>> Hi,
>>
>> There were more bugs since the previous version, plus the BTS barriers got
>> fixed. With these patches, my testcase keeps running and no spurious NMI
>> warnings pop up any more.
>
> Could you please also run the fuzzer that Vi
On Tue, 6 Sep 2016, Ingo Molnar wrote:
> > There were more bugs since the previous version, plus the BTS barriers got
> > fixed. With these patches, my testcase keeps running and no spurious NMI
> > warnings pop up any more.
>
> Could you please also run the fuzzer that Vince uses, does it now
* Alexander Shishkin wrote:
> Hi,
>
> There were more bugs since the previous version, plus the BTS barriers got
> fixed. With these patches, my testcase keeps running and no spurious NMI
> warnings pop up any more.
Could you please also run the fuzzer that Vince uses, does it now pass on
h
Hi,
There were more bugs since the previous version, plus the BTS barriers
got fixed. With these patches, my testcase keeps running and no
spurious NMI warnings pop up any more.
Original story:
Recently Vince has reported warnings and panics coming from the
general direction of AUX tracing. I fo
13 matches
Mail list logo
