From: George Dunlap <george.dunlap@citrix.com>
To: "Xu, Quan" <quan.xu@intel.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"Wu, Feng" <feng.wu@intel.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Liu Jinsong <jinsong.liu@alibaba-inc.com>,
Dario Faggioli <dario.faggioli@citrix.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Keir Fraser <keir@xen.org>
Subject: Re: abstract model of IOMMU unmaping/mapping failures
Date: Fri, 15 Apr 2016 15:02:46 +0100 [thread overview]
Message-ID: <5710F486.5080208@citrix.com> (raw)
In-Reply-To: <945CA011AD5F084CBEA3E851C0AB28894B873451@SHSMSX101.ccr.corp.intel.com>
On 31/03/16 10:06, Xu, Quan wrote:
> All,
>
> Here is a summary of my investigation of the abstract model:
>
> Below policies are adopted when deciding whether to rollback a callchain:
>
> 1. Domain will be crashed immediately within iommu_{,un}map_page, treated as a fatal error (with the exception of the hardware one). Whether to rollback depends on the need of hardware domain;
>
> 2. For hardware domain, roll back on a best effort basis. When rollback is not feasible (in early initialization phase or trade-off of complexity), at least unmap upon maps error and then throw out error message;
>
> Below are a detail analysis of all existing callers on IOMMU interfaces (8-11 needs more discussions):
Hey Quan,
I only reviewed the p2m-related ones (5-10), but I agree with your and
Jan's conclusions. Thanks for doing this legwork.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-15 14:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 9:06 abstract model of IOMMU unmaping/mapping failures Xu, Quan
2016-03-31 9:12 ` Xu, Quan
2016-04-01 0:25 ` Tian, Kevin
2016-04-01 11:57 ` Jan Beulich
2016-04-06 7:38 ` Xu, Quan
2016-04-07 22:44 ` Jan Beulich
2016-04-08 8:54 ` Xu, Quan
2016-04-12 3:30 ` Xu, Quan
2016-04-15 13:32 ` George Dunlap
2016-04-15 14:02 ` George Dunlap [this message]
2016-04-18 1:20 ` Xu, Quan
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=5710F486.5080208@citrix.com \
--to=george.dunlap@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=feng.wu@intel.com \
--cc=george.dunlap@eu.citrix.com \
--cc=jinsong.liu@alibaba-inc.com \
--cc=jun.nakajima@intel.com \
--cc=keir@xen.org \
--cc=kevin.tian@intel.com \
--cc=quan.xu@intel.com \
--cc=xen-devel@lists.xen.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.