From: Alistair Francis <alistair23@gmail.com>
To: Bug 1859291 <1859291@bugs.launchpad.net>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Bug 1859291] [NEW] RISC-V incorrect exception generated
Date: Fri, 31 Jan 2020 17:24:41 -0800 [thread overview]
Message-ID: <CAKmqyKPnkfPCg3O6C3f80d6RRB_6UMGQjXni8OoFRVUq9=SNKg@mail.gmail.com> (raw)
In-Reply-To: <157875755996.2711.225801499083245592.malonedeb@soybean.canonical.com>
Do you have steps to reproduce this?
Alistair
On Sat, Jan 11, 2020 at 8:25 AM Teodori Serge <teodori.serge@gmail.com> wrote:
>
> Public bug reported:
>
> When using 'ecall' from supervisor mode, user exception is raised
> instead of supervisor exception. The problem is located under
> 'target/riscv/insn_trans/trans_priviledged.inc.c' in function 'static
> bool trans_ecall(DisasContext *ctx, arg_ecall *a)'. Best regards, Serge
> Teodori
>
> ** Affects: qemu
> Importance: Undecided
> Status: New
>
>
> ** Tags: risc-v
>
> --
> You received this bug notification because you are a member of qemu-
> devel-ml, which is subscribed to QEMU.
> https://bugs.launchpad.net/bugs/1859291
>
> Title:
> RISC-V incorrect exception generated
>
> Status in QEMU:
> New
>
> Bug description:
> When using 'ecall' from supervisor mode, user exception is raised
> instead of supervisor exception. The problem is located under
> 'target/riscv/insn_trans/trans_priviledged.inc.c' in function 'static
> bool trans_ecall(DisasContext *ctx, arg_ecall *a)'. Best regards,
> Serge Teodori
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1859291/+subscriptions
>
next prev parent reply other threads:[~2020-02-01 1:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-11 15:45 [Bug 1859291] [NEW] RISC-V incorrect exception generated Teodori Serge
2020-02-01 1:24 ` Alistair Francis [this message]
2020-02-01 1:31 ` [Bug 1859291] " Alistair Francis
2020-02-03 13:32 ` Teodori Serge
2020-02-03 13:34 ` Teodori Serge
2020-03-17 20:25 ` Alistair Francis
2021-05-02 18:22 ` Thomas Huth
2021-07-02 4:17 ` Launchpad Bug Tracker
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='CAKmqyKPnkfPCg3O6C3f80d6RRB_6UMGQjXni8OoFRVUq9=SNKg@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=1859291@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).