From: Jan Beulich <jbeulich@suse.com>
To: Roger Pau Monne <roger.pau@citrix.com>
Cc: Juergen Gross <jgross@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Paul Durrant <Paul.Durrant@citrix.com>
Subject: Re: [Xen-devel] [PATCH] x86/iommu: fix hwdom iommu requirements check
Date: Mon, 30 Sep 2019 11:00:02 +0200 [thread overview]
Message-ID: <d54a0367-a9e0-048d-95a7-1e9f89e73077@suse.com> (raw)
In-Reply-To: <95aa17310e8b46619a0a701e416d6c47@AMSPEX02CL03.citrite.net>
On 30.09.2019 09:52, Paul Durrant wrote:
>> -----Original Message-----
>> From: Roger Pau Monne <roger.pau@citrix.com>
>> Sent: 28 September 2019 09:27
>> To: xen-devel@lists.xenproject.org
>> Cc: Roger Pau Monne <roger.pau@citrix.com>; Jan Beulich <jbeulich@suse.com>; Paul Durrant
>> <Paul.Durrant@citrix.com>; Juergen Gross <jgross@suse.com>
>> Subject: [PATCH] x86/iommu: fix hwdom iommu requirements check
>>
>> Both a shadow and a HAP hwdom require an iommu and must be run in
>> strict mode. Change the HAP check into a hvm domain check.
>>
>> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>
> Yes, I completely forgot that it is legitimate for a PVH dom0 to operate in shadow mode.
>
> Reviewed-by: Paul Durrant <paul.durrant@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-09-30 9:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-28 8:26 [Xen-devel] [PATCH] x86/iommu: fix hwdom iommu requirements check Roger Pau Monne
2019-09-30 6:07 ` Jürgen Groß
2019-09-30 7:52 ` Paul Durrant
2019-09-30 9:00 ` Jan Beulich [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=d54a0367-a9e0-048d-95a7-1e9f89e73077@suse.com \
--to=jbeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=jgross@suse.com \
--cc=roger.pau@citrix.com \
--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.