From: Sasha Levin <sasha.levin@oracle.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Stefan Fritsch <sf@sfritsch.de>
Cc: kvm@vger.kernel.org, will.deacon@arm.com,
virtualization@lists.linux-foundation.org, penberg@iki.fi
Subject: Re: [PATCH RFC] virtio-pci: share config interrupt between virtio devices
Date: Sun, 21 Sep 2014 09:47:51 -0400 [thread overview]
Message-ID: <541ED707.4050100@oracle.com> (raw)
In-Reply-To: <20140921080914.GA2489@redhat.com>
On 09/21/2014 04:09 AM, Michael S. Tsirkin wrote:
>> The virtio 0.9.5 spec says that ISR is "unused" when in MSI-X mode. I
>> > don't think that you can depend on the device to set the configuration
>> > changed bit.
>> > The virtio 1.0 spec seems to have fixed that.
> Yes, virtio 0.9.5 has this bug. But in practice qemu always set this
> bit, so for qemu we could do that unconditionally. Pekka's lkvm tool
> doesn't unfortunately. It's easy to fix that, but it would be nicer to
> additionally probe for old versions of the tool, and disable IRQF_SHARED
> in that case.
>
> To complicate things, lkvm does not use a distinct subsystem vendor ID,
> in spite of the fact the virtio spec always required this explicitly.
I think I may be a bit confused here, but AFAIK we do set subsystem vendor
ID properly for our virtio-pci devices?
vpci->pci_hdr = (struct pci_device_header) {
.vendor_id = cpu_to_le16(PCI_VENDOR_ID_REDHAT_QUMRANET),
.device_id = cpu_to_le16(device_id),
[...]
.subsys_vendor_id = cpu_to_le16(PCI_SUBSYSTEM_VENDOR_ID_REDHAT_QUMRANET),
Thanks,
Sasha
next prev parent reply other threads:[~2014-09-21 13:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 5:41 [PATCH RFC] virtio-pci: share config interrupt between virtio devices Amos Kong
2014-09-01 6:37 ` Michael S. Tsirkin
2014-09-01 7:58 ` Amos Kong
2014-09-01 8:12 ` Michael S. Tsirkin
2014-09-18 19:18 ` Stefan Fritsch
[not found] ` <11860049.kd4R4PIiz4@k>
2014-09-21 8:09 ` Michael S. Tsirkin
2014-09-21 9:36 ` Stefan Fritsch
2014-09-21 10:21 ` Michael S. Tsirkin
2014-09-23 20:47 ` Stefan Fritsch
2014-09-21 13:47 ` Sasha Levin [this message]
2014-09-21 15:02 ` Michael S. Tsirkin
2014-09-21 15:19 ` Sasha Levin
2014-09-21 17:53 ` Michael S. Tsirkin
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=541ED707.4050100@oracle.com \
--to=sasha.levin@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=penberg@iki.fi \
--cc=sf@sfritsch.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=will.deacon@arm.com \
/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).