qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Gleb Popov <arrowd@freebsd.org>,
	 Konrad Witaszczyk <def@freebsd.org>,
	Jessica Clarke <jrtc27@freebsd.org>,
	Kyle Evans <kevans@freebsd.org>, Stacey Son <sson@freebsd.org>
Subject: Re: [PATCH 4/6] bsd-user/bsd-file.h: Add implementations for read, pread, readv and preadv
Date: Tue, 7 Jun 2022 19:02:26 -0700	[thread overview]
Message-ID: <CANCZdfrca-pwZDLsr77YkkOPH6aTOEjEXR9iSCF+GPeASc0LzQ@mail.gmail.com> (raw)
In-Reply-To: <575c6936-c0e0-2c9f-8c5d-e9184001804b@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]

On Tue, Jun 7, 2022 at 2:45 PM Richard Henderson <
richard.henderson@linaro.org> wrote:

> On 6/7/22 13:14, Warner Losh wrote:
> > +/* read(2) */
> > +static inline abi_long do_bsd_read(abi_long arg1, abi_long arg2,
> abi_long arg3)
>
> Why the inline markers?  Best to drop them.
>

static inline ensures that we don't get a warning if bsd-file.h is included
in multiple places and these routines aren't used.

Though it turns out....


> > +        /*
> > +         * File system calls.
> > +         */
> > +    case TARGET_FREEBSD_NR_read: /* read(2) */
> > +        ret = do_bsd_read(arg1, arg2, arg3);
> > +        break;
> > +
> > +    case TARGET_FREEBSD_NR_pread: /* pread(2) */
> > +        ret = do_bsd_pread(cpu_env, arg1, arg2, arg3, arg4, arg5, arg6);
> > +        break;
> > +
> > +    case TARGET_FREEBSD_NR_readv: /* readv(2) */
> > +        ret = do_bsd_readv(arg1, arg2, arg3);
> > +        break;
>
> Missing preadv, which you added above.


It would have caught this :)  I'll update this and the write changes...

Warner

[-- Attachment #2: Type: text/html, Size: 1759 bytes --]

  reply	other threads:[~2022-06-08  2:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 20:14 [PATCH 0/6] bsd-user upstreaming: read, write and exit Warner Losh
2022-06-07 20:14 ` [PATCH 1/6] bsd-user/freebsd/os-syscall.c: lock_iovec Warner Losh
2022-06-07 21:01   ` Richard Henderson
2022-06-07 21:31     ` Warner Losh
2022-06-07 20:14 ` [PATCH 2/6] bsd-user/freebsd/os-syscall.c: unlock_iovec Warner Losh
2022-06-07 21:28   ` Richard Henderson
2022-06-07 21:51     ` Warner Losh
2022-06-07 22:23       ` Richard Henderson
2022-06-07 23:35         ` Warner Losh
2022-06-08  2:02           ` Richard Henderson
2022-06-08 16:32             ` Warner Losh
2022-06-07 20:14 ` [PATCH 3/6] bsd-user/freebsd/os-syscall.c: Tracing and error boilerplate Warner Losh
2022-06-07 21:34   ` Richard Henderson
2022-06-07 21:56     ` Warner Losh
2022-06-07 20:14 ` [PATCH 4/6] bsd-user/bsd-file.h: Add implementations for read, pread, readv and preadv Warner Losh
2022-06-07 21:45   ` Richard Henderson
2022-06-08  2:02     ` Warner Losh [this message]
2022-06-07 20:14 ` [PATCH 5/6] bsd-user/bsd-file.h: Meat of the write system calls Warner Losh
2022-06-07 21:46   ` Richard Henderson
2022-06-07 20:14 ` [PATCH 6/6] bsd-user/freebsd/os-syscall.c: Implement exit Warner Losh

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=CANCZdfrca-pwZDLsr77YkkOPH6aTOEjEXR9iSCF+GPeASc0LzQ@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=arrowd@freebsd.org \
    --cc=def@freebsd.org \
    --cc=jrtc27@freebsd.org \
    --cc=kevans@freebsd.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sson@freebsd.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).