From: Malcolm Crossley <malcolm.crossley@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Yu C Zhang <yu.c.zhang@intel.com>,
AndrewCooper <andrew.cooper3@citrix.com>,
Paul Durrant <Paul.Durrant@citrix.com>,
David Vrabel <david.vrabel@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Zhiyuan Lv <zhiyuan.lv@intel.com>
Subject: Re: Xen PV IOMMU interface draft D
Date: Tue, 23 Feb 2016 16:22:36 +0000 [thread overview]
Message-ID: <56CC874C.9050009@citrix.com> (raw)
In-Reply-To: <56CC944602000078000D54D2@prv-mh.provo.novell.com>
On 23/02/16 16:17, Jan Beulich wrote:
>>>> On 10.02.16 at 11:09, <malcolm.crossley@citrix.com> wrote:
>> % Xen PV IOMMU interface
>> % Malcolm Crossley <<malcolm.crossley@citrix.com>>
>> Paul Durrant <<paul.durrant@citrix.com>>
>> % Draft D
>>
>> Introduction
>> ============
>>
>> Revision History
>> ----------------
>>
>> --------------------------------------------------------------------
>> Version Date Changes
>> ------- ----------- ----------------------------------------------
>> Draft A 10 Apr 2014 Initial draft.
>>
>> Draft B 12 Jun 2015 Second draft.
>>
>> Draft C 26 Jun 2015 Third draft.
>>
>> Draft D 09 Feb 2016 Fourth draft.
>
> Unless this is a complete re-write, I'd really like to avoid needing to
> read through all of it again. Do you perhaps have a PDF version
> somewhere with change marks?
>
It was really a minor update to ensure the design matched the RFC implementation.
The diff for the draft D is below. For the next revision I will details what has changed.
diff -r a35c08555541 -r e829e3d0fcec designs/pv-iommu-control/design.txt
--- a/designs/pv-iommu-control/design.txt
+++ b/designs/pv-iommu-control/design.txt
@@ -1,7 +1,7 @@
% Xen PV IOMMU interface
% Malcolm Crossley <<malcolm.crossley@citrix.com>>
Paul Durrant <<paul.durrant@citrix.com>>
-% Draft C
+% Draft D
Introduction
============
@@ -17,6 +17,8 @@ Draft A 10 Apr 2014 Initial draft.
Draft B 12 Jun 2015 Second draft.
Draft C 26 Jun 2015 Third draft.
+
+Draft D 09 Feb 2016 Fourth draft.
--------------------------------------------------------------------
Background
@@ -481,7 +483,9 @@ IOMMU_OP_readable 0 Cr
IOMMU_OP_writeable 1 Create writeable IOMMU mapping
IOMMU_MAP_OP_no_ref_cnt 2 IOMMU mapping does not take a reference to
MFN backing BFN mapping
-Reserved for future use 3-9 n/a
+IOMMU_MAP_OP_add_m2b 3 Wildcard M2B mapping added for
+ lookup_foreign_page to use
+Reserved for future use 4-9 n/a
IOMMU_page_order 10-15 Page order to be used for both gfn and bfn
Defined values for map_page subop status field:
@@ -519,7 +523,9 @@ Defined bits for flags field:
Name Bit Definition
---- ----- ----------------------------------
-Reserved for future use 0-9 n/a
+IOMMU_UNMAP_OP_remove_m2b 0 Wildcard M2B mapping removed for
+ lookup_foreign_page use
+Reserved for future use 1-9 n/a
IOMMU_page_order 10-15 Page order to be used for bfn
Sorry about the hassle. I posted the RFC because I was would like to get some comments on the M2B
implementation and the iommu_lookup_page code.
Malcolm
> Jan
>
next prev parent reply other threads:[~2016-02-23 16:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 16:43 [RFC] Xen PV IOMMU interface draft B Malcolm Crossley
2015-06-16 13:19 ` Jan Beulich
2015-06-16 14:47 ` Malcolm Crossley
2015-06-16 15:56 ` Jan Beulich
2015-06-17 12:48 ` Yu, Zhang
2015-06-17 13:34 ` Jan Beulich
2015-06-17 13:44 ` Malcolm Crossley
2015-06-26 10:23 ` Xen PV IOMMU interface draft C Malcolm Crossley
2015-06-26 11:03 ` Ian Campbell
2015-06-29 14:40 ` Konrad Rzeszutek Wilk
2015-06-29 14:52 ` Ian Campbell
2015-06-29 15:05 ` Malcolm Crossley
2015-06-29 15:24 ` David Vrabel
2015-06-29 15:36 ` Ian Campbell
2015-07-10 19:32 ` Konrad Rzeszutek Wilk
2016-02-10 10:09 ` Xen PV IOMMU interface draft D Malcolm Crossley
2016-02-18 8:21 ` Tian, Kevin
2016-02-23 16:17 ` Jan Beulich
2016-02-23 16:22 ` Malcolm Crossley [this message]
2016-03-02 6:54 ` Tian, Kevin
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=56CC874C.9050009@citrix.com \
--to=malcolm.crossley@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=Paul.Durrant@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=kevin.tian@intel.com \
--cc=xen-devel@lists.xenproject.org \
--cc=yu.c.zhang@intel.com \
--cc=zhiyuan.lv@intel.com \
/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.