From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jing Liu <liujbjl@linux.vnet.ibm.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
Cleber Rosa <crosa@redhat.com>,
qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 3/3] qemu-iotests: require CONFIG_LINUX_AIO for test 087
Date: Wed, 26 Jul 2017 10:49:51 +0100 [thread overview]
Message-ID: <20170726094951.GC28914@redhat.com> (raw)
In-Reply-To: <7343a904-6f31-b8b1-c721-267c66e4cb75@linux.vnet.ibm.com>
On Wed, Jul 26, 2017 at 04:55:39PM +0800, Jing Liu wrote:
>
>
> On 2017/7/25 下午11:48, Daniel P. Berrange wrote:
> > On Tue, Jul 25, 2017 at 04:45:46PM +0100, Stefan Hajnoczi wrote:
> > > On Mon, Jul 24, 2017 at 02:44:13PM +0800, Jing Liu wrote:
> > > > On 2017/7/21 上午11:47, Cleber Rosa wrote:
> > > > > One of the "sub-"tests of test 087 requires CONFIG_LINUX_AIO.
> > > > >
> > > > > As a PoC/RFC, this goes the easy route and skips the test as a whole
> > > > > when that feature is missing. Other approaches include splitting
> > > > > the test and adding extra filtering.
> > > > >
> > > > > Signed-off-by: Cleber Rosa <crosa@redhat.com>
> > > > > ---
> > > > > tests/qemu-iotests/087 | 1 +
> > > > > 1 file changed, 1 insertion(+)
> > > > >
> > > > > diff --git a/tests/qemu-iotests/087 b/tests/qemu-iotests/087
> > > > > index f8e4903..a2fb7de 100755
> > > > > --- a/tests/qemu-iotests/087
> > > > > +++ b/tests/qemu-iotests/087
> > > > > @@ -34,6 +34,7 @@ status=1 # failure is the default!
> > > > > _supported_fmt qcow2
> > > > > _supported_proto file
> > > > > _supported_os Linux
> > > > > +_require_feature CONFIG_LINUX_AIO
> > > > I tested that CONFIG_NETTLE_KDF is also a necessary for 087.
> > > >
> > > > +_require_feature CONFIG_NETTLE_KDF
> > > Are you sure? Looks like either nettle or gcrypt is needed:
> > Correct, it works with either.
> Ah, because I just found out nettle which related to KDF.
> why can not find out gcrypt.h in qemu?
> How to compile config_gcrypt_kdf into qemu?
QEMU picks either nettle or libgcrypt automatically, dependant on which
of these gnutls is linked to.
You can force override this via --disable-nettle --enable-gcrypt
(or vica-verca), for sake of testing, but you shouldn't do that
for production builds.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-07-26 9:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 3:47 [Qemu-devel] [PATCH 0/3] build configuration query tool and conditional (qemu-io)test skip Cleber Rosa
2017-07-21 3:47 ` [Qemu-devel] [PATCH 1/3] scripts: introduce buildconf.py Cleber Rosa
2017-07-21 14:00 ` Eric Blake
2017-07-21 14:07 ` Cleber Rosa
2017-07-21 3:47 ` [Qemu-devel] [PATCH 2/3] qemu-iotests: add _require_feature() function Cleber Rosa
2017-07-21 3:47 ` [Qemu-devel] [PATCH 3/3] qemu-iotests: require CONFIG_LINUX_AIO for test 087 Cleber Rosa
2017-07-24 6:44 ` Jing Liu
2017-07-25 15:45 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-07-25 15:48 ` Daniel P. Berrange
2017-07-26 8:55 ` Jing Liu
2017-07-26 9:49 ` Daniel P. Berrange [this message]
2017-07-21 4:39 ` [Qemu-devel] [PATCH 0/3] build configuration query tool and conditional (qemu-io)test skip no-reply
2017-07-21 12:33 ` Stefan Hajnoczi
2017-07-21 13:49 ` Cleber Rosa
2017-08-08 8:01 ` Markus Armbruster
2017-07-21 14:01 ` Daniel P. Berrange
2017-07-21 14:21 ` Cleber Rosa
2017-07-25 15:49 ` Stefan Hajnoczi
2017-07-25 16:16 ` Cleber Rosa
2017-07-25 16:24 ` Daniel P. Berrange
2017-07-25 16:47 ` Cleber Rosa
2017-07-26 17:58 ` Stefan Hajnoczi
2017-07-26 18:24 ` Cleber Rosa
2017-07-27 13:41 ` Stefan Hajnoczi
2017-08-08 8:06 ` Markus Armbruster
2017-08-08 12:44 ` Stefan Hajnoczi
2017-08-08 14:52 ` Markus Armbruster
2017-08-09 10:30 ` Stefan Hajnoczi
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=20170726094951.GC28914@redhat.com \
--to=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=kwolf@redhat.com \
--cc=liujbjl@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).