From: Kevin Wolf <kwolf@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Clément Chigot" <chigot@adacore.com>,
qemu-devel@nongnu.org, hreitz@redhat.com, qemu-block@nongnu.org
Subject: Re: [PATCH 5/5] vvfat: add support for "size" options
Date: Wed, 5 Nov 2025 10:35:58 +0100 [thread overview]
Message-ID: <aQsafmFOrfEmOc0M@redhat.com> (raw)
In-Reply-To: <874ir9ot1a.fsf@pond.sub.org>
Am 05.11.2025 um 08:08 hat Markus Armbruster geschrieben:
> Kevin Wolf <kwolf@redhat.com> writes:
>
> [...]
>
> > To me it looks a bit like what we really want is an enum for floppy
> > sizes (though is there any real reason why we have only those two?), but
> > an arbitrary size for hard disks.
> >
> > Without the enum, obviously, users could specify 1440k and that would do
> > the right thing. Maybe special casing whatever 1.44M and 2.88M result
> > in and translating them into 1440k and 2880k could be more justifiable
> > than special casing 1M and 2M, but it would still be ugly.
> >
> > Markus, do you have any advice how this should be represented in QAPI?
>
> Still want answers here?
Yes, I'm still not sure how we could best represent both hard disk and
floppy sizes in vvfat in a way that isn't completely counterintuitive
for users, that also isn't just arbitrary magic and that works on the
command line.
Unless the need for different sizes has gone away, but I don't think we
found any other solution for the problem that would not require a
configurable disk/file system size?
Kevin
next prev parent reply other threads:[~2025-11-05 9:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 7:57 [PATCH 0/5] block/vvfat: introduce "size" option Clément Chigot
2025-09-03 7:57 ` [PATCH 1/5] vvfat: introduce no-mbr option Clément Chigot
2025-10-23 18:20 ` Kevin Wolf
2025-10-29 8:37 ` Clément Chigot
2025-10-29 10:56 ` Kevin Wolf
2025-10-29 13:44 ` Clément Chigot
2025-09-03 7:57 ` [PATCH 2/5] vvfat: move fat_type check prior to size setup Clément Chigot
2025-10-23 18:39 ` Kevin Wolf
2025-10-29 13:48 ` Clément Chigot
2025-10-29 13:58 ` BALATON Zoltan
2025-10-29 16:05 ` Kevin Wolf
2025-09-03 7:57 ` [PATCH 3/5] vvfat: add a define for SECTOR_SIZE Clément Chigot
2025-10-23 18:47 ` Kevin Wolf
2025-09-03 7:57 ` [PATCH 4/5] vvfat: move size parameters within driver structure Clément Chigot
2025-09-03 7:57 ` [PATCH 5/5] vvfat: add support for "size" options Clément Chigot
2025-10-23 19:29 ` Kevin Wolf
2025-10-24 8:30 ` Markus Armbruster
2025-10-24 9:23 ` Clément Chigot
2025-10-27 12:09 ` Markus Armbruster
2025-10-28 14:54 ` Clément Chigot
2025-10-31 7:46 ` Markus Armbruster
2025-10-31 9:47 ` Clément Chigot
2025-10-31 11:56 ` Kevin Wolf
2025-10-31 13:07 ` Clément Chigot
2025-11-05 7:06 ` Markus Armbruster
2025-11-05 7:08 ` Markus Armbruster
2025-11-05 9:35 ` Kevin Wolf [this message]
2025-11-05 10:15 ` Clément Chigot
2025-11-07 8:06 ` Markus Armbruster
2025-09-15 8:47 ` [PATCH 0/5] block/vvfat: introduce "size" option Clément Chigot
2025-10-07 7:43 ` Clément Chigot
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=aQsafmFOrfEmOc0M@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=chigot@adacore.com \
--cc=hreitz@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).