All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Amit Shah <amit.shah@qumranet.com>
Cc: avi@qumranet.com, kvm@vger.kernel.org, muli@il.ibm.com,
	anthony@codemonkey.ws, jesse.barnes@intel.com,
	david.woodhouse@intel.com, mark.gross@intel.com,
	benami@il.ibm.com, weidong.han@intel.com
Subject: Re: VT-d support for device assignment
Date: Mon, 1 Sep 2008 15:08:37 +0200	[thread overview]
Message-ID: <20080901130837.GE4895@8bytes.org> (raw)
In-Reply-To: <1219389054-15332-1-git-send-email-amit.shah@qumranet.com>

On Fri, Aug 22, 2008 at 10:10:52AM +0300, 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.
> 
> I've updated the 2nd patch to use VT-d only when requested by a parameter
> on the command line, making it easier to support iommu with pvdma and
> multiple iommu types.
> 
> The command line currently should be invoked as:
> 
> -pcidevice dev=00:13.0,vtd=on


I don't like the vtd=on flag. I think its not good to have seperate
parameters for Intel and AMD IOMMUs. So I think a parameter called
iommu=on is the better choice.

Joerg


  parent reply	other threads:[~2008-09-01 13:08 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22  7:10 VT-d support for device assignment Amit Shah
2008-08-22  7:10 ` [PATCH] VT-d: changes to support KVM Amit Shah
2008-08-22  7:10   ` [PATCH] KVM: Device Assignment with VT-d Amit Shah
2008-08-23 16:21   ` [PATCH] VT-d: changes to support KVM Jesse Barnes
2008-08-22 13:54 ` VT-d support for device assignment 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 [this message]
  -- 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-26  8:55 Amit Shah
2008-08-26  9:10 ` Avi Kivity
2008-08-26 14:11   ` Amit Shah
2008-08-26 14:38     ` Avi Kivity
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=20080901130837.GE4895@8bytes.org \
    --to=joro@8bytes.org \
    --cc=amit.shah@qumranet.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=benami@il.ibm.com \
    --cc=david.woodhouse@intel.com \
    --cc=jesse.barnes@intel.com \
    --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 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.