From: Sheng Yang <sheng@linux.intel.com>
To: kvm@vger.kernel.org
Cc: Gregory Haskins <gregory.haskins@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Matthew Wilcox <willy@linux.intel.com>
Subject: Re: KVM_ASSIGN_SET_MSIX_NR and KVM_ASSIGN_SET_MSIX_ENTRY should support MSI?
Date: Wed, 20 May 2009 16:48:17 +0800 [thread overview]
Message-ID: <200905201648.18249.sheng@linux.intel.com> (raw)
In-Reply-To: <4A00230A.70607@gmail.com>
On Tuesday 05 May 2009 19:29:14 Gregory Haskins wrote:
> 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
Hi
Sorry for I don't have time to work at it recently... And Avi's review
patchset reminded me the merge for 2.6.31 would be soon. Anyone have
interesting to get this done?
Thanks!
--
regards
Yang, Sheng
prev parent reply other threads:[~2009-05-20 8:47 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
2009-05-20 8:48 ` Sheng Yang [this message]
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=200905201648.18249.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=avi@redhat.com \
--cc=gregory.haskins@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.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 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).