From: Stefan Weil <weil@mail.berlios.de>
To: Blue Swirl <blauwirbel@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Move block format drivers to new directory 'bdrv'
Date: Sun, 26 Apr 2009 23:26:03 +0200 [thread overview]
Message-ID: <49F4D16B.6010700@mail.berlios.de> (raw)
In-Reply-To: <f43fc5580904261110g741a4865ld6d36995514bd18c@mail.gmail.com>
Blue Swirl schrieb:
> On 4/26/09, Anthony Liguori <anthony@codemonkey.ws> wrote:
>
>> Avi Kivity wrote:
>>
>>
>>> Blue Swirl wrote:
>>>
>>>
>>>> Taking one step further, why not introduce directories similar to
>>>>
>> VirtualBox:
>>
>>>> http://www.virtualbox.org/browser/trunk/src/VBox
>>>>
>>>>
>>>>
>>>>
>>> No objection, but let's go one step at a time.
>>>
>>>
>> I was going to suggest exactly the same thing. It would be good for
>> someone to look at making a more logical layout in hw/.
>>
>
> hw could be arranged the same way, renamed to 'target':
>
> target
> |-- audio
> |-- block
> |-- bluetooth
> |-- boards
> | |-- alpha
> | |-- arm
> | |-- cris
> | |-- i386
> | |-- m68k
> | |-- mips
> | |-- ppc
> | |-- sh4
> | |-- sparc
> | |-- sparc64
> | `-- x86_64
> |-- input
> |-- irq
> |-- isa
> |-- mtd
> |-- net
> |-- pci
> |-- scsi
> |-- serial
> |-- timer
> |-- usb
> |-- video
> `-- xen
>
>
>
... or similar to linux kernel structure?
target
|-- arch
| |-- ...
|-- drivers
| |-- ...
Then it's clearer where the emulation code for a PC board (i386 or x86_64?),
a network card (pci or net?) or others should be placed.
next prev parent reply other threads:[~2009-04-26 21:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 15:19 [Qemu-devel] [PATCH] Move block format drivers to new directory 'bdrv' Avi Kivity
2009-04-26 15:29 ` Christoph Hellwig
2009-04-26 15:55 ` Avi Kivity
2009-04-26 16:18 ` Blue Swirl
2009-04-26 16:20 ` Avi Kivity
2009-04-26 16:40 ` Blue Swirl
2009-04-26 17:04 ` Avi Kivity
2009-04-26 17:44 ` Anthony Liguori
2009-04-26 17:56 ` Christoph Hellwig
2009-04-26 18:06 ` Avi Kivity
2009-04-26 17:41 ` Anthony Liguori
2009-04-26 18:10 ` Blue Swirl
2009-04-26 21:26 ` Stefan Weil [this message]
2009-04-27 12:14 ` Kevin Wolf
2009-04-27 13:52 ` Jamie Lokier
2009-04-27 14:37 ` M. Warner Losh
2009-04-27 12:08 ` Kevin Wolf
2009-04-27 12:10 ` Avi Kivity
2009-04-27 12:17 ` Kevin Wolf
2009-05-02 10:34 ` Stuart Brady
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=49F4D16B.6010700@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=blauwirbel@gmail.com \
--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).