From: Warner Losh <imp@bsdimp.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Ilya Leoshkevich <iii@linux.ibm.com>,
Kyle Evans <kevans@freebsd.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] bsd-user/x86_64/target_arch_thread.h: Align stack
Date: Wed, 31 Jul 2024 17:18:44 -0600 [thread overview]
Message-ID: <CANCZdfrPcW+ZmjBCAOo9npmZavGfP5ZcGP08UZ-4vxPSE6Czuw@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfrdXguv_Ynm24dW4d_LY1kDEbHGwQhADFjuPrEuRSiF3w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2260 bytes --]
On Wed, Jul 31, 2024 at 5:03 PM Warner Losh <imp@bsdimp.com> wrote:
> Hmmm... All platforms likely need this....
> Oh, they all have it except x86, both 32 and 64-bit.... but i386 is
> already properly aligned (at least in the
> FreeBSD kernel), so maybe that's not needed.
>
>
> On Wed, Jul 31, 2024 at 4:43 PM Richard Henderson <
> richard.henderson@linaro.org> wrote:
>
>> On 8/1/24 00:44, Ilya Leoshkevich wrote:
>> > bsd-user qemu-x86_64 almost immediately dies with:
>> >
>> > qemu: 0x4002201a68: unhandled CPU exception 0xd - aborting
>> >
>> > on FreeBSD 14.1-RELEASE. This is an instruction that requires
>> > alignment:
>> >
>> > (gdb) x/i 0x4002201a68
>> > 0x4002201a68: movaps %xmm0,-0x40(%rbp)
>> >
>> > and the argument is not aligned:
>> >
>> > (gdb) p/x env->regs[5]
>> > $1 = 0x822443b58
>> >
>> > A quick experiment shows that the userspace entry point expects
>> > misaligned rsp:
>> >
>> > (gdb) starti
>> > (gdb) p/x $rsp
>> > $1 = 0x7fffffffeaa8
>> >
>> > Emulate this behavior in bsd-user.
>> >
>> > Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
>> > ---
>> > bsd-user/x86_64/target_arch_thread.h | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/bsd-user/x86_64/target_arch_thread.h
>> b/bsd-user/x86_64/target_arch_thread.h
>> > index 52c28906d6d..25233443c14 100644
>> > --- a/bsd-user/x86_64/target_arch_thread.h
>> > +++ b/bsd-user/x86_64/target_arch_thread.h
>> > @@ -31,7 +31,7 @@ static inline void target_thread_init(struct
>> target_pt_regs *regs,
>> > struct image_info *infop)
>> > {
>> > regs->rax = 0;
>> > - regs->rsp = infop->start_stack;
>> > + regs->rsp = (infop->start_stack & ~0xfUL) - 8;
>>
>> The formula in sys/amd64/amd64/exec_machdep.c, exec_setregs is
>>
>> ((stack - 8) & ~0xful) + 8
>>
>> With that,
>> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>>
>
> Agreed.
>
> Reviewed-by: Warner Losh <imp@bsdimp.com>
>
> There's a *lot* that's missing on for amd64 emulation relative to the
> other platforms.
>
Forgot to mention that I've queued this change with Richard's suggested
modification.
Warner
[-- Attachment #2: Type: text/html, Size: 3439 bytes --]
prev parent reply other threads:[~2024-07-31 23:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 14:44 [PATCH] bsd-user/x86_64/target_arch_thread.h: Align stack Ilya Leoshkevich
2024-07-31 22:43 ` Richard Henderson
2024-07-31 23:03 ` Warner Losh
2024-07-31 23:18 ` Warner Losh [this message]
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=CANCZdfrPcW+ZmjBCAOo9npmZavGfP5ZcGP08UZ-4vxPSE6Czuw@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=iii@linux.ibm.com \
--cc=kevans@freebsd.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).