From: Avi Kivity <avi@qumranet.com>
To: Ben-Ami Yassour <benami@il.ibm.com>
Cc: amit.shah@qumranet.com, kvm@vger.kernel.org, muli@il.ibm.com,
weidong.han@intel.com, "Kay, Allen M" <allen.m.kay@intel.com>
Subject: Re: [PATCH] VT-d : changes to support KVM
Date: Sat, 05 Jul 2008 13:55:00 +0300 [thread overview]
Message-ID: <486F5304.4070307@qumranet.com> (raw)
In-Reply-To: <1215012800-18550-2-git-send-email-benami@il.ibm.com>
Ben-Ami Yassour 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>
> ---
> drivers/pci/dmar.c | 4 +-
> drivers/pci/intel-iommu.c | 117 ++++++++++++++-
> drivers/pci/intel-iommu.h | 344 -------------------------------------------
> drivers/pci/iova.c | 2 +-
> drivers/pci/iova.h | 52 -------
> include/linux/intel-iommu.h | 344 +++++++++++++++++++++++++++++++++++++++++++
> include/linux/iova.h | 52 +++++++
> 7 files changed, 512 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 use the git diff '-M' flag (or set the 'diff.renames' config
variable) so rename patches are reviewable.
>
> +void kvm_intel_iommu_domain_exit(struct dmar_domain *domain)
> +{
> + u64 end;
> +
> + /* Domain 0 is reserved, so dont process it */
> + if (!domain)
> + return;
> +
> + end = DOMAIN_MAX_ADDR(domain->gaw);
> + end = end & (~PAGE_MASK_4K);
> +
> + /* clear ptes */
> + dma_pte_clear_range(domain, 0, end);
> +
> + /* free page tables */
> + dma_pte_free_pagetable(domain, 0, end);
> +
> + iommu_free_domain(domain);
> + free_domain_mem(domain);
> +}
> +EXPORT_SYMBOL_GPL(kvm_intel_iommu_domain_exit);
>
I don't understand why the names are prefixed with 'kvm_'. These are
not kvm functions.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-07-05 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 15:33 VT-d pci passthrough patches Ben-Ami Yassour
2008-07-02 15:33 ` [PATCH] VT-d : changes to support KVM Ben-Ami Yassour
2008-07-02 15:33 ` [PATCH] KVM: PCIPT: VT-d support Ben-Ami Yassour
2008-07-03 4:55 ` Han, Weidong
2008-07-06 11:15 ` Ben-Ami Yassour
[not found] ` <08DF4D958216244799FC84F3514D70F00181AB10@pdsmsx415.ccr.corp.intel.com>
2008-07-03 6:16 ` Han, Weidong
2008-07-03 11:33 ` Ben-Ami Yassour
2008-07-05 10:55 ` Avi Kivity [this message]
2008-07-06 11:12 ` [PATCH] VT-d : changes to support KVM Ben-Ami Yassour
-- strict thread matches above, loose matches on Subject: below --
2008-07-06 10:52 VT-d pci passthrough patches Ben-Ami Yassour
2008-07-06 10:52 ` [PATCH] VT-d : changes to support KVM Ben-Ami Yassour
2008-07-10 9:14 VT-d pci passthrough patches Ben-Ami Yassour
2008-07-10 9:14 ` [PATCH] VT-d : changes to support KVM Ben-Ami Yassour
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-23 16:21 ` Jesse Barnes
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=486F5304.4070307@qumranet.com \
--to=avi@qumranet.com \
--cc=allen.m.kay@intel.com \
--cc=amit.shah@qumranet.com \
--cc=benami@il.ibm.com \
--cc=kvm@vger.kernel.org \
--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.