[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] ATS and dependent features


  • To: Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>
  • From: "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
  • Date: Thu, 29 Nov 2012 01:07:16 +0000
  • Accept-language: en-US
  • Cc: "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
  • Delivery-date: Thu, 29 Nov 2012 01:08:51 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: AQHNzINiSOuk8WhZTUOv61PMlYmAhZgAAhig
  • Thread-topic: ATS and dependent features

ATS should be a host feature controlled by iommu, and I don't think dom0 can 
control  it from Xen's architecture.   Perhaps we need to forbid dom0 
controlling these features. 
Xiantao

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
> Sent: Tuesday, November 27, 2012 5:42 PM
> To: Zhang, Xiantao; xen-devel
> Subject: ATS and dependent features
> 
> All,
> 
> while investigating an issue with some device not working under Xen without
> "ats=off", I started wondering whether it is correct to allow the Dom0 kernel
> concurrent control over ATS, PRI, and PASID - it would seem to me that with
> Xen controlling the IOMMU, it should also have exclusive control over the
> enabling of those features.
> 
> Thanks for any comments in this regard,
> Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.