From: "Zanussi, Tom" <tom.zanussi@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Artem Bityutskiy <dedekind1@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] trace/synthetic_events: increase SYNTH_FIELDS_MAX
Date: Fri, 15 Nov 2019 10:21:05 -0600 [thread overview]
Message-ID: <8751ffdd-ea8c-4aa5-663d-0d7d0fd0886d@linux.intel.com> (raw)
In-Reply-To: <20191115105227.341c238e@gandalf.local.home>
Hi Steve and Artem,
On 11/15/2019 9:52 AM, Steven Rostedt wrote:
> On Fri, 15 Nov 2019 11:17:30 +0200
> Artem Bityutskiy <dedekind1@gmail.com> wrote:
>
>> From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
>>
>> Increase the maximum allowed count of synthetic event fields from 16 to 32
>> in order to allow for larger-than-usual events.
>
> I'm fine with this, Tom are you OK with it?
Yeah, looks good to me. Thanks for the patch, Artem.
Reviewed-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Tom
>
> -- Steve
>
>>
>> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
>> ---
>> kernel/trace/trace_events_hist.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
>> index 7482a1466ebf..f49d1a36d3ae 100644
>> --- a/kernel/trace/trace_events_hist.c
>> +++ b/kernel/trace/trace_events_hist.c
>> @@ -23,7 +23,7 @@
>> #include "trace_dynevent.h"
>>
>> #define SYNTH_SYSTEM "synthetic"
>> -#define SYNTH_FIELDS_MAX 16
>> +#define SYNTH_FIELDS_MAX 32
>>
>> #define STR_VAR_LEN_MAX 32 /* must be multiple of sizeof(u64) */
>>
>
prev parent reply other threads:[~2019-11-15 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 9:17 [PATCH] trace/synthetic_events: increase SYNTH_FIELDS_MAX Artem Bityutskiy
2019-11-15 15:52 ` Steven Rostedt
2019-11-15 16:21 ` Zanussi, Tom [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8751ffdd-ea8c-4aa5-663d-0d7d0fd0886d@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox