From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v3 6/6] qemu_calculate_timeout: increase minimum timeout to 1h Date: Fri, 10 Feb 2012 12:18:11 +0100 Message-ID: <4F34FCF3.4080300@redhat.com> References: <201202100952.26104.paul@codesourcery.com> <4F34F567.3040309@redhat.com> <201202101109.03374.paul@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Stefano Stabellini Cc: "avi@redhat.com" , "xen-devel@lists.xensource.com" , Paul Brook , "qemu-devel@nongnu.org" List-Id: xen-devel@lists.xenproject.org On 02/10/2012 12:19 PM, Stefano Stabellini wrote: > I think you are right and the right thing to do would be blocking > indefinitely. > However if slirp doesn't support it, we could have a timeout of 1000 if > CONFIG_SLIRP, otherwise block indefinitely. You could add a similar hack to qemu_bh_update_timeout for slirp_update_timeout. Paolo