From: Avi Kivity <avi@qumranet.com>
To: Amit Shah <amit.shah@qumranet.com>
Cc: kvm@vger.kernel.org, muli@il.ibm.com, anthony@codemonkey.ws,
jbarnes@virtuousgeek.org, david.woodhouse@intel.com,
mark.gross@intel.com, benami@il.ibm.com, weidong.han@intel.com,
allen.m.kay@intel.com
Subject: Re: VT-d support for device assignment
Date: Tue, 26 Aug 2008 12:10:57 +0300 [thread overview]
Message-ID: <48B3C8A1.6070801@qumranet.com> (raw)
In-Reply-To: <1219740935-19701-1-git-send-email-amit.shah@qumranet.com>
Amit Shah wrote:
> The following two patches contain VT-d support for device assignment for KVM guests.
>
> The first patch contains the changes that are required to the generic VT-d code.
>
> The second patch contains the changes to KVM.
>
> Since the last send, I've updated the 2nd patch to expose KVM_CAP_IOMMU and check for the existence of an IOMMU before using one. I've also preserved the 'From' field for both the patches so that the original authors are credited for the patches.
>
> The command line currently should be invoked with the parameter:
>
> -pcidevice dev=00:13.0,dma=iommu
>
Why not default to iommu if one is available?
btw, -usbdevice prefixes host devices with host:, no? maybe adopt the
convention for -pcidevice?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-08-26 9:10 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-26 8:55 VT-d support for device assignment Amit Shah
2008-08-26 8:55 ` [PATCH 1/2] VT-d: changes to support KVM Amit Shah
2008-08-26 8:55 ` [PATCH 2/2] KVM: Device Assignment with VT-d Amit Shah
2008-08-26 10:28 ` Zhang, Xiantao
2008-08-26 10:35 ` Amit Shah
2008-08-26 10:42 ` Zhang, Xiantao
2008-08-26 10:57 ` Amit Shah
2008-08-26 11:04 ` Zhang, Xiantao
2008-08-26 14:41 ` Avi Kivity
2008-08-26 15:09 ` Han, Weidong
2008-09-03 16:52 ` Amit Shah
2008-09-09 7:18 ` Han, Weidong
2008-08-26 9:10 ` Avi Kivity [this message]
2008-08-26 14:11 ` VT-d support for device assignment Amit Shah
2008-08-26 14:38 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-09-09 15:37 Amit Shah
2008-09-14 0:46 ` Avi Kivity
2008-09-23 18:57 ` Jesse Barnes
2008-09-09 14:44 Amit Shah
2008-09-09 13:50 Han, Weidong
2008-08-22 7:10 Amit Shah
2008-08-22 13:54 ` Byron Stanoszek
2008-08-22 15:32 ` Amit Shah
2008-08-22 18:29 ` Muli Ben-Yehuda
2008-08-22 18:37 ` Avi Kivity
2008-08-22 19:09 ` Muli Ben-Yehuda
2008-08-22 16:08 ` Muli Ben-Yehuda
2008-08-22 18:12 ` Avi Kivity
2008-08-22 18:23 ` Muli Ben-Yehuda
2008-08-22 18:21 ` Avi Kivity
2008-08-22 18:28 ` Muli Ben-Yehuda
2008-08-23 9:12 ` Amit Shah
2008-08-23 9:33 ` Avi Kivity
2008-08-23 9:49 ` Amit Shah
2008-08-24 10:01 ` Avi Kivity
2008-08-23 9:50 ` Muli Ben-Yehuda
2008-08-23 9:55 ` Muli Ben-Yehuda
2008-08-24 10:02 ` Avi Kivity
2008-08-23 9:57 ` Muli Ben-Yehuda
2008-08-23 10:25 ` Amit Shah
2008-08-23 10:40 ` Muli Ben-Yehuda
2008-08-23 11:11 ` Amit Shah
2008-08-23 12:11 ` Muli Ben-Yehuda
2008-08-23 14:01 ` Amit Shah
2008-09-01 13:08 ` Joerg Roedel
2008-08-21 11:10 Ben-Ami Yassour
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=48B3C8A1.6070801@qumranet.com \
--to=avi@qumranet.com \
--cc=allen.m.kay@intel.com \
--cc=amit.shah@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=benami@il.ibm.com \
--cc=david.woodhouse@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=muli@il.ibm.com \
--cc=weidong.han@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