From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>, "John Snow" <jsnow@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-block@nongnu.org, "Max Reitz" <mreitz@redhat.com>
Subject: [PATCH-for-5.2 7/7] hw/block/fdc: Add ASCII art schema of QOM relations
Date: Thu, 6 Aug 2020 10:08:24 +0200 [thread overview]
Message-ID: <20200806080824.21567-8-f4bug@amsat.org> (raw)
In-Reply-To: <20200806080824.21567-1-f4bug@amsat.org>
Without knowing the QEMU history, it is hard to relate QEMU objects
with the hardware datasheet.
For example, one naively expects:
* a floppy disk is plugged / unplugged on the bus
Wrong! QEMU floppy disks always sit on the bus. The block drives
are plugged / unplugged on the disks, and the disks magically
re-adapt their proprieties to match the block drive.
* a floppy controller has a fixed number of disks pluggable on the bus
Wrong! QEMU floppy controllers have as much slots as the number of
floppy drive provided when a machine is created. Then the ACPI table
are generated and the number of slots can not be modified. So if you
expect a dual slot controller being created with slot A and B, if
the machine is created with a single drive attached, the controller
will only have slot A created, and you will never be able to plug
drive B without risking a mismatch in the ACPI tables.
* a floppy controller supporting 4 disks uses 2 buses
Wrong! QEMU uses a single bus to plug the 4 disks.
As all these false assumptions are not obvious (we don't plug a disk,
we plug a block drive into a disk, etc...), start documenting the QOM
relationships with a simple ASCII schema.
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
hw/block/fdc.c | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
diff --git a/hw/block/fdc.c b/hw/block/fdc.c
index 6944b06e4b..b109f37050 100644
--- a/hw/block/fdc.c
+++ b/hw/block/fdc.c
@@ -47,6 +47,28 @@
#include "qemu/module.h"
#include "trace.h"
+/*
+ * QOM relationship:
+ * =================
+ *
+ * +-------------------+
+ * | |
+ * isa/sysbus <--->| |
+ * | |
+ * irq/dma <----| fdc |
+ * |
+ * clk ---->| | +-+------+-+ +-+------+-+
+ * | | | | blk | | | | blk | |
+ * +--------+----------+ | | | | | | | |
+ * | | +------+ | | +------+ |
+ * | | | | |
+ * | | floppy | | floppy |
+ * | +----+-----+ +----+-----+
+ * | floppy-bus | |
+ * +------------------------v---------------v---
+ *
+ */
+
/********************************************************/
/* debug Floppy devices */
--
2.21.3
next prev parent reply other threads:[~2020-08-06 11:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 8:08 [PATCH-for-5.2 0/7] hw/block/fdc: Cleanups trying to make sense of the floppy controllers Philippe Mathieu-Daudé
2020-08-06 8:08 ` [PATCH-for-5.2 1/7] hw/block/fdc: Let sector count be unsigned Philippe Mathieu-Daudé
2020-08-06 8:08 ` [PATCH-for-5.2 2/7] hw/block/fdc: Let sector offset " Philippe Mathieu-Daudé
2020-08-06 8:08 ` [PATCH-for-5.2 3/7] hw/block/fdc: Use warn_report() instead of debug FLOPPY_DPRINTF() calls Philippe Mathieu-Daudé
2020-08-06 8:08 ` [PATCH-for-5.2 4/7] hw/block/fdc: Convert debug FLOPPY_DPRINTF() to trace events Philippe Mathieu-Daudé
2020-08-06 8:08 ` [PATCH-for-5.2 5/7] hw/block/fdc: Drop pointless FLOPPY_DPRINTF() call Philippe Mathieu-Daudé
2020-08-06 8:08 ` [PATCH-for-5.2 6/7] hw/block/fdc: Use more descriptive TypeInfo names Philippe Mathieu-Daudé
2020-08-06 8:08 ` Philippe Mathieu-Daudé [this message]
2020-08-06 8:57 ` [PATCH-for-5.2 7/7] hw/block/fdc: Add ASCII art schema of QOM relations Kevin Wolf
2020-08-06 10:33 ` Philippe Mathieu-Daudé
2020-08-06 12:04 ` Kevin Wolf
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=20200806080824.21567-8-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).