From: Julien Grall <julien.grall@arm.com>
To: Andrii Anisov <andrii.anisov@gmail.com>, xen-devel@lists.xenproject.org
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Andrii Anisov <andrii_anisov@epam.com>
Subject: Re: [PATCH 0/2] Dangling fixes for ARM iommu
Date: Wed, 23 Jan 2019 18:34:06 +0000 [thread overview]
Message-ID: <b30883e0-ec2d-ba19-e65f-baafa6736f51@arm.com> (raw)
In-Reply-To: <e919a1c0-2fef-29e9-658c-59660aaf63b9@gmail.com>
On 23/01/2019 18:29, Andrii Anisov wrote:
>
> On 23.01.19 20:14, Julien Grall wrote:
>> I can queue the first hunk for Xen 4.13.
> For 4.13? Well I hope we will manage to upstream the whole series until then.
If you plan to resend it separately, I can apply to the next branch regardless
the rest of the series.
>> It does not make sense to remove the properties "iommus", "iommu-map",
>> "iommu-map-mask" if Dom0 is already touching the IOMMU. It is either
>> everything or nothing.
> So that patch should be totally rewritten. At least to support iommu=disabled.
And the case where IOMMU is enabled but no IOMMU driver is present in Xen.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2019-01-23 18:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 17:04 [PATCH 0/2] Dangling fixes for ARM iommu Andrii Anisov
2019-01-21 17:04 ` [PATCH 1/2] iommu/arm: Misc fixes for arch specific part Andrii Anisov
2019-01-21 17:04 ` [PATCH 2/2] xen/arm: domain_build: Don't expose IOMMU specific properties to the guest Andrii Anisov
2019-10-01 15:04 ` [Xen-devel] " Julien Grall
2019-10-01 15:25 ` Oleksandr
2019-10-01 15:36 ` Julien Grall
2019-10-01 16:07 ` Oleksandr
2019-10-01 19:07 ` Julien Grall
2019-10-03 12:18 ` Oleksandr
2019-10-07 21:02 ` Julien Grall
2019-10-08 15:34 ` Oleksandr
2019-01-21 17:29 ` [PATCH 0/2] Dangling fixes for ARM iommu Julien Grall
2019-01-22 13:48 ` Andrii Anisov
2019-01-22 14:31 ` Julien Grall
2019-01-23 17:53 ` Andrii Anisov
2019-01-23 18:14 ` Julien Grall
2019-01-23 18:29 ` Andrii Anisov
2019-01-23 18:34 ` Julien Grall [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=b30883e0-ec2d-ba19-e65f-baafa6736f51@arm.com \
--to=julien.grall@arm.com \
--cc=andrii.anisov@gmail.com \
--cc=andrii_anisov@epam.com \
--cc=jgross@suse.com \
--cc=sstabellini@kernel.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).