From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Huacai Chen <chenhc@lemote.com>
Cc: "open list:MIPS" <linux-mips@vger.kernel.org>,
Fuxin Zhang <zhangfx@lemote.com>,
Zhangjin Wu <wuzhangjin@gmail.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Subject: Re: [PATCH V2] MIPS: perf: Add hardware perf events support for new Loongson-3
Date: Thu, 30 Apr 2020 10:13:57 +0200 [thread overview]
Message-ID: <20200430081357.GA7626@alpha.franken.de> (raw)
In-Reply-To: <CAAhV-H6j9ktHZ2C2Psk6X+0jmh-L9GMgOmKM95x0iXHo0d7TqA@mail.gmail.com>
On Thu, Apr 30, 2020 at 03:30:55PM +0800, Huacai Chen wrote:
> Hi, Thomas,
>
> On Thu, Apr 30, 2020 at 2:33 AM Thomas Bogendoerfer
> <tsbogend@alpha.franken.de> wrote:
> >
> > On Wed, Apr 29, 2020 at 03:26:10PM +0800, Huacai Chen wrote:
> > > New Loongson-3 means Loongson-3A R2 (Loongson-3A2000) and newer CPUs.
> > > Loongson-3 processors have three types of PMU types (so there are three
> > > event maps): Loongson-3A1000/Loonngson-3B1000/Loongson-3B1500 is Type-1,
> > > Loongson-3A2000/Loongson-3A3000 is Type-2, Loongson-3A4000+ is Type-3.
> > >
> > > Signed-off-by: Huacai Chen <chenhc@lemote.com>
> > > ---
> > > .../asm/mach-loongson64/cpu-feature-overrides.h | 1 +
> > > arch/mips/kernel/perf_event_mipsxx.c | 358 +++++++++++++++++++--
> >
> > checkpatch warns about missing break/fallthrough statement and indention
> > problems, could please look at this ? And as all the new code is only
> > usefull for loongsoon CPUs could you try to only compile it in, if it's
> > enabled for the image ?
> OK, I will solve the "fallthrough" warnings and indention warnings.
> But the other problem is I should use #ifdef CONFIG_CPU_LOONGSON64 to
> guard all new code in this file? I remember that Paul Burton suggest
> us to avoid use #ifdef and use runtime detection instead.
if you do the cpu checks for current_cpu_type() == CPU_LOONGSON64
the compiler will eliminate not needed cpu code. Looks like most
of the new code is done inside case CPU_LOONGSON64 blocks, so
that is fine. Could you check how much size increase you get for
a non loongson64 target with your patch ?
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2020-04-30 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 7:26 [PATCH V2] MIPS: perf: Add hardware perf events support for new Loongson-3 Huacai Chen
2020-04-29 18:22 ` Thomas Bogendoerfer
2020-04-30 7:30 ` Huacai Chen
2020-04-30 8:13 ` Thomas Bogendoerfer [this message]
2020-04-30 9:42 ` Huacai Chen
2020-04-30 15:10 ` Thomas Bogendoerfer
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=20200430081357.GA7626@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=chenhc@lemote.com \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-mips@vger.kernel.org \
--cc=wuzhangjin@gmail.com \
--cc=zhangfx@lemote.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.