Re: [Xen-devel] [Patch RFC 11/13] vt-d: If the Device-TLB flush is still not completed when

["Xu, Quan" <quan.xu@xxxxxxxxx>]

Hi, Kornrad

> -----Original Message-----
> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@xxxxxxxxxx]
> Sent: Thursday, September 24, 2015 1:39 AM
> To: Xu, Quan
> Cc: andrew.cooper3@xxxxxxxxxx; Dong, Eddie; ian.campbell@xxxxxxxxxx;
> ian.jackson@xxxxxxxxxxxxx; jbeulich@xxxxxxxx; Nakajima, Jun; keir@xxxxxxx;
> Tian, Kevin; tim@xxxxxxx; Zhang, Yang Z; george.dunlap@xxxxxxxxxxxxx;
> xen-devel@xxxxxxxxxxxxx
> Subject: Re: [Xen-devel] [Patch RFC 11/13] vt-d: If the Device-TLB flush is 
> still not
> completed when
> 
> > index 5dc0033..f661c8c 100644
> > --- a/xen/include/xen/hvm/iommu.h
> > +++ b/xen/include/xen/hvm/iommu.h
> > @@ -20,6 +20,7 @@
> >  #define __XEN_HVM_IOMMU_H__
> >
> >  #include <xen/iommu.h>
> > +#include <xen/wait.h>
> >  #include <xen/list.h>
> >  #include <asm/hvm/iommu.h>
> >
> > @@ -56,12 +57,15 @@ struct hvm_iommu {
> >      struct page_list_head qi_hold_page_list;
> >      spinlock_t qi_lock;
> >
> > +    struct waitqueue_head qi_wq;
> > +
> 
> 
> Is there anything that mandates this must be an HVM guest? As in - can't you
> have ATS with an PV guest (and doing passthrough?)

Yes, this patch set if just for HVM guest. It is complicated to support both PV 
guest and HVM guest.



Quan




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