From: Paul Durrant <Paul.Durrant@citrix.com>
To: 'Jan Beulich' <JBeulich@suse.com>, Julien Grall <julien.grall@arm.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Kevin Tian <kevin.tian@intel.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH v8 1/7] iommu: introduce the concept of DFN...
Date: Thu, 13 Sep 2018 13:46:39 +0000 [thread overview]
Message-ID: <768bc5c5bcce4b96a7d72e660e0e7a06@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <5B9A68D602000078001E8443@prv1-mh.provo.novell.com>
> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@suse.com]
> Sent: 13 September 2018 14:41
> To: Paul Durrant <Paul.Durrant@citrix.com>
> Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>; Julien Grall
> <julien.grall@arm.com>; Wei Liu <wei.liu2@citrix.com>; Kevin Tian
> <kevin.tian@intel.com>; Stefano Stabellini <sstabellini@kernel.org>; xen-
> devel <xen-devel@lists.xenproject.org>
> Subject: RE: [PATCH v8 1/7] iommu: introduce the concept of DFN...
>
> >>> On 13.09.18 at 15:09, <Paul.Durrant@citrix.com> wrote:
> > Do you want me to move the page size definitions and re-submit with
> > the other things fixed up?
>
> Irrespective of your subsequent reply, re-submission perhaps wants to
> wait until you've clarified with ARM folks which of the #define-s need
> to move, and which ones may remain common.
>
Ok.
Julien,
Is there a concept of default IOMMU page size for ARM, or is it always implementation specific?
Paul
> Jan
>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-09-13 13:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 10:31 [PATCH v8 0/6] paravirtual IOMMU pre-requisites and clean-up Paul Durrant
2018-09-13 10:31 ` [PATCH v8 1/7] iommu: introduce the concept of DFN Paul Durrant
2018-09-13 12:45 ` Jan Beulich
2018-09-13 13:09 ` Paul Durrant
2018-09-13 13:21 ` Paul Durrant
2018-09-13 13:40 ` Jan Beulich
2018-09-13 13:46 ` Paul Durrant [this message]
2018-09-13 14:14 ` Paul Durrant
2018-09-13 10:31 ` [PATCH v8 2/7] iommu: make use of type-safe DFN and MFN in exported functions Paul Durrant
2018-09-13 10:31 ` [PATCH v8 3/7] iommu: push use of type-safe DFN and MFN into iommu_ops Paul Durrant
2018-09-13 10:31 ` [PATCH v8 4/7] iommu: don't domain_crash() inside iommu_map/unmap_page() Paul Durrant
2018-09-13 10:31 ` [PATCH v8 5/7] memory: add check_get_page_from_gfn() as a wrapper Paul Durrant
2018-09-13 13:22 ` Jan Beulich
2018-09-13 13:43 ` Paul Durrant
2018-09-13 10:31 ` [PATCH v7 6/6] vtd: add lookup_page method to iommu_ops Paul Durrant
2018-09-13 10:31 ` [PATCH v8 6/7] vtd: add missing check for shared EPT Paul Durrant
2018-09-13 10:31 ` [PATCH v8 7/7] vtd: add lookup_page method to iommu_ops Paul Durrant
2018-09-13 13:29 ` Jan Beulich
2018-09-13 13:34 ` Paul Durrant
2018-09-13 13:44 ` Jan Beulich
2018-09-13 13:50 ` Paul Durrant
2018-09-13 13:56 ` Jan Beulich
2018-09-13 14:04 ` Paul Durrant
2018-09-13 14:50 ` Jan Beulich
2018-09-13 14:53 ` Paul Durrant
2018-09-14 7:58 ` Jan Beulich
2018-09-14 8:11 ` Paul Durrant
2018-09-14 8:28 ` Jan Beulich
2018-09-14 8:48 ` Paul Durrant
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=768bc5c5bcce4b96a7d72e660e0e7a06@AMSPEX02CL03.citrite.net \
--to=paul.durrant@citrix.com \
--cc=JBeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=kevin.tian@intel.com \
--cc=sstabellini@kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=wei.liu2@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 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).