From: Kevin Wolf <kwolf@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "Hervé Poussineau" <hpoussin@reactos.org>,
qemu-devel@nongnu.org,
"Stefan Hajnoczi" <stefanha@linux.vnet.ibm.com>,
"Markus Armbruster" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 07/10] block: add a transfer rate for floppy types
Date: Mon, 23 Jan 2012 09:51:30 +0100 [thread overview]
Message-ID: <4F1D1F92.1030506@redhat.com> (raw)
In-Reply-To: <CAAu8pHtweT5=dtQ1BasN+rB_5XaUzbF_w-hz28iuz2D6rVXuhg@mail.gmail.com>
Am 21.01.2012 20:02, schrieb Blue Swirl:
> On Mon, Jan 16, 2012 at 10:18, Kevin Wolf <kwolf@redhat.com> wrote:
>> Am 15.01.2012 08:51, schrieb Hervé Poussineau:
>>> Floppies must be read at a specific transfer rate, depending of its own format.
>>> Update floppy description table to include required transfer rate.
>>>
>>> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
>>> ---
>>> block.c | 74 ++++++++++++++++++++++++++++++++-----------------------------
>>> block.h | 10 +++++++-
>>> hw/fdc.c | 3 +-
>>> hw/pc.c | 3 +-
>>
>> Meh. Having any floppy-specific logic in the block layer is wrong. We
>> need to finally get this moved into fdc.c.
>
> Well, actually this code was moved recently from fdc.c to block.c
> (5bbdbb4676d17e782ae83055bac58e0751b25e4b). The other geometry
> guessing functions (ATA CHS) are also there. If we supported native
> floppy (or ATA) pass trough, the geometry would have to be read from
> the host device, so I think it's logical to keep that in block level
> instead of all devices. Maybe we could also split block.c into
> block-fdc.c, block-ata.c etc.
The geometry is guest state, so it shouldn't be in the block layer,
which deals with host state. Maybe we could need some hw/block.c that
deals with guest state concepts that are shared between multiple device.
Images or passthrough backends could provide defaults.
I'll admit that not having an obvious place for media (we only have it
for images and guest devices) doesn't make the design decisions easier.
Kevin
next prev parent reply other threads:[~2012-01-23 8:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 7:51 [Qemu-devel] [PATCH v2 00/10] Misc fixes for floppy emulation Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 01/10] fdc: take side count into account Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 02/10] fdc: set busy bit when starting a command Hervé Poussineau
2012-01-16 9:33 ` Kevin Wolf
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 03/10] fdc: most control commands do not generate interrupts Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 04/10] fdc: emulate stepping 0 Hervé Poussineau
2012-01-16 9:54 ` Kevin Wolf
2012-01-23 7:58 ` Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 05/10] fdc: handle read-only floppies (abort early on write commands) Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 06/10] fdc: add CCR (Configuration Control Register) write register Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 07/10] block: add a transfer rate for floppy types Hervé Poussineau
2012-01-16 10:18 ` Kevin Wolf
2012-01-21 19:02 ` Blue Swirl
2012-01-23 8:51 ` Kevin Wolf [this message]
2012-01-23 16:56 ` Blue Swirl
2012-01-27 8:33 ` Markus Armbruster
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 08/10] fdc: check if media rate is correct before doing any transfer Hervé Poussineau
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 09/10] fdc: fix seek command, which shouldn't check tracks Hervé Poussineau
2012-01-16 10:32 ` Kevin Wolf
2012-01-15 7:51 ` [Qemu-devel] [PATCH v2 10/10] fdc: DIR (Digital Input Register) should return status of current drive Hervé Poussineau
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=4F1D1F92.1030506@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=hpoussin@reactos.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).