From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] drive_add vs. pci_add
Date: Thu, 25 Jun 2009 18:39:01 +0300 [thread overview]
Message-ID: <4A439A15.5040707@redhat.com> (raw)
In-Reply-To: <4A431D3D.2040604@web.de>
On 06/25/2009 09:46 AM, Jan Kiszka wrote:
> Hi,
>
> sorry, it's still early, but isn't the monitor command 'drive_add'
> completely redundant to 'pci_add ... storage'? If yes, and drive_add is
> only there for legacy users, I would mask its help from the monitor
> interface to avoid confusion.
>
What we really want is pci_add storage to add a storage controller, and
drive_add to attach a drive to that controller. I don't think that's
what happens now.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-25 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 6:46 [Qemu-devel] drive_add vs. pci_add Jan Kiszka
2009-06-25 7:15 ` [Qemu-devel] " Jan Kiszka
2009-06-25 15:39 ` Avi Kivity [this message]
2009-06-25 16:02 ` [Qemu-devel] " Paul Brook
2009-06-25 18:28 ` Anthony Liguori
2009-06-25 21:09 ` Jan Kiszka
2009-06-25 22:18 ` Paul Brook
2009-06-25 16:07 ` Jan Kiszka
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=4A439A15.5040707@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@web.de \
--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).