From: Stefan Weil <sw@weilnetz.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Corey Bryant <coreyb@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH for-1.2] osdep: Fix compilation failure on BSD systems
Date: Thu, 16 Aug 2012 14:27:25 +0200 [thread overview]
Message-ID: <502CE72D.1090706@weilnetz.de> (raw)
In-Reply-To: <1345115718-4054-1-git-send-email-peter.maydell@linaro.org>
Am 16.08.2012 13:15, schrieb Peter Maydell:
> Fix compilation failure on BSD systems (which don't have
> O_DIRECT or O_NOATIME:
> osdep.c:116: error: ‘O_DIRECT’ undeclared (first use in this function)
> osdep.c:116: error: (Each undeclared identifier is reported only once
> osdep.c:116: error: for each function it appears in.)
> osdep.c:116: error: ‘O_NOATIME’ undeclared (first use in this function)
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> PS: Do we care about O_DSYNC, O_RSYNC, O_SYNC? POSIX says those can be
> used via fcntl() too...
>
> osdep.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/osdep.c b/osdep.c
> index 5b78cee..3b25297 100644
> --- a/osdep.c
> +++ b/osdep.c
> @@ -113,7 +113,13 @@ static int qemu_dup_flags(int fd, int flags)
> }
>
> /* Set/unset flags that we can with fcntl */
> - setfl_flags = O_APPEND | O_ASYNC | O_DIRECT | O_NOATIME | O_NONBLOCK;
> + setfl_flags = O_APPEND | O_ASYNC | O_NONBLOCK;
> +#ifdef O_NOATIME
> + setfl_flags |= O_NOATIME;
> +#endif
> +#ifdef O_DIRECT
> + setfl_flags |= O_DIRECT;
> +#endif
> dup_flags &= ~setfl_flags;
> dup_flags |= (flags & setfl_flags);
> if (fcntl(ret, F_SETFL, dup_flags) == -1) {
Would O_DSYNC be a good replacement here for an
undefined O_DIRECT? block/raw-posix.c does it like that.
What about defining O_NOATIME and O_DIRECT in qemu-common.h
when needed (like it is done for O_BINARY)?
But I don't want to delay 1.2, therefore
Reviewed-by: Stefan Weil <sw@weilnetz.de>
Regards,
Stefan W.
next prev parent reply other threads:[~2012-08-16 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 11:15 [Qemu-devel] [PATCH for-1.2] osdep: Fix compilation failure on BSD systems Peter Maydell
2012-08-16 12:27 ` Stefan Weil [this message]
2012-08-16 12:45 ` Peter Maydell
2012-08-16 13:11 ` Corey Bryant
2012-08-16 13:25 ` Peter Maydell
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=502CE72D.1090706@weilnetz.de \
--to=sw@weilnetz.de \
--cc=aliguori@us.ibm.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=patches@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.