qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: agraf@suse.de, gollub@b1-systems.de, qemu-devel@nongnu.org,
	lcapitulino@redhat.com
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_x86_64_rhel5
Date: Tue, 4 Oct 2011 08:18:07 +0100	[thread overview]
Message-ID: <20111004071807.GA8149@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <87ehyu2w99.fsf@skywalker.in.ibm.com>

On Mon, Oct 03, 2011 at 04:10:50PM +0530, Aneesh Kumar K.V wrote:
> On Mon, 3 Oct 2011 08:37:52 +0100, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> > On Sat, Oct 01, 2011 at 03:03:23PM +0530, Aneesh Kumar K.V wrote:
> > > +#ifndef CONFIG_UTIMENSAT
> > > +    /*
> > > +     * We support handle fs driver only if all related
> > > +     * syscalls are provided by host.
> > > +     */
> > 
> > Perhaps a ./configure check should be added to see whether the handle
> > syscalls are supported instead of using CONFIG_UTIMENSAT.
> > 
> 
> We already do check for handle syscall. Since glibc doesn't have the
> this syscall yet, I added the check in virtio-9p-handle.c as below

CONFIG_UTIMENSAT is defined when the host has glibc >= 2.6.

Handle syscalls are available on Linux 2.6.39 but not exposed by glibc.

Therefore CONFIG_UTIMENSAT has nothing to do with handle syscalls and
does not mean handle syscalls are supported.  I would drop that hunk of
the patch or test for the actual handle syscalls in ./configure.

Stefan

  reply	other threads:[~2011-10-04  7:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29 23:28 [Qemu-devel] buildbot failure in qemu on default_x86_64_rhel5 qemu
2011-09-30  8:26 ` Stefan Hajnoczi
2011-10-01  8:58   ` Aneesh Kumar K.V
2011-10-01  9:33     ` Aneesh Kumar K.V
2011-10-03  7:37       ` Stefan Hajnoczi
2011-10-03 10:40         ` Aneesh Kumar K.V
2011-10-04  7:18           ` Stefan Hajnoczi [this message]
2011-10-04  8:48             ` Aneesh Kumar K.V
2011-10-04 10:29               ` Stefan Hajnoczi
  -- strict thread matches above, loose matches on Subject: below --
2012-12-13 22:27 qemu
2012-05-14 23:58 qemu
2012-02-26  0:07 qemu
2011-12-13  0:06 qemu
2011-11-23  0:09 qemu
2011-11-22 23:53 ` Alexander Graf
2011-11-23  8:36   ` Stefan Hajnoczi
2011-09-05 23:24 qemu

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=20111004071807.GA8149@stefanha-thinkpad.localdomain \
    --to=stefanha@gmail.com \
    --cc=agraf@suse.de \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=gollub@b1-systems.de \
    --cc=lcapitulino@redhat.com \
    --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).