From: Jonathan Phenix <jonathan.phenix@videotron.ca>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Block driver and constant sector size
Date: Sat, 12 May 2007 12:35:46 -0400 [thread overview]
Message-ID: <4645ECE2.4050408@videotron.ca> (raw)
Hi,
currently the block driver in qemu only handles blocks (or sectors)
which are 512 bytes long, this is ideal if the device you are emulating
have a block size which is a multiple of 512. Unfortunately, this is not
always the case, for example an audio CD (CD-DA) or a CD in mode 2 have
a sector size of 2352, which is not a multiple of 512. Typical data CD
are encoded in mode 1 with an ISO9660 file system, and this mode uses a
sector size of 2048, which is a multiple of 512, this is the reason why
the problem probably didn't come up yet. You can dump about any CDs in
mode 2 under Linux with the "cdrdao read-cd --read-raw [...]" command
for example.
In order to let the block driver read these raw images, I would like to
change:
BlockDriverState *bdrv_new(const char *device_name);
to:
BlockDriverState *bdrv_new(const char *device_name, int sector_size);
and change:
int (*bdrv_probe)(const uint8_t *buf, int buf_size, const char *filename);
of the BlockDriver structure to:
int (*bdrv_probe)(const uint8_t *buf, int buf_size, const char
*filename, int sector_size);
Then, each probe functions should be modified to reject sector size
which is not 512 bytes, except for the raw block driver, which will be
modified to accept any block sizes. This change would probably solve the
whole problem without having a negative impact on the rest of the code.
Is it the right way to solve the problem? If this solution is accepted,
I will code it and submit a patch.
Regards,
Jonathan Phénix
next reply other threads:[~2007-05-12 16:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 16:35 Jonathan Phenix [this message]
2007-05-18 20:41 ` [Qemu-devel] Block driver and constant sector size Paul Brook
2007-05-20 20:27 ` Jonathan Phenix
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=4645ECE2.4050408@videotron.ca \
--to=jonathan.phenix@videotron.ca \
--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).