public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
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: [PATCH 1/2] VT-d: Changes to support KVM
Date: Wed, 10 Sep 2008 18:53:28 +0300	[thread overview]
Message-ID: <48C7ED78.9080201@qumranet.com> (raw)
In-Reply-To: <1220974650-9444-2-git-send-email-amit.shah@qumranet.com>

Amit Shah wrote:
> From: Kay, Allen M <allen.m.kay@intel.com>
>
> This patch extends the VT-d driver to support KVM
>
> [Ben: fixed memory pinning]
>
> Signed-off-by: Kay, Allen M <allen.m.kay@intel.com>
> Signed-off-by: Weidong Han <weidong.han@intel.com>
> Signed-off-by: Ben-Ami Yassour <benami@il.ibm.com>
> Signed-off-by: Amit Shah <amit.shah@qumranet.com>
>
> Acked-by: Mark Gross <mgross@linux.intel.com>
> ---
>  drivers/pci/dmar.c          |    4 +-
>  drivers/pci/intel-iommu.c   |  116 ++++++++++++++-
>  drivers/pci/intel-iommu.h   |  344 -----------------------------------------
>  drivers/pci/iova.c          |    2 +-
>  drivers/pci/iova.h          |   52 -------
>  include/linux/intel-iommu.h |  355 +++++++++++++++++++++++++++++++++++++++++++
>  include/linux/iova.h        |   52 +++++++
>  7 files changed, 522 insertions(+), 403 deletions(-)
>  delete mode 100644 drivers/pci/intel-iommu.h
>  delete mode 100644 drivers/pci/iova.h
>  create mode 100644 include/linux/intel-iommu.h
>  create mode 100644 include/linux/iova.h
>   

Please resend with git's -M option, so we can review the file moves.


-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2008-09-10 15:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 15:37 VT-d support for device assignment Amit Shah
2008-09-09 15:37 ` [PATCH 1/2] VT-d: Changes to support KVM Amit Shah
2008-09-09 15:37   ` [PATCH 2/2] KVM: Device Assignment with VT-d Amit Shah
2008-09-11  7:21     ` Han, Weidong
2008-09-14  0:49       ` Avi Kivity
2008-09-10 15:53   ` Avi Kivity [this message]
2008-09-10 18:11     ` [PATCH 1/2] VT-d: Changes to support KVM Jesse Barnes
2008-09-10 19:06       ` David Woodhouse
2008-09-11  6:11     ` Han, Weidong
2008-09-14  0:46 ` VT-d support for device assignment Avi Kivity
2008-09-23 18:57   ` Jesse Barnes
  -- strict thread matches above, loose matches on Subject: below --
2008-09-09 14:44 Amit Shah
2008-09-09 14:44 ` [PATCH 1/2] VT-d: Changes to support KVM Amit Shah
2008-09-09 13:51 [PATCH 1/2] VT-d: changes " Han, Weidong
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-21 11:10 VT-d support for device assignment Ben-Ami Yassour
2008-08-21 11:10 ` [PATCH 1/2] VT-d: changes to support KVM Ben-Ami Yassour
2008-08-07 14:14 Ben-Ami Yassour
2008-08-13  9:21 ` Yang, Sheng
2008-08-13  9:21   ` 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=48C7ED78.9080201@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