From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH v3 4/4] xen: expose that grant table mappings update the IOMMU
Date: Mon, 26 May 2014 18:10:19 +0200 [thread overview]
Message-ID: <5383676B.2060405@citrix.com> (raw)
In-Reply-To: <53832A620200007800015A96@mail.emea.novell.com>
On 26/05/14 11:49, Jan Beulich wrote:
>>>> On 23.05.14 at 18:33, <roger.pau@citrix.com> wrote:
>> Add a new XENFEAT_hvm_gntmap_supports_iommu that is used to check
>> whether the hypervisor properly updates the IOMMU on auto-translated
>> guests when doing a grant table map/unmap operation.
>
> As said before, if this is indeed HVM-only (I assume PVH is being
> implied here), this should be exposed via the new CPUID leaf
> rather than via the feature map.
OK, I've been looking into this, but it seems that for PVH cpuid is
limited to 2 leafs only, so hvm_hypervisor_cpuid_leaf is never called.
Will look into expanding this, but then I should probably add some
checks to prevent PVH guests from reporting either
XEN_HVM_CPUID_APIC_ACCESS_VIRT or XEN_HVM_CPUID_X2APIC_VIRT for the time
being.
Roger.
prev parent reply other threads:[~2014-05-26 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 16:33 [PATCH v3 0/4] Fix grant map/unmap with auto-translated guests Roger Pau Monne
2014-05-23 16:33 ` [PATCH v3 1/4] xen: make logdirty and iommu mutually exclusive Roger Pau Monne
2014-05-26 9:45 ` Jan Beulich
2014-05-23 16:33 ` [PATCH v3 2/4] iommu: set correct IOMMU entries when iommu_hap_pt_share == 0 Roger Pau Monne
2014-05-23 17:23 ` Konrad Rzeszutek Wilk
2014-05-23 16:33 ` [PATCH v3 3/4] amd-iommu: disable iommu_hap_pt_share with AMD IOMMUs Roger Pau Monne
2014-05-23 16:33 ` [PATCH v3 4/4] xen: expose that grant table mappings update the IOMMU Roger Pau Monne
2014-05-26 9:49 ` Jan Beulich
2014-05-26 16:10 ` Roger Pau Monné [this message]
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=5383676B.2060405@citrix.com \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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.