From: Richard Henderson <richard.henderson@linaro.org>
To: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Cc: laurent@vivier.eu
Subject: Re: [PATCH] linux-user/i386: Properly align signal frame
Date: Sat, 5 Aug 2023 19:29:45 -0700 [thread overview]
Message-ID: <da2bf153-151a-baf1-7e7b-ab5f8ba5b3cc@linaro.org> (raw)
In-Reply-To: <cca0a698-2ce6-dcfa-129c-4a205287e1ca@tls.msk.ru>
On 8/5/23 14:56, Michael Tokarev wrote:
> 30.06.2023 20:53, Richard Henderson wrote:
>> Ping 2.
>>
>> On 6/20/23 15:26, Richard Henderson wrote:
>>> Ping.
>>>
>>> On 5/24/23 07:46, Richard Henderson wrote:
>>>> The beginning of the structure, with pretaddr, should be just below
>>>> 16-byte alignment. Disconnect fpstate from sigframe, just like the
>>>> kernel does.
>
> Whom we're pinging here? :)
> Ping 3 ;)
>
> (This is https://gitlab.com/qemu-project/qemu/-/issues/1648 and is a
> -stable material too, it seems)
In the month since, I've discovered that fpstate needs even more work.
This is extremely fiddly stuff, and we need a complete rewrite to match the kernel and the
required alignments.
r~
next prev parent reply other threads:[~2023-08-06 2:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 5:46 [PATCH] linux-user/i386: Properly align signal frame Richard Henderson
2023-05-24 5:50 ` Richard Henderson
2023-05-26 2:56 ` fanwj--- via
2023-05-26 14:27 ` Richard Henderson
2023-06-20 13:26 ` Richard Henderson
2023-06-30 17:53 ` Richard Henderson
2023-07-02 18:41 ` Michael Tokarev
2023-08-05 21:56 ` Michael Tokarev
2023-08-06 2:29 ` Richard Henderson [this message]
2023-10-26 6:35 ` Michael Tokarev
2023-10-27 4:07 ` Richard Henderson
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=da2bf153-151a-baf1-7e7b-ab5f8ba5b3cc@linaro.org \
--to=richard.henderson@linaro.org \
--cc=laurent@vivier.eu \
--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).