From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Li, Kevin" <cnkevin@amazon.com>
Cc: qemu-devel@nongnu.org, Richard Henderson <richard.henderson@linaro.org>
Subject: Re: Questions about QEMU exception
Date: Wed, 09 Nov 2022 10:00:18 +0000 [thread overview]
Message-ID: <87h6z8e90i.fsf@linaro.org> (raw)
In-Reply-To: <6FE4D6CD-1F6C-4632-92ED-9233C8F0EB87@amazon.com>
"Li, Kevin" <cnkevin@amazon.com> writes:
> Hi qemu community,
>
>
>
> We are working on some open source project which uses qemu on mac, and we have some signing process to sign
> qemu-system-x86_64.
>
> If qemu-system-x86_64 is not signed, we don’t see any problem, but after sign it, we got the following error:
>
>
>
> qemu-system-x86_64 -M none -netdev help]: stdout=\"Accelerators supported in QEMU binary:\\ntcg\\nhax\\nhvf\\n\",
> stderr=\"qemu-system-x86_64: allocate 1073741824 bytes for jit buffer: Invalid argument
>
>
>
> Does anyone has clue about what change may result in this failure?
Not sure about the details but I suspect this is something to do with
the way we have to jump through hoops to allocate the code buffer on
MacOSX.
You could stick some printfs around:
alloc_code_gen_buffer_splitwx_vmremap
and
alloc_code_gen_buffer_anon
AIUI we have to allocate a non-executable but writable buffer for the
code and then remap an executable view of the same region to execute the
generated JIT code. Maybe being a signed binary adds more restrictions
on which OS apis can be called?
--
Alex Bennée
next prev parent reply other threads:[~2022-11-09 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 1:45 Questions about QEMU exception Li, Kevin
2022-11-09 10:00 ` Alex Bennée [this message]
2022-11-09 10:10 ` Peter Maydell
2022-11-09 17:35 ` Li, Kevin
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=87h6z8e90i.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=cnkevin@amazon.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.