From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ravi Bangoria <ravi.bangoria@amd.com>
Cc: mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, yao.jin@linux.intel.com, namhyung@kernel.org,
kim.phillips@amd.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] perf annotate: Add fusion logic for AMD microarchs
Date: Fri, 10 Sep 2021 11:19:02 -0300 [thread overview]
Message-ID: <YTtpVpo3d/h5YkVc@kernel.org> (raw)
In-Reply-To: <6a987cad-6c46-280e-f791-6c59b6628a45@amd.com>
Em Fri, Sep 10, 2021 at 04:47:31PM +0530, Ravi Bangoria escreveu:
>
> >> +static bool x86__ins_is_fused(struct arch *arch, const char *ins1,
> >> + const char *ins2)
> >> +{
> >> + if (strstarts(arch->vendor, "AuthenticAMD"))
> >> + return amd__ins_is_fused(arch, ins1, ins2);
> >> +
> >> + return intel__ins_is_fused(arch, ins1, ins2);
> >> +}
> >> +
> >
> > Can we instead make x86__ins_is_fused be a pointer and instead of
> > storing arch->vendor we set it to one of amd__ins_is_fused() or
> > intel__ins_is_fused()?
> >
> > I.e. here:
> >
> >> static int x86__cpuid_parse(struct arch *arch, char *cpuid)
> >> {
> >> unsigned int family, model, stepping;
> >> @@ -184,6 +216,9 @@ static int x86__cpuid_parse(struct arch *arch, char *cpuid)
> >> if (ret == 3) {
> >> arch->family = family;
> >> arch->model = model;
> >> + arch->vendor = strndup(cpuid, 12);
> >
> > x86__ins_is_fused = strstarts(cpuid, "AuthenticAMD") ?
> > amd__ins_is_fused :
> > intel__ins_is_fused;
>
> Sure. Will post v2.
Thanks, if you're quick we may get this into this merge window :-)
> Thanks for the review Arnaldo,
- Arnaldo
next prev parent reply other threads:[~2021-09-10 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 10:56 [PATCH 1/2] perf annotate: Fix fused instr logic for assembly functions Ravi Bangoria
2021-09-06 10:56 ` [PATCH 2/2] perf annotate: Add fusion logic for AMD microarchs Ravi Bangoria
2021-09-09 20:32 ` Arnaldo Carvalho de Melo
2021-09-10 11:17 ` Ravi Bangoria
2021-09-10 14:19 ` Arnaldo Carvalho de Melo [this message]
2021-09-11 4:42 ` Ravi Bangoria
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=YTtpVpo3d/h5YkVc@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=kim.phillips@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@amd.com \
--cc=yao.jin@linux.intel.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).