From: "Jan Beulich" Subject: Re: [PATCH v1 0/2] Extend ioreq-server to support page write protection Date: Fri, 15 Aug 2014 00:12:12 +0100 Message-ID: <53ED505C02000078000BA819@mail.emea.novell.com> References: <53E33C90020000780002A00D@mail.emea.novell.com> <53E48B26020000780002A4E9@mail.emea.novell.com> <76A3A946BA26DE4F9D9D5090FFA4A64932DA6F@SHSMSX101.ccr.corp.intel.com> <20140813083833.GB28131@deinos.phlegethon.org> <20140814080806.GA13892@deinos.phlegethon.org> <20140814202522.GA58875@deinos.phlegethon.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Kevin Tian Cc: "keir@xen.org" , "ian.campbell@citrix.com" , "stefano.stabellini@eu.citrix.com" , Tim Deegan , "ian.jackson@eu.citrix.com" , Donald D Dugger , "xen-devel@lists.xen.org" , "Paul.Durrant@citrix.com" , Zhiyuan Lv , Yang Z Zhang , Wei Ye List-Id: xen-devel@lists.xenproject.org >>> On 15.08.14 at 00:53, wrote: > btw just curious how we handle p2m_ram_ro today. Does it play any trick > to fail-safe in IOMMU side, e.g. zap the mapping or not? Otherwise when > it allows read-only DMA there's no way to prevent DMA writes either. :-) Why would that be? A page marked r/o in the IOMMU page tables ought to very well be protected against DMA writes. It's just that these will cause faults, which - if happening too frequently - will result in the device getting turned off, quite likely (implicitly) killing the guest. Jan