From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: kajoljain <kjain@linux.ibm.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
maddy@linux.vnet.ibm.com, atrajeev@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, ravi.bangoria@linux.ibm.com,
linux-perf-users@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
rnsastry@linux.ibm.com, "Paul A. Clarke" <pc@us.ibm.com>
Subject: Re: [PATCH] perf script python: Fix buffer size to report iregs in perf script
Date: Wed, 7 Jul 2021 11:04:49 -0300 [thread overview]
Message-ID: <YOW0gU4yNpgN8MjB@kernel.org> (raw)
In-Reply-To: <d59266da-2aa6-69ff-646b-144ba874ee2f@linux.ibm.com>
Em Wed, Jul 07, 2021 at 11:16:20AM +0530, kajoljain escreveu:
> On 7/7/21 12:45 AM, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Jul 06, 2021 at 05:26:12PM +0530, kajoljain escreveu:
> >> On 6/29/21 12:39 PM, kajoljain wrote:
> >>> On 6/28/21 8:19 PM, Paul A. Clarke wrote:
> >>>> On Mon, Jun 28, 2021 at 11:53:41AM +0530, Kajol Jain wrote:
> >>>>> @@ -713,7 +711,16 @@ static void set_regs_in_dict(PyObject *dict,
> >>>>> struct evsel *evsel)
> >>>>> {
> >>>>> struct perf_event_attr *attr = &evsel->core.attr;
> >>>>> - char bf[512];
> >>>>> +
> >>>>> + /*
> >>>>> + * Here value 28 is a constant size which can be used to print
> >>>>> + * one register value and its corresponds to:
> >>>>> + * 16 chars is to specify 64 bit register in hexadecimal.
> >>>>> + * 2 chars is for appending "0x" to the hexadecimal value and
> >>>>> + * 10 chars is for register name.
> >>>>> + */
> >>>>> + int size = __sw_hweight64(attr->sample_regs_intr) * 28;
> >>>>> + char bf[size];
> >>>> I propose using a template rather than a magic number here. Something like:
> >>>> const char reg_name_tmpl[] = "10 chars ";
> >>>> const char reg_value_tmpl[] = "0x0123456789abcdef";
> >>>> const int size = __sw_hweight64(attr->sample_regs_intr) +
> >>>> sizeof reg_name_tmpl + sizeof reg_value_tmpl;
> >>> Thanks for reviewing the patch. Yes these are
> >>> some standardization we can do by creating macros for different
> >>> fields.
> >>> The basic idea is, we want to provide significant buffer size
> >>> based on number of registers present in sample_regs_intr to accommodate
> >>> all data.
> >> Is the approach used in this patch looks fine to you?
> > Yeah, and the comment you provide right above it explains it, so I think
> > that is enough, ok?
> Thanks for reviewing it. As you said added comment already explains
> why we are taking size constant as 28, should we skip adding macros part?
> Can you pull this patch.
Sure.
- Arnaldo
prev parent reply other threads:[~2021-07-07 14:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 6:23 [PATCH] perf script python: Fix buffer size to report iregs in perf script Kajol Jain
2021-06-28 7:15 ` Nageswara Sastry
2021-06-28 14:49 ` Paul A. Clarke
2021-06-29 7:09 ` kajoljain
2021-07-06 11:56 ` kajoljain
2021-07-06 19:15 ` Arnaldo Carvalho de Melo
2021-07-07 5:46 ` kajoljain
2021-07-07 14:04 ` Arnaldo Carvalho de Melo [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=YOW0gU4yNpgN8MjB@kernel.org \
--to=acme@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=jolsa@redhat.com \
--cc=kjain@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=pc@us.ibm.com \
--cc=ravi.bangoria@linux.ibm.com \
--cc=rnsastry@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).