From: Jonathan Behrens <jonathan@fintelia.io>
To: Alistair Francis <alistair23@gmail.com>
Cc: "open list:RISC-V" <qemu-riscv@nongnu.org>,
"Sagar Karandikar" <sagark@eecs.berkeley.edu>,
"Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>,
"Palmer Dabbelt" <palmer@sifive.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Alistair Francis" <Alistair.Francis@wdc.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v2] target/riscv: Expose "priv" register for GDB
Date: Mon, 7 Oct 2019 20:22:47 -0400 [thread overview]
Message-ID: <CANnJOVGDcGrM5FY12GBurSTWWD++EKdrkUB5o-ZEOPsBm8RhQg@mail.gmail.com> (raw)
In-Reply-To: <CAKmqyKPFuyuC6sGCRGJGo2f_3=2z33MmuXHZov5R0pc7A9O9Jg@mail.gmail.com>
On Mon, Oct 7, 2019 at 2:36 PM Alistair Francis <alistair23@gmail.com> wrote:
> On Fri, Oct 4, 2019 at 8:18 AM Jonathan Behrens <jonathan@fintelia.io> wrote:
> > @@ -296,6 +302,14 @@ int riscv_cpu_gdb_write_register(CPUState *cs, uint8_t *mem_buf, int n)
> > } else if (n == 32) {
> > env->pc = ldtul_p(mem_buf);
> > return sizeof(target_ulong);
> > + } else if (n == 33) {
> > +#ifndef CONFIG_USER_ONLY
> > + env->priv = ldtul_p(mem_buf) & 0x3;
> > + if (env->priv == PRV_H) {
> > + env->priv = PRV_S;
> > + }
>
> Why have this? There is no PRV_H so we should never be in that privilege mode.
>
> Alistair
This is hopefully more clear in the next version, but the idea is that
since GDB can try to set the privilege mode to *any* value this
function needs to make sure that it isn't set to something unsupported
like PRV_H.
Jonathan
next prev parent reply other threads:[~2019-10-08 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 15:16 [PATCH v2] target/riscv: Expose "priv" register for GDB Jonathan Behrens
2019-10-05 12:08 ` Bin Meng
2019-10-07 18:31 ` Alistair Francis
2019-10-08 0:22 ` Jonathan Behrens [this message]
2019-10-07 21:16 ` Jim Wilson
2019-10-08 0:19 ` Jonathan Behrens
2019-10-08 9:00 ` Bin Meng
2019-10-08 16:42 ` Jim Wilson
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=CANnJOVGDcGrM5FY12GBurSTWWD++EKdrkUB5o-ZEOPsBm8RhQg@mail.gmail.com \
--to=jonathan@fintelia.io \
--cc=Alistair.Francis@wdc.com \
--cc=alex.bennee@linaro.org \
--cc=alistair23@gmail.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=palmer@sifive.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=sagark@eecs.berkeley.edu \
/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).