From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
qemu-devel@nongnu.org
Subject: Re: updated: kvm PCI todo wiki
Date: Thu, 22 Aug 2013 11:27:22 +0300 [thread overview]
Message-ID: <20130822082722.GA22117@redhat.com> (raw)
In-Reply-To: <1377160174.32763.61.camel@haakon3.risingtidesystems.com>
On Thu, Aug 22, 2013 at 01:29:34AM -0700, Nicholas A. Bellinger wrote:
> On Wed, 2013-08-21 at 14:45 +0200, Hannes Reinecke wrote:
> > On 08/21/2013 12:48 PM, Michael S. Tsirkin wrote:
> > > Hey guys,
> > > I've put up a wiki page with a kvm PCI todo list,
> > > mainly to avoid effort duplication, but also in the hope
> > > to draw attention to what I think we should try addressing
> > > in KVM:
> > >
> > > http://www.linux-kvm.org/page/PCITodo
> > >
> > > This page could cover all PCI related activity in KVM,
> > > it is very incomplete.
> > > We should probably add e.g. IOMMU related stuff.
> > >
> > > Note: if there's no developer listed for an item,
> > > this just means I don't know of anyone actively working
> > > on an issue at the moment, not that no one intends to.
> > >
> > > I would appreciate it if others working on one of the items on this list
> > > would add their names so we can communicate better. If others like this
> > > wiki page, please go ahead and add stuff you are working on if any.
> > >
> > > It would be especially nice to add testing projects.
> > >
> > > Also, feel free to add links to bugzillas items.
> > >
> > On a related note, did anyone ever tried to test MSI / MSI-X with a
> > windows guest? I've tried to enable it for virtio but for some reason
> > Windows didn't wanted to enable it. AHCI was even worse; the stock
> > Windows version doesn't support MSI and the Intel one doesn't like our
> > implementation :-(.
> >
> > Anyone ever managed to get this to work?
> >
> > If not it'd be a good topic for the wiki ...
> >
>
> Speaking of which, I asked Asias about this recently and he seems to
> think that virtio-net + virtio-blk drivers for MSFT do in fact support
> MSI /MSI-X.
>
> MST, do you know if that that true..?
>
> --nab
Yes, they do for modern windows versions.
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: Asias He <asias@redhat.com>,
virtualization@lists.linux-foundation.org,
Hannes Reinecke <hare@suse.de>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] updated: kvm PCI todo wiki
Date: Thu, 22 Aug 2013 11:27:22 +0300 [thread overview]
Message-ID: <20130822082722.GA22117@redhat.com> (raw)
In-Reply-To: <1377160174.32763.61.camel@haakon3.risingtidesystems.com>
On Thu, Aug 22, 2013 at 01:29:34AM -0700, Nicholas A. Bellinger wrote:
> On Wed, 2013-08-21 at 14:45 +0200, Hannes Reinecke wrote:
> > On 08/21/2013 12:48 PM, Michael S. Tsirkin wrote:
> > > Hey guys,
> > > I've put up a wiki page with a kvm PCI todo list,
> > > mainly to avoid effort duplication, but also in the hope
> > > to draw attention to what I think we should try addressing
> > > in KVM:
> > >
> > > http://www.linux-kvm.org/page/PCITodo
> > >
> > > This page could cover all PCI related activity in KVM,
> > > it is very incomplete.
> > > We should probably add e.g. IOMMU related stuff.
> > >
> > > Note: if there's no developer listed for an item,
> > > this just means I don't know of anyone actively working
> > > on an issue at the moment, not that no one intends to.
> > >
> > > I would appreciate it if others working on one of the items on this list
> > > would add their names so we can communicate better. If others like this
> > > wiki page, please go ahead and add stuff you are working on if any.
> > >
> > > It would be especially nice to add testing projects.
> > >
> > > Also, feel free to add links to bugzillas items.
> > >
> > On a related note, did anyone ever tried to test MSI / MSI-X with a
> > windows guest? I've tried to enable it for virtio but for some reason
> > Windows didn't wanted to enable it. AHCI was even worse; the stock
> > Windows version doesn't support MSI and the Intel one doesn't like our
> > implementation :-(.
> >
> > Anyone ever managed to get this to work?
> >
> > If not it'd be a good topic for the wiki ...
> >
>
> Speaking of which, I asked Asias about this recently and he seems to
> think that virtio-net + virtio-blk drivers for MSFT do in fact support
> MSI /MSI-X.
>
> MST, do you know if that that true..?
>
> --nab
Yes, they do for modern windows versions.
next prev parent reply other threads:[~2013-08-22 8:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 10:48 updated: kvm PCI todo wiki Michael S. Tsirkin
2013-08-21 10:48 ` [Qemu-devel] " Michael S. Tsirkin
2013-08-21 12:45 ` Hannes Reinecke
2013-08-21 12:45 ` [Qemu-devel] " Hannes Reinecke
2013-08-21 11:52 ` Vadim Rozenfeld
2013-08-21 11:52 ` [Qemu-devel] " Vadim Rozenfeld
2013-08-21 12:05 ` Michael S. Tsirkin
2013-08-21 12:05 ` Michael S. Tsirkin
2013-08-21 12:05 ` [Qemu-devel] " Michael S. Tsirkin
2013-08-22 8:29 ` Nicholas A. Bellinger
2013-08-22 8:29 ` Nicholas A. Bellinger
2013-08-22 8:29 ` [Qemu-devel] " Nicholas A. Bellinger
2013-08-22 8:27 ` Michael S. Tsirkin [this message]
2013-08-22 8:27 ` 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=20130822082722.GA22117@redhat.com \
--to=mst@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.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.