On June 23, 2016 12:18 AM, Jan Beulich wrote:
> >>> On 22.06.16 at 17:54, wrote:
> > On June 17, 2016 3:01 PM, Jan Beulich wrote:
> >> And again I don't understand: ASSERT()s are to verify assumed state.
> >> If
> > static
> >> code analysis resulted in understanding a function is unreachable
>
>>> On 22.06.16 at 17:54, wrote:
> On June 17, 2016 3:01 PM, Jan Beulich wrote:
>> And again I don't understand: ASSERT()s are to verify assumed state. If
> static
>> code analysis resulted in understanding a function is unreachable when
>> qi_ctrl->qinval_maddr is zero (because qinval ought to
On June 17, 2016 3:01 PM, Jan Beulich wrote:
> And again I don't understand: ASSERT()s are to verify assumed state. If static
> code analysis resulted in understanding a function is unreachable when
> qi_ctrl->qinval_maddr is zero (because qinval ought to have got disabled if
> any
> of the table
On June 18, 2016 5:54 PM, Xu, Quan wrote:
> On June 17, 2016 9:35 PM, Julien Grall wrote:
> > On 17/06/16 09:51, Xu, Quan wrote:
> > > + arm/amd maintainers..
> > >
> > > On June 01, 2016 5:05 PM, Xu, Quan wrote:
> > >> If Device-TLB flush timed out, we hide the target ATS device
> > >> immediat
On June 17, 2016 9:35 PM, Julien Grall wrote:
> On 17/06/16 09:51, Xu, Quan wrote:
> > + arm/amd maintainers..
> >
> > On June 01, 2016 5:05 PM, Xu, Quan wrote:
> >> If Device-TLB flush timed out, we hide the target ATS device
> >> immediately and crash the domain owning this ATS device. If impac
Hi Quan,
On 17/06/16 09:51, Xu, Quan wrote:
+ arm/amd maintainers..
On June 01, 2016 5:05 PM, Xu, Quan wrote:
If Device-TLB flush timed out, we hide the target ATS device immediately and
crash the domain owning this ATS device. If impacted domain is hardware
domain, just throw out a warning.
+ arm/amd maintainers..
On June 01, 2016 5:05 PM, Xu, Quan wrote:
> If Device-TLB flush timed out, we hide the target ATS device immediately and
> crash the domain owning this ATS device. If impacted domain is hardware
> domain, just throw out a warning.
>
> By hiding the device, we make sure it
>>> On 17.06.16 at 10:15, wrote:
> On June 17, 2016 3:01 PM, Jan Beulich wrote:
>> >>> On 17.06.16 at 08:08, wrote:
>>
>> > On June 16, 2016 5:05 PM, Jan Beulich wrote:
>> >> >>> On 16.06.16 at 10:42, wrote:
>> >> > On June 02, 2016 7:07 PM, Jan Beulich wrote:
>> >> >> >>> On 01.06.16 at 11:
On June 17, 2016 3:01 PM, Jan Beulich wrote:
> >>> On 17.06.16 at 08:08, wrote:
>
> > On June 16, 2016 5:05 PM, Jan Beulich wrote:
> >> >>> On 16.06.16 at 10:42, wrote:
> >> > On June 02, 2016 7:07 PM, Jan Beulich wrote:
> >> >> >>> On 01.06.16 at 11:05, wrote:
> >> >> > +static void dev_inv
>>> On 17.06.16 at 08:08, wrote:
> On June 16, 2016 5:05 PM, Jan Beulich wrote:
>> >>> On 16.06.16 at 10:42, wrote:
>> > On June 02, 2016 7:07 PM, Jan Beulich wrote:
>> >> >>> On 01.06.16 at 11:05, wrote:
>> >> > +static void dev_invalidate_iotlb_timeout(struct iommu *iommu, u16 did,
>> >> >
On June 16, 2016 5:05 PM, Jan Beulich wrote:
> >>> On 16.06.16 at 10:42, wrote:
> > On June 02, 2016 7:07 PM, Jan Beulich wrote:
> >> >>> On 01.06.16 at 11:05, wrote:
> >> > +static void dev_invalidate_iotlb_timeout(struct iommu *iommu, u16 did,
> >> > +
>>> On 16.06.16 at 10:42, wrote:
> On June 02, 2016 7:07 PM, Jan Beulich wrote:
>> >>> On 01.06.16 at 11:05, wrote:
>> > --- a/xen/drivers/passthrough/vtd/extern.h
>> > +++ b/xen/drivers/passthrough/vtd/extern.h
>> > @@ -21,6 +21,7 @@
>> > #define _VTD_EXTERN_H_
>> >
>> > #include "dmar.h"
>>
(* I will CC arm/amd maintainer after this vt-d specific discussion, and then
send out my proposal...)
On June 02, 2016 7:07 PM, Jan Beulich wrote:
> >>> On 01.06.16 at 11:05, wrote:
> > --- a/xen/drivers/passthrough/vtd/extern.h
> > +++ b/xen/drivers/passthrough/vtd/extern.h
> > @@ -21,6 +21,7
>>> On 01.06.16 at 11:05, wrote:
> --- a/xen/drivers/passthrough/vtd/extern.h
> +++ b/xen/drivers/passthrough/vtd/extern.h
> @@ -21,6 +21,7 @@
> #define _VTD_EXTERN_H_
>
> #include "dmar.h"
> +#include "../ats.h"
Why? You don't de-reference struct pci_ats_dev * in this file, so
all you'd need
From: Quan Xu
If Device-TLB flush timed out, we hide the target ATS device
immediately and crash the domain owning this ATS device. If
impacted domain is hardware domain, just throw out a warning.
By hiding the device, we make sure it can't be assigned to any
domain any longer (see device_assign
15 matches
Mail list logo