From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Leo Yan <leo.yan@linaro.org>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Peter Zijlstra <peterz@infradead.org>,
John Garry <john.garry@huawei.com>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Suleiman Souhlal <suleiman@google.com>,
Namhyung Kim <namhyung@kernel.org>, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCHv2] perf kvm: add kvm-stat for arm64
Date: Wed, 16 Sep 2020 17:00:51 +0900 [thread overview]
Message-ID: <20200916080051.GF604@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <20200916075154.GA13660@leoy-ThinkPad-X240s>
On (20/09/16 15:51), Leo Yan wrote:
> On Wed, Sep 16, 2020 at 09:44:04AM +0900, Sergey Senozhatsky wrote:
> > On (20/09/15 21:21), Leo Yan wrote:
> > >
> > > Sorry if I miss anything for this.
> > >
> >
> > No, you are absolutely right! I should have looked more attentively.
> >
> > Is "IL" good enough for a decoded reason
> >
> > {ARM_EXCEPTION_IRQ, "IRQ" }, \
> > {ARM_EXCEPTION_EL1_SERROR, "SERROR" }, \
> > {ARM_EXCEPTION_TRAP, "TRAP" }, \
> > + {ARM_EXCEPTION_IL, "IL" }, \
> > {ARM_EXCEPTION_HYP_GONE, "HYP_GONE" }
> >
> > or should there be "ILLEGAL", or maybe something even better?
> > ILLEGAL_EXC, etc.
>
> I personally think "ILLEGAL" is neat and clear :)
OK.
By the way, arch/arm64/kernel/traps.c has esr_class_str[] with
decoded exception names. Maybe I can reuse some.
-ss
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-09-16 8:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 9:11 [PATCHv2] perf kvm: add kvm-stat for arm64 Sergey Senozhatsky
2020-09-15 10:36 ` Leo Yan
2020-09-15 10:57 ` Sergey Senozhatsky
2020-09-15 11:15 ` Sergey Senozhatsky
2020-09-15 13:21 ` Leo Yan
2020-09-16 0:44 ` Sergey Senozhatsky
2020-09-16 7:51 ` Leo Yan
2020-09-16 8:00 ` Sergey Senozhatsky [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=20200916080051.GF604@jagdpanzerIV.localdomain \
--to=sergey.senozhatsky@gmail.com \
--cc=john.garry@huawei.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=suleiman@google.com \
--cc=will@kernel.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