From: "John Högberg" <john.hogberg@ericsson.com>
To: "mjt@tls.msk.ru" <mjt@tls.msk.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>
Subject: Re: [PATCH 1/2] target/arm: Handle IC IVAU to improve compatibility with JITs
Date: Sun, 11 Jun 2023 17:31:36 +0000 [thread overview]
Message-ID: <e9c30eedbc07c9a9e3e9e433435ee1dba0e9d47a.camel@ericsson.com> (raw)
In-Reply-To: <baa7eed9-8e39-f454-bad0-e6934ccd0778@tls.msk.ru>
Sorry, something went sideways on my end. I'll try re-sending the
patchset tomorrow through the web-based interface mentioned in the
documentation, hopefully that will be foolproof. :)
Regards,
John Högberg
-----Original Message-----
From: Michael Tokarev <mjt@tls.msk.ru>
To: John Högberg <john.hogberg@ericsson.com>, qemu-devel@nongnu.org <qemu-devel@nongnu.org>
Cc: peter.maydell@linaro.org <peter.maydell@linaro.org>
Subject: Re: [PATCH 1/2] target/arm: Handle IC IVAU to improve compatibility with JITs
Date: Sun, 11 Jun 2023 19:47:58 +0300
11.06.2023 14:53, John Högberg wrote:
...
>
> +#ifdef CONFIG_USER_ONLY
> +/*
> + * `IC IVAU` is handled to improve compatibility with JITs that dual-
> map their
> + * code to get around W^X restrictions, where one region is writable
> and the
> + * other is executable.
The patches seems to be line-wrap-damaged, and also base64-encoded.
Dunno if it's possible to un-damage it easily...
/mjt
next prev parent reply other threads:[~2023-06-11 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-11 11:44 [PATCH 0/2] target/arm: Improve user-mode compatibility with JITs John Högberg
2023-06-11 11:53 ` [PATCH 1/2] target/arm: Handle IC IVAU to improve " John Högberg
2023-06-11 16:47 ` Michael Tokarev
2023-06-11 17:31 ` John Högberg [this message]
2023-06-11 11:54 ` [PATCH 2/2] tests/tcg/aarch64: Add testcases for IC IVAU and dual-mapped code John Högberg
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=e9c30eedbc07c9a9e3e9e433435ee1dba0e9d47a.camel@ericsson.com \
--to=john.hogberg@ericsson.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--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).