On Thu, Mar 03, 2016 at 02:14:29PM +, Mark Rutland wrote:
> On Wed, Mar 02, 2016 at 02:26:18PM +, Mark Rutland wrote:
> > Functions which the compiler has instrumented for ASAN place poison on
> > the stack shadow upon entry and remove this poison prior to returning.
> >
> > In the case
On Thu, Mar 03, 2016 at 02:14:29PM +, Mark Rutland wrote:
> On Wed, Mar 02, 2016 at 02:26:18PM +, Mark Rutland wrote:
> > Functions which the compiler has instrumented for ASAN place poison on
> > the stack shadow upon entry and remove this poison prior to returning.
> >
> > In the case
On Wed, Mar 02, 2016 at 02:26:18PM +, Mark Rutland wrote:
> Functions which the compiler has instrumented for ASAN place poison on
> the stack shadow upon entry and remove this poison prior to returning.
>
> In the case of cpuidle, CPUs exit the kernel a number of levels deep
> in C code. Any
On Wed, Mar 02, 2016 at 02:26:18PM +, Mark Rutland wrote:
> Functions which the compiler has instrumented for ASAN place poison on
> the stack shadow upon entry and remove this poison prior to returning.
>
> In the case of cpuidle, CPUs exit the kernel a number of levels deep
> in C code. Any
Functions which the compiler has instrumented for ASAN place poison on
the stack shadow upon entry and remove this poison prior to returning.
In the case of cpuidle, CPUs exit the kernel a number of levels deep
in C code. Any instrumented functions on this critical path will leave
portions of the
Functions which the compiler has instrumented for ASAN place poison on
the stack shadow upon entry and remove this poison prior to returning.
In the case of cpuidle, CPUs exit the kernel a number of levels deep
in C code. Any instrumented functions on this critical path will leave
portions of the
6 matches
Mail list logo
