From: Thomas Huth <thuth@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: Qemu-block <qemu-block@nongnu.org>
Subject: Re: [PATCH 3/4] Move CONFIG_XFS handling to meson.build
Date: Fri, 10 Dec 2021 08:53:37 +0100 [thread overview]
Message-ID: <7da70e19-537b-9ca5-125d-f9bcf2d3f6df@redhat.com> (raw)
In-Reply-To: <e02332c0-7c4e-18a2-5c33-b00e8045f6da@redhat.com>
On 02/11/2021 12.34, Paolo Bonzini wrote:
> On 28/10/21 20:59, Thomas Huth wrote:
>> Checking for xfsctl() can be done more easily in meson.build. Also,
>> this is not a "real" feature like the other features that we provide
>> with the "--enable-xxx" and "--disable-xxx" switches for the
>> configure script, since this does not influence lots of code (it's
>> only about one call to xfsctl() in file-posix.c), so people don't
>> gain much with the ability to disable this with "--disable-xfsctl".
>> Let's rather treat this like the other cc.has_function() checks in
>> meson.build, i.e. don't add a new option for this in meson_options.txt.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>
> I think we should just use ioctl and copy the relevant definitions from Linux:
>
> struct dioattr {
> u32 d_mem; /* data buffer memory alignment */
> u32 d_miniosz; /* min xfer size */
> u32 d_maxiosz; /* max xfer size */
> };
>
> #define XFS_IOC_DIOINFO _IOR ('X', 30, struct dioattr)
I've now had a closer look at this idea, but it's getting messy: We'd
additionally also need the platform_test_xfs_fd() function that is called
from file-posix.c ... sure it's not big, but the XFS header stuff is
licensed as LGPL, so it feels wrong to copy this over into file-posix.c that
has a MIT license. Of course, it could be rewritten, or put into a separate
file ... but that is already way more cumbersome for such a small benefit.
So I think I prefer to rather keep my patch in the current shape that has a
way nicer diffstat with way less risk of messing things up here.
Thomas
next prev parent reply other threads:[~2021-12-10 7:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 18:59 [PATCH 0/4] configure and meson.build improvements Thomas Huth
2021-10-28 18:59 ` [PATCH 1/4] configure: Remove the check for the __thread keyword Thomas Huth
2021-10-29 16:48 ` Richard Henderson
2021-11-02 11:37 ` Paolo Bonzini
2021-10-28 18:59 ` [PATCH 2/4] Move the l2tpv3 test from configure to meson.build Thomas Huth
2021-11-02 11:36 ` Paolo Bonzini
2021-10-28 18:59 ` [PATCH 3/4] Move CONFIG_XFS handling " Thomas Huth
2021-11-02 11:34 ` Paolo Bonzini
2021-11-02 11:38 ` Thomas Huth
2021-11-02 11:50 ` Paolo Bonzini
2021-12-10 7:53 ` Thomas Huth [this message]
2021-12-10 8:39 ` Paolo Bonzini
2021-12-10 8:46 ` Thomas Huth
2021-12-10 10:10 ` Paolo Bonzini
2021-12-14 9:15 ` Thomas Huth
2021-10-28 18:59 ` [PATCH 4/4] Move the libssh setup from configure " Thomas Huth
2021-10-29 6:09 ` Thomas Huth
2021-11-02 11:36 ` Paolo Bonzini
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=7da70e19-537b-9ca5-125d-f9bcf2d3f6df@redhat.com \
--to=thuth@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.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 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).