From: Laurent Vivier <laurent@vivier.eu>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH] linux-user: Set CF_PARALLEL when mapping shared memory
Date: Sat, 12 Jun 2021 12:29:38 +0200 [thread overview]
Message-ID: <c2016ff3-8ed8-5e9c-eaa5-6c467d9ebf03@vivier.eu> (raw)
In-Reply-To: <20210612060828.695332-1-richard.henderson@linaro.org>
Le 12/06/2021 à 08:08, Richard Henderson a écrit :
> Signal the translator to use host atomic instructions for
> guest operations, insofar as it is possible. This is the
> best we can do to allow the guest to interact atomically
> with other processes.
>
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/121
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> linux-user/mmap.c | 14 ++++++++++++++
> linux-user/syscall.c | 12 ++++++++++++
> 2 files changed, 26 insertions(+)
>
> diff --git a/linux-user/mmap.c b/linux-user/mmap.c
> index 7e3b245036..0e103859fe 100644
> --- a/linux-user/mmap.c
> +++ b/linux-user/mmap.c
> @@ -451,6 +451,20 @@ abi_long target_mmap(abi_ulong start, abi_ulong len, int target_prot,
> goto fail;
> }
>
> + /*
> + * If we're mapping shared memory, ensure we generate code for parallel
> + * execution and flush old translations. This will work up to the level
> + * supported by the host -- anything that requires EXCP_ATOMIC will not
> + * be atomic with respect to an external process.
> + */
> + if (flags & MAP_SHARED) {
> + CPUState *cpu = thread_cpu;
> + if (!(cpu->tcg_cflags & CF_PARALLEL)) {
> + cpu->tcg_cflags |= CF_PARALLEL;
> + tb_flush(cpu);
> + }
> + }
> +
> real_start = start & qemu_host_page_mask;
> host_offset = offset & qemu_host_page_mask;
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 974dd46c9a..54037db8d6 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -4603,6 +4603,7 @@ static inline abi_ulong target_shmlba(CPUArchState *cpu_env)
> static inline abi_ulong do_shmat(CPUArchState *cpu_env,
> int shmid, abi_ulong shmaddr, int shmflg)
> {
> + CPUState *cpu = env_cpu(cpu_env);
> abi_long raddr;
> void *host_raddr;
> struct shmid_ds shm_info;
> @@ -4633,6 +4634,17 @@ static inline abi_ulong do_shmat(CPUArchState *cpu_env,
>
> mmap_lock();
>
> + /*
> + * We're mapping shared memory, so ensure we generate code for parallel
> + * execution and flush old translations. This will work up to the level
> + * supported by the host -- anything that requires EXCP_ATOMIC will not
> + * be atomic with respect to an external process.
> + */
> + if (!(cpu->tcg_cflags & CF_PARALLEL)) {
> + cpu->tcg_cflags |= CF_PARALLEL;
> + tb_flush(cpu);
> + }
> +
> if (shmaddr)
> host_raddr = shmat(shmid, (void *)g2h_untagged(shmaddr), shmflg);
> else {
>
Applied to my linux-user-for-6.1 branch.
Thanks,
Laurent
next prev parent reply other threads:[~2021-06-12 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 6:08 [PATCH] linux-user: Set CF_PARALLEL when mapping shared memory Richard Henderson
2021-06-12 10:29 ` Laurent Vivier [this message]
2021-06-14 12:06 ` Alex Bennée
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=c2016ff3-8ed8-5e9c-eaa5-6c467d9ebf03@vivier.eu \
--to=laurent@vivier.eu \
--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).