qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Evgeny Iakovlev <eiakovlev@linux.microsoft.com>,
	qemu-devel@nongnu.org,  alex.bennee@linaro.org
Subject: Re: [PATCH] semihosting: add O_BINARY flag in host_open for NT compatibility
Date: Fri, 6 Jan 2023 17:48:38 +0800	[thread overview]
Message-ID: <CAEUhbmVkDVz_DLrzAFzGT75aBf6_t3LSAfTfogkLpLQLQ-+ZHg@mail.gmail.com> (raw)
In-Reply-To: <408a6546-025b-1a94-ee98-a577b8460e13@linaro.org>

On Fri, Jan 6, 2023 at 3:39 PM Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
>
> On 5/1/23 22:19, Evgeny Iakovlev wrote:
> > Windows open(2) implementations opens files in text mode by default and
> > needs a Windows-only O_BINARY flag to open files as binary. Qemu already
>
> s/Qemu/QEMU/
>
> > knows about that flag in osdep.h, so we can just add it to the
> > host_flags for better compatibility when running qemu on Windows.
>
> s/qemu/QEMU/
>
> > Signed-off-by: Evgeny Iakovlev <eiakovlev@linux.microsoft.com>
> > ---
> >   semihosting/syscalls.c | 2 ++
> >   1 file changed, 2 insertions(+)
> >
> > diff --git a/semihosting/syscalls.c b/semihosting/syscalls.c
> > index 508a0ad88c..00f77507e5 100644
> > --- a/semihosting/syscalls.c
> > +++ b/semihosting/syscalls.c
> > @@ -278,6 +278,8 @@ static void host_open(CPUState *cs, gdb_syscall_complete_cb complete,
> >           host_flags |= O_EXCL;
> >       }
> >
> > +    host_flags |= O_BINARY;
> > +
> >       ret = open(p, host_flags, mode);
> >       if (ret < 0) {
> >           complete(cs, -1, errno);
>
> Alternatively with more churn:
>
> -- >8 --
> diff --git a/semihosting/syscalls.c b/semihosting/syscalls.c
> index 508a0ad88c..b621d78c2d 100644
> --- a/semihosting/syscalls.c
> +++ b/semihosting/syscalls.c
> @@ -253,7 +253,7 @@ static void host_open(CPUState *cs,
> gdb_syscall_complete_cb complete,
>   {
>       CPUArchState *env G_GNUC_UNUSED = cs->env_ptr;
>       char *p;
> -    int ret, host_flags;
> +    int ret, host_flags = O_BINARY;
>
>       ret = validate_lock_user_string(&p, cs, fname, fname_len);
>       if (ret < 0) {
> @@ -262,11 +262,11 @@ static void host_open(CPUState *cs,
> gdb_syscall_complete_cb complete,
>       }
>
>       if (gdb_flags & GDB_O_WRONLY) {
> -        host_flags = O_WRONLY;
> +        host_flags |= O_WRONLY;
>       } else if (gdb_flags & GDB_O_RDWR) {
> -        host_flags = O_RDWR;
> +        host_flags |= O_RDWR;
>       } else {
> -        host_flags = O_RDONLY;
> +        host_flags |= O_RDONLY;
>       }
>       if (gdb_flags & GDB_O_CREAT) {
>           host_flags |= O_CREAT;
> ---
>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>

With Philippe's comments addressed,
Reviewed-by: Bin Meng <bmeng.cn@gmail.com>


  reply	other threads:[~2023-01-06  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 21:19 [PATCH] semihosting: add O_BINARY flag in host_open for NT compatibility Evgeny Iakovlev
2023-01-06  7:29 ` Philippe Mathieu-Daudé
2023-01-06  9:48   ` Bin Meng [this message]
2023-01-06 10:21     ` Evgeny Iakovlev
2023-01-06 10:27     ` Evgeny Iakovlev

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=CAEUhbmVkDVz_DLrzAFzGT75aBf6_t3LSAfTfogkLpLQLQ-+ZHg@mail.gmail.com \
    --to=bmeng.cn@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=eiakovlev@linux.microsoft.com \
    --cc=philmd@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).