All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Bug 1594239 <1594239@bugs.launchpad.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1594239] Re: After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error
Date: Tue, 5 Jul 2016 16:02:30 +0100	[thread overview]
Message-ID: <CAFEAcA_0i-B41JjL_2GTb56UQdxf_GhZHegxWpjtCEbFumWD2Q@mail.gmail.com> (raw)
In-Reply-To: <20160705144121.14300.19514.malone@soybean.canonical.com>

On 5 July 2016 at 15:41, Tom Hanson <thomas.hanson@linaro.org> wrote:
> As noted above, virtio-scsi-pci uses a bus address as part of the
> internal ID string while virtio-scsi-device does not.
>
>   * Is this difference intentional?

Probably not.

>   * Are they intended to support different use cases? If so, what?

virtio-scsi-device is a "virtio backend" (other backends
include char, block and net devices), which plugs into a
"virtio bus". Virtio buses are provided by "virtio transports",
which can be PCI, s390 CCW, or virtio-mmio, and any particular
virtio bus has either 0 or 1 virtio backends on it.

The general idea is that this is a clean-ish separation between
the "what is this virtio device doing" and "how exactly do you
access it". virtio-scsi-pci is one of the family of virtio-*-pci
devices which combine a virtio-pci transport and a virtio-foo
backend in one convenient package -- we provide these (a) for
backward compatibility with old command lines etc from before
we made the backend/transport split and (b) for convenience
since the command lines are shorter than if you specify
the transport and backend separately manually.

(Note that a virtio-pci transport is a pci device, not a
pci bus -- it plugs into a pci bus on one and has a
virtio-bus on the other.)

thanks
-- PMM

  reply	other threads:[~2016-07-05 15:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20  3:21 [Qemu-devel] [Bug 1594239] [NEW] After adding more scsi disks for Aarch64 virtual machine, start the VM and got Qemu Error Kevin Zhao
2016-06-27 14:53 ` [Qemu-devel] [Bug 1594239] " Peter Maydell
2016-06-28 13:37 ` Kevin Zhao
2016-06-28 16:46 ` Cole Robinson
2016-06-28 17:22 ` Dr. David Alan Gilbert
2016-07-01  0:45 ` Tom Hanson
2016-07-01  4:21 ` Tom Hanson
2016-07-01  8:27 ` Dr. David Alan Gilbert
2016-07-01 14:22   ` Tom Hanson
2016-07-01 15:08 ` Dr. David Alan Gilbert
2016-07-01 22:33   ` Tom Hanson
2016-07-02  1:07 ` Tom Hanson
2016-07-02  9:19 ` Laszlo Ersek (Red Hat)
2016-07-05 14:41 ` Tom Hanson
2016-07-05 15:02   ` Peter Maydell [this message]
2016-07-05 15:03     ` Peter Maydell
2016-07-05 14:58 ` Dr. David Alan Gilbert
2016-07-05 15:20 ` Tom Hanson
2016-07-05 16:29   ` Peter Maydell
2016-07-05 16:43     ` Tom Hanson
2016-07-05 19:57       ` Peter Maydell
2016-07-05 15:29 ` Laszlo Ersek (Red Hat)
2016-07-05 15:46   ` Tom Hanson
2016-07-05 15:47 ` Laszlo Ersek (Red Hat)
2016-07-05 16:34 ` Tom Hanson
2016-07-05 17:50 ` Laszlo Ersek (Red Hat)
2016-07-05 19:10 ` Tom Hanson
2016-07-05 19:26 ` Laszlo Ersek (Red Hat)
2016-07-05 20:22   ` Tom Hanson
2016-07-05 20:40     ` Tom Hanson
2016-07-14 18:04 ` Laszlo Ersek (Red Hat)
2016-09-02 21:34 ` T. Huth
2016-11-18 22:52 ` PabloSaenz

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=CAFEAcA_0i-B41JjL_2GTb56UQdxf_GhZHegxWpjtCEbFumWD2Q@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=1594239@bugs.launchpad.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.