All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Luca Tettamanti <kronos.it@gmail.com>,
	kvm@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: lspci says: "SCSI storage controller: Qumranet, Inc. Virtio block device". Is it really?
Date: Mon, 19 Oct 2009 15:48:08 +0200	[thread overview]
Message-ID: <4ADC6E18.4080505@redhat.com> (raw)
In-Reply-To: <4ADC6CDC.3000409@wpkg.org>

On 10/19/2009 03:42 PM, Tomasz Chmielewski wrote:
> Luca Tettamanti wrote:
>
>>> So why was "SCSI storage controller" any better than "IDE interface" or
>>> "SATA controller" for virtio block device, if it does not talk SCSI 
>>> protocol
>>> (other than "SCSI storage controller" being the first on the list of
>>> subclasses)?
>>
>> Because both ATA and SATA classes have a generic driver that would try
>> to bind to that controller (and the whole point of virtio block device
>> is to avoid emulating a ATA/SATA controller).
>>
>>> Doesn't "80  Mass storage controller" ("0x80    0x00    Other mass 
>>> storage
>>> controller") fit better for virtio block device?
>>
>> Maybe. I guess that are compatibility problem with "other" operating 
>> systems.
>
> Thanks for clarifications.
>
> It makes sense in that case - I don't have any more questions ;)
>
>
we need it for windows viostor driver to be WHQL'ed

  reply	other threads:[~2009-10-19 13:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-19 12:14 lspci says: "SCSI storage controller: Qumranet, Inc. Virtio block device". Is it really? Tomasz Chmielewski
2009-10-19 13:09 ` Luca Tettamanti
2009-10-19 13:31   ` Tomasz Chmielewski
2009-10-19 13:36     ` Luca Tettamanti
2009-10-19 13:42       ` Tomasz Chmielewski
2009-10-19 13:48         ` Vadim Rozenfeld [this message]
2009-10-19 19:01     ` Gerd Hoffmann

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=4ADC6E18.4080505@redhat.com \
    --to=vrozenfe@redhat.com \
    --cc=kronos.it@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mangoo@wpkg.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.