qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "J. Neuschäfer" <j.neuschaefer@gmx.net>
Cc: qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH] linux-user/arm: Fix return value of SYS_cacheflush
Date: Mon, 16 Jun 2025 11:13:24 +0100	[thread overview]
Message-ID: <CAFEAcA9ZS-8YKwboEYz_rWCFr5ezu3UOdhRaww3eJ2=cUKVeyA@mail.gmail.com> (raw)
In-Reply-To: <20250613-cache-v1-1-ee9f4a9ba81b@gmx.net>

On Fri, 13 Jun 2025 at 17:02, J. Neuschäfer <j.neuschaefer@gmx.net> wrote:
>
> Although the emulated cacheflush syscall does nothing, it still needs to
> return zero to indicate success.
>
> Signed-off-by: J. Neuschäfer <j.neuschaefer@gmx.net>
> ---
>  linux-user/arm/cpu_loop.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/linux-user/arm/cpu_loop.c b/linux-user/arm/cpu_loop.c
> index e8417d040691a04a3edc0f5508f047571beac8fa..33f63951a958a5a48ced2d1e187264d691e5c940 100644
> --- a/linux-user/arm/cpu_loop.c
> +++ b/linux-user/arm/cpu_loop.c
> @@ -363,6 +363,7 @@ void cpu_loop(CPUARMState *env)
>                      switch (n) {
>                      case ARM_NR_cacheflush:
>                          /* nop */
> +                        env->regs[0] = 0;
>                          break;
>                      case ARM_NR_set_tls:
>                          cpu_set_tls(env, env->regs[0]);

Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
and queued to target-arm.next. Interesting that nobody's
noticed this in all these years...

(If we were really enthusiastic we could make it fail for
the "end < start || flags" condition the kernel tests, but
that seems unnecessary. The kernel also checks for access
permissions, which would be harder.)

thanks
-- PMM


      reply	other threads:[~2025-06-16 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 15:59 [PATCH] linux-user/arm: Fix return value of SYS_cacheflush J. Neuschäfer
2025-06-16 10:13 ` Peter Maydell [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='CAFEAcA9ZS-8YKwboEYz_rWCFr5ezu3UOdhRaww3eJ2=cUKVeyA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=j.neuschaefer@gmx.net \
    --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).