RE: [bug] kpti, perf_event, bts: sporadic truncated trace

2018-07-13 Thread Hugh Dickins
On Fri, 13 Jul 2018, Metzger, Markus T wrote: > Hello Hugh, > > > A little "optimization" crept into alloc_bts_buffer() along the way, which > > now > > places bts_interrupt_threshold not on a record boundary. > > And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says "This > >

RE: [bug] kpti, perf_event, bts: sporadic truncated trace

2018-07-13 Thread Hugh Dickins
On Fri, 13 Jul 2018, Metzger, Markus T wrote: > Hello Hugh, > > > A little "optimization" crept into alloc_bts_buffer() along the way, which > > now > > places bts_interrupt_threshold not on a record boundary. > > And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says "This > >

Re: [bug] kpti, perf_event, bts: sporadic truncated trace

2018-07-13 Thread Peter Zijlstra
On Thu, Jul 12, 2018 at 06:22:13PM -0700, Hugh Dickins wrote: > A little "optimization" crept into alloc_bts_buffer() along the way, > which now places bts_interrupt_threshold not on a record boundary. > And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says > "This address must

Re: [bug] kpti, perf_event, bts: sporadic truncated trace

2018-07-13 Thread Peter Zijlstra
On Thu, Jul 12, 2018 at 06:22:13PM -0700, Hugh Dickins wrote: > A little "optimization" crept into alloc_bts_buffer() along the way, > which now places bts_interrupt_threshold not on a record boundary. > And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says > "This address must

RE: [bug] kpti, perf_event, bts: sporadic truncated trace

2018-07-13 Thread Metzger, Markus T
Hello Hugh, > A little "optimization" crept into alloc_bts_buffer() along the way, which now > places bts_interrupt_threshold not on a record boundary. > And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says "This > address must point to an offset from the BTS buffer base that is a

RE: [bug] kpti, perf_event, bts: sporadic truncated trace

2018-07-13 Thread Metzger, Markus T
Hello Hugh, > A little "optimization" crept into alloc_bts_buffer() along the way, which now > places bts_interrupt_threshold not on a record boundary. > And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says "This > address must point to an offset from the BTS buffer base that is a

Re: [bug] kpti, perf_event, bts: sporadic truncated trace

2018-07-12 Thread Hugh Dickins
On Thu, 12 Jul 2018, Metzger, Markus T wrote: > Hello, > > Starting with 4.15 I noticed that BTS is sporadically missing the tail > of the trace in the perf_event data buffer. It shows as > > [decode error (1): instruction overflow] > > in GDB. Chances to see this are higher the longer

Re: [bug] kpti, perf_event, bts: sporadic truncated trace

2018-07-12 Thread Hugh Dickins
On Thu, 12 Jul 2018, Metzger, Markus T wrote: > Hello, > > Starting with 4.15 I noticed that BTS is sporadically missing the tail > of the trace in the perf_event data buffer. It shows as > > [decode error (1): instruction overflow] > > in GDB. Chances to see this are higher the longer

Re: [bug] kpti, perf_event, bts: sporadic truncated trace

2018-07-12 Thread Andi Kleen
"Metzger, Markus T" writes: Adding Dave Hansen > Hello, > > Starting with 4.15 I noticed that BTS is sporadically missing the tail > of the trace in the perf_event data buffer. It shows as > > [decode error (1): instruction overflow] > > in GDB. Chances to see this are higher the longer

Re: [bug] kpti, perf_event, bts: sporadic truncated trace

2018-07-12 Thread Andi Kleen
"Metzger, Markus T" writes: Adding Dave Hansen > Hello, > > Starting with 4.15 I noticed that BTS is sporadically missing the tail > of the trace in the perf_event data buffer. It shows as > > [decode error (1): instruction overflow] > > in GDB. Chances to see this are higher the longer