From: Gregory Haskins <gregory.haskins@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Sheng Yang <sheng@linux.intel.com>, Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Matthew Wilcox <willy@linux.intel.com>,
kvm@vger.kernel.org
Subject: Re: KVM_ASSIGN_SET_MSIX_NR and KVM_ASSIGN_SET_MSIX_ENTRY should support MSI?
Date: Tue, 05 May 2009 07:29:14 -0400 [thread overview]
Message-ID: <4A00230A.70607@gmail.com> (raw)
In-Reply-To: <20090505103028.GA15418@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
Michael S. Tsirkin wrote:
> The new KVM_ASSIGN_SET_MSIX_NR and KVM_ASSIGN_SET_MSIX_ENTRY ioctls have
> been merged for 2.6.30. However, I note that PCI spec allows devices to
> support multiple vectors with MSI as well (support will be in linux
> 2.6.30).
>
> Even though qemu for now only uses a single vector with MSI, it would
> seem that it's better to make the kernel/user interface generic straight
> away rather than add more ioctls later. What do you think? It might not
> be too late to fix this for 2.6.30.
>
+1
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 266 bytes --]
next prev parent reply other threads:[~2009-05-05 11:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 10:30 KVM_ASSIGN_SET_MSIX_NR and KVM_ASSIGN_SET_MSIX_ENTRY should support MSI? Michael S. Tsirkin
2009-05-05 11:04 ` Marcelo Tosatti
2009-05-05 11:08 ` Michael S. Tsirkin
2009-05-05 11:57 ` Avi Kivity
2009-05-05 12:01 ` Michael S. Tsirkin
2009-05-05 12:08 ` Avi Kivity
2009-05-05 12:39 ` Michael S. Tsirkin
2009-05-05 12:57 ` Michael S. Tsirkin
2009-05-05 13:30 ` Avi Kivity
2009-05-06 3:11 ` Sheng Yang
2009-05-05 11:29 ` Gregory Haskins [this message]
2009-05-20 8:48 ` Sheng Yang
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=4A00230A.70607@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.com \
--cc=willy@linux.intel.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 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.