On 8/28/2018 9:32 PM, Steven Rostedt wrote:
On Tue, 28 Aug 2018 18:47:33 +0530
Sai Prakash Ranjan wrote:
On 8/27/2018 9:45 PM, Steven Rostedt wrote:
On Sat, 25 Aug 2018 12:54:07 +0530
Sai Prakash Ranjan wrote:
Ftrace does not trace __raw{read,write}{b,l,w,q}() functions. I am not
sure
On 8/28/2018 9:32 PM, Steven Rostedt wrote:
On Tue, 28 Aug 2018 18:47:33 +0530
Sai Prakash Ranjan wrote:
On 8/27/2018 9:45 PM, Steven Rostedt wrote:
On Sat, 25 Aug 2018 12:54:07 +0530
Sai Prakash Ranjan wrote:
Ftrace does not trace __raw{read,write}{b,l,w,q}() functions. I am not
sure
On Tue, 28 Aug 2018 18:47:33 +0530
Sai Prakash Ranjan wrote:
> On 8/27/2018 9:45 PM, Steven Rostedt wrote:
> > On Sat, 25 Aug 2018 12:54:07 +0530
> > Sai Prakash Ranjan wrote:
> >
> >
> >> Ftrace does not trace __raw{read,write}{b,l,w,q}() functions. I am not
> >> sure why and how it is
On Tue, 28 Aug 2018 18:47:33 +0530
Sai Prakash Ranjan wrote:
> On 8/27/2018 9:45 PM, Steven Rostedt wrote:
> > On Sat, 25 Aug 2018 12:54:07 +0530
> > Sai Prakash Ranjan wrote:
> >
> >
> >> Ftrace does not trace __raw{read,write}{b,l,w,q}() functions. I am not
> >> sure why and how it is
On 8/27/2018 9:45 PM, Steven Rostedt wrote:
On Sat, 25 Aug 2018 12:54:07 +0530
Sai Prakash Ranjan wrote:
Ftrace does not trace __raw{read,write}{b,l,w,q}() functions. I am not
sure why and how it is filtered out because I do not see any notrace
flag in those functions, maybe that whole
On 8/27/2018 9:45 PM, Steven Rostedt wrote:
On Sat, 25 Aug 2018 12:54:07 +0530
Sai Prakash Ranjan wrote:
Ftrace does not trace __raw{read,write}{b,l,w,q}() functions. I am not
sure why and how it is filtered out because I do not see any notrace
flag in those functions, maybe that whole
On Sat, 25 Aug 2018 12:54:07 +0530
Sai Prakash Ranjan wrote:
> Ftrace does not trace __raw{read,write}{b,l,w,q}() functions. I am not
> sure why and how it is filtered out because I do not see any notrace
> flag in those functions, maybe that whole directory is filtered out.
> So adding this
On Sat, 25 Aug 2018 12:54:07 +0530
Sai Prakash Ranjan wrote:
> Ftrace does not trace __raw{read,write}{b,l,w,q}() functions. I am not
> sure why and how it is filtered out because I do not see any notrace
> flag in those functions, maybe that whole directory is filtered out.
> So adding this
On 8/24/2018 8:59 PM, Kees Cook wrote:
On Fri, Aug 24, 2018 at 7:45 AM, Sai Prakash Ranjan
wrote:
read/write{b,w,l,q} are typically used for reading from memory
mapped registers, which can cause hangs if accessed
unclocked. Tracing these events can help in debugging
various issues faced during
On 8/24/2018 8:59 PM, Kees Cook wrote:
On Fri, Aug 24, 2018 at 7:45 AM, Sai Prakash Ranjan
wrote:
read/write{b,w,l,q} are typically used for reading from memory
mapped registers, which can cause hangs if accessed
unclocked. Tracing these events can help in debugging
various issues faced during
On Fri, Aug 24, 2018 at 7:45 AM, Sai Prakash Ranjan
wrote:
> read/write{b,w,l,q} are typically used for reading from memory
> mapped registers, which can cause hangs if accessed
> unclocked. Tracing these events can help in debugging
> various issues faced during initial development.
>
> We log
On Fri, Aug 24, 2018 at 7:45 AM, Sai Prakash Ranjan
wrote:
> read/write{b,w,l,q} are typically used for reading from memory
> mapped registers, which can cause hangs if accessed
> unclocked. Tracing these events can help in debugging
> various issues faced during initial development.
>
> We log
read/write{b,w,l,q} are typically used for reading from memory
mapped registers, which can cause hangs if accessed
unclocked. Tracing these events can help in debugging
various issues faced during initial development.
We log this trace information in persistent ram buffer which
can be viewed
read/write{b,w,l,q} are typically used for reading from memory
mapped registers, which can cause hangs if accessed
unclocked. Tracing these events can help in debugging
various issues faced during initial development.
We log this trace information in persistent ram buffer which
can be viewed
14 matches
Mail list logo