On Wed, 04 Sep 2019 08:13:58 -0500
Tom Zanussi wrote:
> Hi Steve,
>
> On Wed, 2019-09-04 at 06:43 -0400, Steven Rostedt wrote:
> > On Fri, 12 Jul 2019 11:05:06 -0500
> > Tom Zanussi wrote:
> >
> > > Hi Zhengjun,
> > >
> > > On Fri, 2019-07-12 at 09:53 +0800, Zhengjun Xing wrote:
> > > > A
Hi Steve,
On Wed, 2019-09-04 at 06:43 -0400, Steven Rostedt wrote:
> On Fri, 12 Jul 2019 11:05:06 -0500
> Tom Zanussi wrote:
>
> > Hi Zhengjun,
> >
> > On Fri, 2019-07-12 at 09:53 +0800, Zhengjun Xing wrote:
> > > Add "gfp_t" support in synthetic_events, then the "gfp_t" type
> > > parameter in
On Fri, 12 Jul 2019 11:05:06 -0500
Tom Zanussi wrote:
> Hi Zhengjun,
>
> On Fri, 2019-07-12 at 09:53 +0800, Zhengjun Xing wrote:
> > Add "gfp_t" support in synthetic_events, then the "gfp_t" type
> > parameter in some functions can be traced.
> >
> > Prints the gfp flags as hex in addition to t
Hi Steve,
On 8/13/2019 11:04 AM, Steven Rostedt wrote:
On Tue, 13 Aug 2019 09:04:28 +0800
Xing Zhengjun wrote:
Hi Steve,
Could you help to review? Thanks.
Thanks for the ping. Yes, I'll take a look at it. I'll be pulling in a
lot of patches that have queued up.
-- Steve
Could you
On Tue, 13 Aug 2019 09:04:28 +0800
Xing Zhengjun wrote:
> Hi Steve,
>
> Could you help to review? Thanks.
Thanks for the ping. Yes, I'll take a look at it. I'll be pulling in a
lot of patches that have queued up.
-- Steve
>
> On 7/13/2019 12:05 AM, Tom Zanussi wrote:
> > Hi Zhengjun,
>
Hi Steve,
Could you help to review? Thanks.
On 7/13/2019 12:05 AM, Tom Zanussi wrote:
Hi Zhengjun,
On Fri, 2019-07-12 at 09:53 +0800, Zhengjun Xing wrote:
Add "gfp_t" support in synthetic_events, then the "gfp_t" type
parameter in some functions can be traced.
Prints the gfp flags as hex
Hi Zhengjun,
On Fri, 2019-07-12 at 09:53 +0800, Zhengjun Xing wrote:
> Add "gfp_t" support in synthetic_events, then the "gfp_t" type
> parameter in some functions can be traced.
>
> Prints the gfp flags as hex in addition to the human-readable flag
> string. Example output:
>
> whoopsie-630
Add "gfp_t" support in synthetic_events, then the "gfp_t" type
parameter in some functions can be traced.
Prints the gfp flags as hex in addition to the human-readable flag
string. Example output:
whoopsie-630 [000] ...1 78.969452: testevent: bar=b20 (GFP_ATOMIC|__GFP_ZERO)
rcuc/0-11 [000
8 matches
Mail list logo