From: Alexander Graf <agraf@suse.de>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: 乔崇 <qiaochong@loongson.cn>,
teheo@suse.de, "Joerg Roedel" <joro@8bytes.org>,
qemu-devel@nongnu.org, "Elek Roland" <elek.roland@gmail.com>
Subject: [Qemu-devel] Re: AHCI support integration
Date: Sun, 09 May 2010 21:11:17 +0200 [thread overview]
Message-ID: <4BE708D5.5080405@suse.de> (raw)
In-Reply-To: <1945C1D2D39F43239CFD537CA66DA5F8@FSCPC>
Sebastian Herbszt wrote:
> The ICH6 AHCI implementation submitted by Chong is an all-in-one
> attempt (ahci.c).
> It includes all needed parts of the ICH6, AHCI, SATA and ATA
> specification.
> The code in hw/ide/* on the other hand is split (or could be split)
> into smaller parts like
> port based and bus master access, IDE and ATA core.
> I think it might be reasonable to split ahci.c into ICH6, AHCI and
> SATA parts and strip the
> limited ATA support and reuse it from the ide core.
> This would give us something like the following:
>
> hw/ide/piix.c (PIIX3 and PIIX4)
> hw/ide/pci.c and core.c (IDE, BM)
> hw/ata-core.c (ATA)
> hw/sata/ich6.c (ICH6)
> hw/sata-core.c (SATA)
> hw/ahci-core.c (AHCI)
>
> Should this be a goal or am i over-engineering here?
[CC'ing Tejun - he volunteered to help out on this topic as well]
I think there's no need to split sata and ahci.
Apart from that, I think we should take things incrementally. For now
there's no need to split IDE further until we hit a technical limit. I
have yet to see a patch trying to reuse the IDE command processing, so
depending on how the respective person implements that, I'm open to
suggenstions.
So as far as I'm concerned, I'd prefer to model things after they're
developed. That way we know the pitfalls.
Alex
next prev parent reply other threads:[~2010-05-09 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-09 16:01 [Qemu-devel] AHCI support integration Sebastian Herbszt
2010-05-09 19:11 ` Alexander Graf [this message]
2010-05-10 6:55 ` [Qemu-devel] " Tejun Heo
2010-05-10 8:12 ` Christoph Egger
2010-05-10 9:45 ` Joerg Roedel
2010-05-10 8:10 ` [Qemu-devel] " Christoph Egger
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=4BE708D5.5080405@suse.de \
--to=agraf@suse.de \
--cc=elek.roland@gmail.com \
--cc=herbszt@gmx.de \
--cc=joro@8bytes.org \
--cc=qemu-devel@nongnu.org \
--cc=qiaochong@loongson.cn \
--cc=teheo@suse.de \
/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).