On Fri, 18 Oct 2019 09:41:05 -0500
"Zanussi, Tom" wrote:
> Reviewed-by: Tom Zanussi
Thanks Zhengjun and Tom!
I'll apply this to my urgent branch and get it upstream (even though
it's a minor fix).
-- Steve
On 10/17/2019 8:20 PM, Zhengjun Xing wrote:
In the format of synthetic events, the "gfp_t" is shown as "signed:1",
but in fact the "gfp_t" is "unsigned", should be shown as "signed:0".
The issue can be reproduced by the following commands:
echo 'memlatency u64 lat; unsigned int order; gfp_t
On Fri, 18 Oct 2019 09:20:34 +0800
Zhengjun Xing wrote:
> In the format of synthetic events, the "gfp_t" is shown as "signed:1",
> but in fact the "gfp_t" is "unsigned", should be shown as "signed:0".
>
> The issue can be reproduced by the following commands:
>
> echo 'memlatency u64 lat; unsig
In the format of synthetic events, the "gfp_t" is shown as "signed:1",
but in fact the "gfp_t" is "unsigned", should be shown as "signed:0".
The issue can be reproduced by the following commands:
echo 'memlatency u64 lat; unsigned int order; gfp_t gfp_flags; int migratetype'
> /sys/kernel/debug/
4 matches
Mail list logo
