From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm <kvm@vger.kernel.org>, Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH] KVM: Fix signature of kvm_iommu_map_pages stub
Date: Thu, 14 Oct 2010 14:43:51 +0200 [thread overview]
Message-ID: <4CB6FB07.10209@siemens.com> (raw)
In-Reply-To: <4CB6F088.2060007@siemens.com>
Am 14.10.2010 13:59, Jan Kiszka wrote:
> Breaks otherwise if CONFIG_IOMMU_API is not set.
Actually, it only broke a special local version. It doesn't break with
current KVM due to
[__kvm_set_memory_region:]
#ifdef CONFIG_DMAR
/* map the pages in iommu page table */
if (npages) {
r = kvm_iommu_map_pages(kvm, &new);
if (r)
goto out_free;
}
#endif
And CONFIG_IOMMU_API is set when CONFIG_DMAR is enabled. But do we only
need this call on Intel?
Jan
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> include/linux/kvm_host.h | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h
> index 0b89d00..866ed30 100644
> --- a/include/linux/kvm_host.h
> +++ b/include/linux/kvm_host.h
> @@ -483,8 +483,7 @@ int kvm_deassign_device(struct kvm *kvm,
> struct kvm_assigned_dev_kernel *assigned_dev);
> #else /* CONFIG_IOMMU_API */
> static inline int kvm_iommu_map_pages(struct kvm *kvm,
> - gfn_t base_gfn,
> - unsigned long npages)
> + struct kvm_memory_slot *slot)
> {
> return 0;
> }
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-10-14 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 11:59 [PATCH] KVM: Fix signature of kvm_iommu_map_pages stub Jan Kiszka
2010-10-14 12:43 ` Jan Kiszka [this message]
2010-10-18 13:04 ` Marcelo Tosatti
2010-10-18 13:11 ` Jan Kiszka
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=4CB6FB07.10209@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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.