qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: Re: [Qemu-devel] [PATCH v2] target/xtensa: linux-user: add call0 ABI support
Date: Mon, 26 Aug 2019 12:53:07 -0700	[thread overview]
Message-ID: <CAMo8BfLu5aog_3WrHbN+75ARTa14ydwkM79RBLn=3r9m8o8FGA@mail.gmail.com> (raw)
In-Reply-To: <20190826181723.14008-1-jcmvbkbc@gmail.com>

On Mon, Aug 26, 2019 at 11:17 AM Max Filippov <jcmvbkbc@gmail.com> wrote:
>
> Xtensa binaries built for call0 ABI don't rotate register window on
> function calls and returns. Invocation of signal handlers from the
> kernel is therefore different in windowed and call0 ABIs.
> There's currently no way to determine xtensa ELF binary ABI from the
> binary itself. Add handler for the --xtensa-abi-call0 command line
> parameter/QEMU_XTENSA_ABI_CALL0 envitonment variable to the qemu-user
> and record ABI choice. Use it to initialize PS.WOE in xtensa_cpu_reset
> and in setup_rt_frame to determine how a signal should be delivered.
>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> Changes v1->v2:
>
> - move handling of QEMU_XTENSA_ABI_CALL0 to linux-user/main.c
> - check xtensa_abi_call0 instead of PS.WOE in the setup_rt_frame

Thought about it some more and decided that checking PS.WOE
was a better choice. Will send v3.

-- 
Thanks.
-- Max


      reply	other threads:[~2019-08-26 19:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26 18:17 [Qemu-devel] [PATCH v2] target/xtensa: linux-user: add call0 ABI support Max Filippov
2019-08-26 19:53 ` Max Filippov [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='CAMo8BfLu5aog_3WrHbN+75ARTa14ydwkM79RBLn=3r9m8o8FGA@mail.gmail.com' \
    --to=jcmvbkbc@gmail.com \
    --cc=laurent@vivier.eu \
    --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).