From: Stefan Hajnoczi <stefanha@redhat.com>
To: Sam Li <faithilikerun@gmail.com>
Cc: qemu-devel@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
dlemoal@kernel.org, dmitry.fomichev@wdc.com
Subject: Re: [PULL 00/17] Block patches
Date: Mon, 1 May 2023 07:56:30 -0400 [thread overview]
Message-ID: <20230501115630.GA1594843@fedora> (raw)
In-Reply-To: <607d67c6-4df6-f573-f7d4-a489e27496b1@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 3514 bytes --]
On Sat, Apr 29, 2023 at 11:05:06PM +0100, Richard Henderson wrote:
> On 4/28/23 13:39, Stefan Hajnoczi wrote:
> > The following changes since commit 05d50ba2d4668d43a835c5a502efdec9b92646e6:
> >
> > Merge tag 'migration-20230427-pull-request' of https://gitlab.com/juan.quintela/qemu into staging (2023-04-28 08:35:06 +0100)
> >
> > are available in the Git repository at:
> >
> > https://gitlab.com/stefanha/qemu.git tags/block-pull-request
> >
> > for you to fetch changes up to d3c760be786571d83d5cea01953e543df4d76f51:
> >
> > docs/zoned-storage:add zoned emulation use case (2023-04-28 08:34:07 -0400)
> >
> > ----------------------------------------------------------------
> > Pull request
> >
> > This pull request contains Sam Li's virtio-blk zoned storage work. These
> > patches were dropped from my previous block pull request due to CI failures.
>
>
> More CI build failures, e.g.
Hi Sam,
There are some more CI failures.
>
> https://gitlab.com/qemu-project/qemu/-/jobs/4202086013#L1720
This Ubuntu 20.04 on s390x CI job failed because <linux/blkzoned.h> is
missing Linux commit e876df1fe0ad ("block: add zone open, close and
finish ioctl support"):
../block/file-posix.c: In function ‘raw_co_zone_mgmt’:
../block/file-posix.c:3472:14: error: ‘BLKOPENZONE’ undeclared (first use in this function)
3472 | zo = BLKOPENZONE;
| ^~~~~~~~~~~
../block/file-posix.c:3472:14: note: each undeclared identifier is reported only once for each function it appears in
../block/file-posix.c:3476:14: error: ‘BLKCLOSEZONE’ undeclared (first use in this function); did you mean ‘BLKRESETZONE’?
3476 | zo = BLKCLOSEZONE;
| ^~~~~~~~~~~~
| BLKRESETZONE
../block/file-posix.c:3480:14: error: ‘BLKFINISHZONE’ undeclared (first use in this function)
3480 | zo = BLKFINISHZONE;
| ^~~~~~~~~~~~~
Older kernels didn't have these ioctls. I don't think it makes sense to
enable file-posix zoned functionality without these ioctls.
I suggest changing the CONFIG_BLKZONED check in meson.build from:
config_host_data.set('CONFIG_BLKZONED', cc.has_header('linux/blkzoned.h'))
to:
config_host_data.set('CONFIG_BLKZONED', cc.has_header_symbol('linux/blkzoned.h', 'BLKOPENZONE'))
> https://gitlab.com/qemu-project/qemu/-/jobs/4202085995#L4088
The <linux/asm/kvm.h> header file started using __DECLARE_FLEX_ARRAY()
and QEMU doesn't have that macro:
linux-headers/asm/kvm.h:509:3: error: expected specifier-qualifier-list before '__DECLARE_FLEX_ARRAY'
509 | __DECLARE_FLEX_ARRAY(struct kvm_vmx_nested_state_data, vmx);
| ^~~~~~~~~~~~~~~~~~~~
You could update the sed command in scripts/update-linux-headers.sh to
convert __DECLARE_FLEX_ARRAY(type, field) into type field[] or import
the Linux macro definition of __DECLARE_FLEX_ARRAY().
Another failure is
https://gitlab.com/qemu-project/qemu/-/jobs/4202085991 where
qemu-iotests is failing because the output has changed due to the
addition of zoned fields to block stats.
Another failure is
https://gitlab.com/qemu-project/qemu/-/jobs/4202086041 where
qemu-system-ppc seems to segfault.
You can find the CI results here: https://gitlab.com/qemu-project/qemu/-/pipelines/852908752
You can run the GitLab CI yourself like this:
$ git push -o ci.variable=QEMU_CI=2 your_gitlab_repo HEAD
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-05-01 11:57 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 12:39 [PULL 00/17] Block patches Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 01/17] block/block-common: add zoned device structs Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 02/17] block/file-posix: introduce helper functions for sysfs attributes Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 03/17] block/block-backend: add block layer APIs resembling Linux ZonedBlockDevice ioctls Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 04/17] block/raw-format: add zone operations to pass through requests Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 05/17] block: add zoned BlockDriver check to block layer Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 06/17] iotests: test new zone operations Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 07/17] block: add some trace events for new block layer APIs Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 08/17] docs/zoned-storage: add zoned device documentation Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 09/17] file-posix: add tracking of the zone write pointers Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 10/17] block: introduce zone append write for zoned devices Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 11/17] qemu-iotests: test zone append operation Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 12/17] block: add some trace events for zone append Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 13/17] include: update virtio_blk headers to v6.3-rc1 Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 14/17] virtio-blk: add zoned storage emulation for zoned devices Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 15/17] block: add accounting for zone append operation Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 16/17] virtio-blk: add some trace events for zoned emulation Stefan Hajnoczi
2023-04-28 12:39 ` [PULL 17/17] docs/zoned-storage:add zoned emulation use case Stefan Hajnoczi
2023-04-29 22:05 ` [PULL 00/17] Block patches Richard Henderson
2023-05-01 11:56 ` Stefan Hajnoczi [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-05 15:45 Hanna Czenczek
2023-06-05 19:03 ` Richard Henderson
2020-09-30 10:12 Stefan Hajnoczi
2020-10-01 11:23 ` Peter Maydell
2020-10-01 13:56 ` Vladimir Sementsov-Ogievskiy
2020-10-01 15:02 ` Stefan Hajnoczi
2020-10-01 15:12 ` Peter Maydell
2020-10-05 13:26 ` Stefan Hajnoczi
2020-10-01 15:29 ` Vladimir Sementsov-Ogievskiy
2020-10-02 10:36 ` Peter Maydell
2020-02-06 12:51 Max Reitz
2020-02-06 18:58 ` 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=20230501115630.GA1594843@fedora \
--to=stefanha@redhat.com \
--cc=dlemoal@kernel.org \
--cc=dmitry.fomichev@wdc.com \
--cc=faithilikerun@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).