From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?windows-1252?Q?Roger_Pau_Monn=E9?= <roger.pau@citrix.com>
Subject: Re: Second regression due to libxl: Remove linux udev
 rules (2ba368d13893402b2f1fb3c283ddcc714659dd9b)
Date: Tue, 18 Aug 2015 09:49:43 +0200
Message-ID: <55D2E397.3020405@citrix.com>
References: <20150728194741.GA13430@l.oracle.com>
	<55B9E614.4040504@citrix.com> <55C07468.4040909@citrix.com>
	<20150807145440.GK29527@l.oracle.com> <55C4C7B1.8020604@citrix.com>
	<20150812140912.GA17002@l.oracle.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xen.org>
Received: from mail6.bemta14.messagelabs.com ([193.109.254.103])
	by lists.xen.org with esmtp (Exim 4.72)
	(envelope-from <prvs=66538a94f=roger.pau@citrix.com>)
	id 1ZRbeW-0004BM-Ki
	for xen-devel@lists.xenproject.org; Tue, 18 Aug 2015 07:49:48 +0000
In-Reply-To: <20150812140912.GA17002@l.oracle.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: george.dunlap@eu.citrix.com, xen-devel@lists.xenproject.org, wei.liu2@citrix.com, Ian Campbell <ian.campbell@citrix.com>
List-Id: xen-devel@lists.xenproject.org

El 12/08/15 a les 16.09, Konrad Rzeszutek Wilk ha escrit:
> On Fri, Aug 07, 2015 at 04:58:57PM +0200, Roger Pau Monn=E9 wrote:
>> El 07/08/15 a les 16.54, Konrad Rzeszutek Wilk ha escrit:
>>> Ok. I hadn't run your patch yet. Do you want me to run the latest stagi=
ng
>>> instead once more with my test-case?
>>
>> Yes please, 40s in my test case seemed to be fine.
> =

> I get inconsistent values. Sometimes it works, sometimes it does not.
> =

> I will try 120 on my test-bed :-(

Thanks, this is not unexpected. IMHO the best way to solve this would be
to make the hotplug timeout settable by the user by adding a new option
to xl.conf:

hotplug_timeout=3D40

Allowing the user to set it to -1 in order to remove the timeout if desired.

This however seems too intrusive IMHO at this point in the release, so I
would argue for just increasing the default timeout to a suitable value.
Konrad do you have any suggestions?

Roger.