From: Alistair Francis <alistair23@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PULL 00/11] riscv-to-apply queue
Date: Thu, 31 Jul 2025 14:36:43 +1000 [thread overview]
Message-ID: <CAKmqyKN9mnd16FCJhEUoVAbHz1++-C2MmFG_ocT+aidj=9SuiQ@mail.gmail.com> (raw)
In-Reply-To: <e4578b16-a23e-4e56-ac72-3e65b8fbae53@tls.msk.ru>
On Thu, Jul 31, 2025 at 4:20 AM Michael Tokarev <mjt@tls.msk.ru> wrote:
>
> On 30.07.2025 04:01, alistair23@gmail.com wrote:
> > From: Alistair Francis <alistair.francis@wdc.com>
> >
> > The following changes since commit 9b80226ece693197af8a981b424391b68b5bc38e:
> >
> > Update version for the v10.1.0-rc1 release (2025-07-29 13:00:41 -0400)
> >
> > are available in the Git repository at:
> >
> > https://github.com/alistair23/qemu.git tags/pull-riscv-to-apply-20250730-2
> >
> > for you to fetch changes up to 86bc3a0abf10072081cddd8dff25aa72c60e67b8:
> >
> > target/riscv: Restrict midelegh access to S-mode harts (2025-07-30 10:59:26 +1000)
> >
> > ----------------------------------------------------------------
> > Third RISC-V PR for 10.1
> >
> > * Fix pmp range wraparound on zero
> > * Update FADT and MADT versions in ACPI tables
> > * Fix target register read when source is inactive
> > * Add riscv_hwprobe entry to linux-user strace list
> > * Do not call GETPC() in check_ret_from_m_mode()
> > * Revert "Generate strided vector loads/stores with tcg nodes."
> > * Fix exception type when VU accesses supervisor CSRs
> > * Restrict mideleg/medeleg/medelegh access to S-mode harts
> > * Restrict midelegh access to S-mode harts
> >
> > ----------------------------------------------------------------
> > Daniel Henrique Barboza (3):
> > linux-user/strace.list: add riscv_hwprobe entry
> > target/riscv: do not call GETPC() in check_ret_from_m_mode()
> > riscv: Revert "Generate strided vector loads/stores with tcg nodes."
> >
> > Jay Chang (2):
> > target/riscv: Restrict mideleg/medeleg/medelegh access to S-mode harts
> > target/riscv: Restrict midelegh access to S-mode harts
> >
> > Sunil V L (3):
> > bios-tables-test-allowed-diff.h: Allow RISC-V FADT and MADT changes
> > hw/riscv/virt-acpi-build.c: Update FADT and MADT versions
> > tests/data/acpi/riscv64: Update expected FADT and MADT
> >
> > Vac Chen (1):
> > target/riscv: Fix pmp range wraparound on zero
> >
> > Xu Lu (1):
> > target/riscv: Fix exception type when VU accesses supervisor CSRs
> >
> > Yang Jialong (1):
> > intc/riscv_aplic: Fix target register read when source is inactive
>
> Is there anything there for qemu-stable?
Urgh, sorry I forgot to CC qemu-stable.
>
> It looks like "Fix exception type when VU accesses supervisor CSRs" is a
> good candidate, maybe "Fix pmp range wraparound on zero" too. Something
> else? "Fix target register read when source is inactive"? The "S-mode
> harts" ones?
>
> I already picked up "do not call GETPC()" as it's been Cc'd qemu-stable
> before, and I'm picking up riscv_hwprobe too, as it's trivial and fixes
> a trivial omission which might be useful. Should I pick up others I
> mentioned?
Thanks for getting those two
77707bfdf8 target/riscv: Fix pmp range wraparound on zero
b6f1244678 intc/riscv_aplic: Fix target register read when source is inactive
30ef718423 target/riscv: Fix exception type when VU accesses supervisor CSRs
e443ba0336 target/riscv: Restrict mideleg/medeleg/medelegh access to
S-mode harts
86bc3a0abf target/riscv: Restrict midelegh access to S-mode harts
Are all good candidates for back porting as well
Alistair
>
> Thanks,
>
> /mjt
next prev parent reply other threads:[~2025-07-31 4:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 1:01 [PULL 00/11] riscv-to-apply queue alistair23
2025-07-30 1:01 ` [PULL 01/11] target/riscv: Fix pmp range wraparound on zero alistair23
2025-07-30 1:01 ` [PULL 02/11] bios-tables-test-allowed-diff.h: Allow RISC-V FADT and MADT changes alistair23
2025-07-30 1:01 ` [PULL 03/11] hw/riscv/virt-acpi-build.c: Update FADT and MADT versions alistair23
2025-07-30 1:01 ` [PULL 04/11] tests/data/acpi/riscv64: Update expected FADT and MADT alistair23
2025-07-30 1:01 ` [PULL 05/11] intc/riscv_aplic: Fix target register read when source is inactive alistair23
2025-07-30 1:01 ` [PULL 06/11] linux-user/strace.list: add riscv_hwprobe entry alistair23
2025-07-30 1:01 ` [PULL 07/11] target/riscv: do not call GETPC() in check_ret_from_m_mode() alistair23
2025-07-30 1:01 ` [PULL 08/11] riscv: Revert "Generate strided vector loads/stores with tcg nodes." alistair23
2025-07-30 1:01 ` [PULL 09/11] target/riscv: Fix exception type when VU accesses supervisor CSRs alistair23
2025-07-30 1:01 ` [PULL 10/11] target/riscv: Restrict mideleg/medeleg/medelegh access to S-mode harts alistair23
2025-07-30 1:01 ` [PULL 11/11] target/riscv: Restrict midelegh " alistair23
2025-07-30 1:04 ` [PULL 00/11] riscv-to-apply queue Alistair Francis
2025-07-30 15:15 ` Stefan Hajnoczi
2025-07-30 18:19 ` Michael Tokarev
2025-07-31 4:36 ` Alistair Francis [this message]
2025-07-31 6:11 ` Michael Tokarev
-- strict thread matches above, loose matches on Subject: below --
2021-07-12 22:53 Alistair Francis
2021-07-13 18:00 ` Peter Maydell
2021-07-15 6:56 ` Alistair Francis
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='CAKmqyKN9mnd16FCJhEUoVAbHz1++-C2MmFG_ocT+aidj=9SuiQ@mail.gmail.com' \
--to=alistair23@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=mjt@tls.msk.ru \
--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).