From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: LIU Zhiwei <baxiantai@gmail.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
"open list:RISC-V" <qemu-riscv@nongnu.org>
Cc: Michael Tokarev <mjt@tls.msk.ru>
Subject: Re: qemu-riscv32 usermode still broken?
Date: Wed, 13 Sep 2023 12:33:49 +0200 [thread overview]
Message-ID: <5225193.mvXUDI8C0e@kona> (raw)
In-Reply-To: <b065fa54-28fc-d64e-c8dd-16104128326d@tls.msk.ru>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
Am Mittwoch, 13. September 2023, 10:06:01 CEST schrieb Michael Tokarev:
> 13.09.2023 04:41, LIU Zhiwei wrote:
> >
> > On 2023/9/13 6:31, Andreas K. Huettel wrote:
> ..
> >> * Something seems wrong in the signal handling (?):
> >
> > If it is wrong for signal handling and for 32-bit, I guess it may be fixed by this patch
> >
> > https://www.mail-archive.com/qemu-devel@nongnu.org/msg981238.html
> >
> > And this patch has been merged into master branch yesterday.
>
> I picked this one up for stable yesterday, scheduled to be released
> on Sep-21.
Oh great, thanks! I'll test this and report back.
-a
>
> Thanks,
>
> /mjt
>
>
>
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2023-09-13 10:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 22:31 qemu-riscv32 usermode still broken? Andreas K. Huettel
2023-09-13 1:41 ` LIU Zhiwei
2023-09-13 8:06 ` Michael Tokarev
2023-09-13 10:33 ` Andreas K. Huettel [this message]
2023-09-14 1:22 ` Andreas K. Huettel
2023-09-16 22:37 ` Andreas K. Huettel
2023-09-18 1:16 ` Alistair Francis
2023-09-19 20:39 ` Andreas K. Huettel
2024-06-11 4:43 ` Alistair Francis
2024-06-11 8:57 ` Andreas K. Huettel
2024-06-12 1:26 ` 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=5225193.mvXUDI8C0e@kona \
--to=dilfridge@gentoo.org \
--cc=baxiantai@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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).