From: Bertrand Marquis <Bertrand.Marquis@arm.com>
To: Julien Grall <julien@xen.org>
Cc: "open list:X86" <xen-devel@lists.xenproject.org>,
Julien Grall <jgrall@amazon.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
Ian Jackson <iwj@xenproject.org>, Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: Re: [PATCH] SUPPORT.MD: Clarify the support state for the Arm SMMUv{1, 2} drivers
Date: Wed, 23 Sep 2020 10:50:43 +0000 [thread overview]
Message-ID: <1D6392F2-F4EC-4025-A793-22EABF85AA0E@arm.com> (raw)
In-Reply-To: <20200923082832.20038-1-julien@xen.org>
Hi,
> On 23 Sep 2020, at 09:28, Julien Grall <julien@xen.org> wrote:
>
> From: Julien Grall <jgrall@amazon.com>
>
> SMMUv{1, 2} are both marked as security supported, so we would
> technically have to issue an XSA for any IOMMU security bug.
>
> However, at the moment, device passthrough is not security supported
> on Arm and there is no plan to change that in the next few months.
>
> Therefore, mark Arm SMMUv{1, 2} as supported but not security supported.
>
> Signed-off-by: Julien Grall <jgrall@amazon.com>
Reviewed-by: Bertrand Marquis <bertrand.marquis@arm.com>
We will publish in the next week a first implementation of SMMUv3 support which might make sense to have fully Supported.
Cheers,
Bertrand
>
> ---
>
> Cc: Bertrand Marquis <Bertrand.Marquis@arm.com>
> ---
> SUPPORT.md | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/SUPPORT.md b/SUPPORT.md
> index 25987ec1dfb6..f35943a432f7 100644
> --- a/SUPPORT.md
> +++ b/SUPPORT.md
> @@ -62,8 +62,8 @@ supported in this document.
>
> Status, AMD IOMMU: Supported
> Status, Intel VT-d: Supported
> - Status, ARM SMMUv1: Supported
> - Status, ARM SMMUv2: Supported
> + Status, ARM SMMUv1: Supported, not security supported
> + Status, ARM SMMUv2: Supported, not security supported
> Status, Renesas IPMMU-VMSA: Supported, not security supported
>
> ### ARM/GICv3 ITS
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-09-23 10:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 8:28 [PATCH] SUPPORT.MD: Clarify the support state for the Arm SMMUv{1, 2} drivers Julien Grall
2020-09-23 10:50 ` Bertrand Marquis [this message]
2020-09-23 11:17 ` Julien Grall
2020-09-23 13:55 ` Bertrand Marquis
2020-09-23 14:05 ` Julien Grall
2020-09-23 17:41 ` Stefano Stabellini
2020-09-24 14:02 ` Bertrand Marquis
2020-09-23 17:43 ` Stefano Stabellini
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=1D6392F2-F4EC-4025-A793-22EABF85AA0E@arm.com \
--to=bertrand.marquis@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jbeulich@suse.com \
--cc=jgrall@amazon.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).