From: Avi Kivity <avi@redhat.com>
To: KVM list <kvm@vger.kernel.org>
Subject: iommu external module
Date: Thu, 02 Oct 2008 15:45:33 +0300 [thread overview]
Message-ID: <48E4C26D.6030608@redhat.com> (raw)
When userspace support for device assignment is merged, we will finally
have full support for device assignment. Unfortunately, many users
won't be able to test or use device assignment, since very few actually
run development kernels. The first stable kernel with enough iommu
support for kvm will be 2.6.28, released in about three months, and
distros are even further away.
We can fix this fairly simply by having an external module for the
iommus, much like kvm itself. I don't think it should be too difficult,
and it will provide a lot of testing to us, and important functionality
for our users.
Anyone willing to pick this up?
--
error compiling committee.c: too many arguments to function
next reply other threads:[~2008-10-02 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 12:45 Avi Kivity [this message]
2008-10-02 14:58 ` iommu external module Muli Ben-Yehuda
2008-10-02 15:30 ` Avi Kivity
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=48E4C26D.6030608@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.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 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).