> On 09.12.2015 at 9:38pm, wrote:
> >>> On 09.12.15 at 14:30, wrote:
> > Any more comment or suggestion?
> >
> > Now there are 2 comments from you and Kevin Tian.
> > 1. from you, just checking g hardware_domain should be enough.
> > 2. from Kevin Tian, do timeout check within dev_invalidate_
>>> On 09.12.15 at 14:30, wrote:
> Any more comment or suggestion?
>
> Now there are 2 comments from you and Kevin Tian.
> 1. from you, just checking g hardware_domain should be enough.
> 2. from Kevin Tian, do timeout check within dev_invalidate_iotlb for each
> ATS device, to identify bo
>On 04.12.2015 at 2:55pm, wrote:
> >>> "Tian, Kevin" 12/04/15 2:49 AM >>>
> >> From: Jan Beulich [mailto:jbeul...@suse.com]
> >> Sent: Thursday, December 03, 2015 9:16 PM
> >> >>> On 03.12.15 at 09:09, wrote:
> >> > If impacted domain is Dom0 or hardware domain, just throw out a
> warning.
>
On 04.12.2015 at 2:55pm, wrote:
> >>> "Tian, Kevin" 12/04/15 2:49 AM >>>
> >> From: Jan Beulich [mailto:jbeul...@suse.com]
> >> Sent: Thursday, December 03, 2015 9:16 PM
> >> >>> On 03.12.15 at 09:09, wrote:
> >> > If impacted domain is Dom0 or hardware domain, just throw out a
> warning.
>
>>> "Tian, Kevin" 12/04/15 2:49 AM >>>
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Thursday, December 03, 2015 9:16 PM
>> >>> On 03.12.15 at 09:09, wrote:
>> > If impacted domain is Dom0 or hardware domain, just throw out a
>> > warning.
>> > It's an open here whether we want to
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, December 03, 2015 9:16 PM
>
> >>> On 03.12.15 at 09:09, wrote:
> > If impacted domain is Dom0 or hardware domain, just throw out a warning.
> > It's an open here whether we want to kill
> > Dom0 or hardware domain (or direct
On 03.12.2015 at 9:16am, wrote:
> >>> On 03.12.15 at 09:09, wrote:
> > If impacted domain is Dom0 or hardware domain, just throw out a
> warning.
> > It's an open here whether we want to kill
> > Dom0 or hardware domain (or directly panic hypervisor). Comments
> > are welcomed.
>
> I th
>>> On 03.12.15 at 09:09, wrote:
> If impacted domain is Dom0 or hardware domain, just throw out a warning.
> It's an open here whether we want to kill
> Dom0 or hardware domain (or directly panic hypervisor). Comments are
> welcomed.
I think that's a reasonable default, provided by tha