From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dario Faggioli Subject: Re: [PATCH] libxl: Increase device model startup timeout to 1min. Date: Tue, 30 Jun 2015 05:08:22 +0200 Message-ID: <1435633702.25170.279.camel@citrix.com> References: <1435319840-25020-1-git-send-email-anthony.perard@citrix.com> <1435336867.32500.209.camel@citrix.com> <20150629142317.GB1891@perard.uk.xensource.com> <1435589517.32500.342.camel@citrix.com> <20150629160919.GC1891@perard.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4841418016032006728==" Return-path: In-Reply-To: <20150629160919.GC1891@perard.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Anthony PERARD Cc: Ian Jackson , xen-devel@lists.xen.org, Wei Liu , Ian Campbell , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org --===============4841418016032006728== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-lD851JvSaSaVY5B7xO/o" --=-lD851JvSaSaVY5B7xO/o Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 2015-06-29 at 17:09 +0100, Anthony PERARD wrote: > On Mon, Jun 29, 2015 at 03:51:57PM +0100, Ian Campbell wrote: > > On Mon, 2015-06-29 at 15:23 +0100, Anthony PERARD wrote: > > > OK. What about: > >=20 > > I'm afraid none of that really explains why QEMU taking >10s is > > reasonable/expected under the circumstances or why 60s is a good choice > > now. > >=20 > > Nor does it really answer Ian's question in > > <21901.33163.547929.321814@mariner.uk.xensource.com> I think. >=20 > I only know what happen, not why it happen. >=20 > How could I investigate why qemu is taking so long after an mmap() syscal= l? > I guest at that time, it is copying the library into memory. >=20 Is there a lot of CPU / memory contention in Dom0 (assuming that QEMU runs in dom0 in this case)? If yes, is it plausible for that to be the cause? If yes, can we show, or monitor, or trace it somehow? That would be a first step toward trying to figure out what specific characteristic of the contended scenario causes the issue... Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-lD851JvSaSaVY5B7xO/o Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAlWSCCYACgkQk4XaBE3IOsQFKwCfb8TcT9Z3ne3mGdOe0sSdzKQh udsAnAl0xUMYkVqUY7EraJKqJmEFM/Cp =KFNh -----END PGP SIGNATURE----- --=-lD851JvSaSaVY5B7xO/o-- --===============4841418016032006728== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============4841418016032006728==--