On May 19, 2016 7:36 PM, Jan Beulich wrote:
> >>> On 19.05.16 at 13:26, wrote:
> > On May 19, 2016 2:13 PM, Jan Beulich wrote:
> >> >>> "Xu, Quan" 05/19/16 3:35 AM >>>
> >> >On May 19, 2016 8:33 AM, Tian, Kevin wrote:
> >> >> A single default value for both IOMMU-side and device-side is
> >> >
>>> On 19.05.16 at 13:26, wrote:
> On May 19, 2016 2:13 PM, Jan Beulich wrote:
>> >>> "Xu, Quan" 05/19/16 3:35 AM >>>
>> >On May 19, 2016 8:33 AM, Tian, Kevin wrote:
>> >> A single default value for both IOMMU-side and device-side is anyway
>> >> not optimal. What about introducing a new knob e
On May 19, 2016 2:13 PM, Jan Beulich wrote:
> >>> "Xu, Quan" 05/19/16 3:35 AM >>>
> >On May 19, 2016 8:33 AM, Tian, Kevin wrote:
> >> A single default value for both IOMMU-side and device-side is anyway
> >> not optimal. What about introducing a new knob e.g.
> >> vtd_qi_device_timeout specifica
>>> "Xu, Quan" 05/19/16 3:35 AM >>>
>On May 19, 2016 8:33 AM, Tian, Kevin wrote:
>> > From: Jan Beulich [mailto:jbeul...@suse.com]
>> > Sent: Wednesday, May 18, 2016 11:05 PM
>> > >>> On 18.05.16 at 14:53, wrote:
>> > The patch can imo remain as is only if the new default timeout is
>> > large e
On May 19, 2016 8:33 AM, Tian, Kevin wrote:
> > From: Jan Beulich [mailto:jbeul...@suse.com]
> > Sent: Wednesday, May 18, 2016 11:05 PM
> >
> > >>> On 18.05.16 at 14:53, wrote:
> > > On May 17, 2016 3:48 PM, Jan Beulich wrote:
> > >> >>> On 17.05.16 at 05:19, wrote:
> > >> >> From: Xu, Quan
>
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, May 18, 2016 11:05 PM
>
> >>> On 18.05.16 at 14:53, wrote:
> > On May 17, 2016 3:48 PM, Jan Beulich wrote:
> >> >>> On 17.05.16 at 05:19, wrote:
> >> >> From: Xu, Quan
> >> >> Sent: Monday, May 16, 2016 11:26 PM
> >> >>
> >> >>
>>> On 18.05.16 at 14:53, wrote:
> On May 17, 2016 3:48 PM, Jan Beulich wrote:
>> >>> On 17.05.16 at 05:19, wrote:
>> >> From: Xu, Quan
>> >> Sent: Monday, May 16, 2016 11:26 PM
>> >>
>> >> On May 13, 2016 11:28 PM, Jan Beulich wrote:
>> >> > >>> On 22.04.16 at 12:54, wrote:
>> >> > > --- a/d
On May 17, 2016 3:48 PM, Jan Beulich wrote:
> >>> On 17.05.16 at 05:19, wrote:
> >> From: Xu, Quan
> >> Sent: Monday, May 16, 2016 11:26 PM
> >>
> >> On May 13, 2016 11:28 PM, Jan Beulich wrote:
> >> > >>> On 22.04.16 at 12:54, wrote:
> >> > > --- a/docs/misc/xen-command-line.markdown
> >> > >
>>> On 17.05.16 at 05:19, wrote:
>> From: Xu, Quan
>> Sent: Monday, May 16, 2016 11:26 PM
>>
>> On May 13, 2016 11:28 PM, Jan Beulich wrote:
>> > >>> On 22.04.16 at 12:54, wrote:
>> > > --- a/docs/misc/xen-command-line.markdown
>> > > +++ b/docs/misc/xen-command-line.markdown
>> > > @@ -1532,6
> From: Xu, Quan
> Sent: Monday, May 16, 2016 11:26 PM
>
> On May 13, 2016 11:28 PM, Jan Beulich wrote:
> > >>> On 22.04.16 at 12:54, wrote:
> > > --- a/docs/misc/xen-command-line.markdown
> > > +++ b/docs/misc/xen-command-line.markdown
> > > @@ -1532,6 +1532,16 @@ Note that if **watchdog** opti
On May 13, 2016 11:28 PM, Jan Beulich wrote:
> >>> On 22.04.16 at 12:54, wrote:
> > --- a/docs/misc/xen-command-line.markdown
> > +++ b/docs/misc/xen-command-line.markdown
> > @@ -1532,6 +1532,16 @@ Note that if **watchdog** option is also
> specified vpmu will be turned off.
> > As the virtuali
>>> On 22.04.16 at 12:54, wrote:
> --- a/docs/misc/xen-command-line.markdown
> +++ b/docs/misc/xen-command-line.markdown
> @@ -1532,6 +1532,16 @@ Note that if **watchdog** option is also specified
> vpmu will be turned off.
> As the virtualisation is not 100% safe, don't use the vpmu flag on
>
12 matches
Mail list logo