From: Dario Faggioli <dario.faggioli@citrix.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] libxl: Increase device model startup timeout to 1min.
Date: Tue, 30 Jun 2015 05:08:22 +0200 [thread overview]
Message-ID: <1435633702.25170.279.camel@citrix.com> (raw)
In-Reply-To: <20150629160919.GC1891@perard.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1309 bytes --]
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:
> >
> > 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.
> >
> > Nor does it really answer Ian's question in
> > <21901.33163.547929.321814@mariner.uk.xensource.com> I think.
>
> I only know what happen, not why it happen.
>
> How could I investigate why qemu is taking so long after an mmap() syscall?
> I guest at that time, it is copying the library into memory.
>
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
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-06-30 3:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 11:57 [PATCH] libxl: Increase device model startup timeout to 1min Anthony PERARD
2015-06-26 16:41 ` Ian Campbell
2015-06-29 14:23 ` Anthony PERARD
2015-06-29 14:51 ` Ian Campbell
2015-06-29 16:09 ` Anthony PERARD
2015-06-30 3:08 ` Dario Faggioli [this message]
2015-06-30 14:04 ` Ian Jackson
2015-06-30 15:58 ` Stefano Stabellini
2015-06-30 16:40 ` Ian Jackson
2015-07-01 15:03 ` Stefano Stabellini
2015-07-02 11:11 ` Anthony PERARD
2015-07-02 12:38 ` Ian Jackson
2015-07-03 11:21 ` Anthony PERARD
2015-07-03 11:30 ` Ian Jackson
2015-07-07 13:44 ` Ian Campbell
2015-07-07 13:47 ` Ian Jackson
2015-07-07 14:37 ` [PATCH V2] " Anthony PERARD
2015-07-07 14:41 ` Ian Jackson
2015-07-07 15:09 ` [PATCH V3] " Anthony PERARD
2015-07-07 15:14 ` Ian Jackson
2015-07-07 15:41 ` Ian Campbell
2015-07-14 6:17 ` Jan Beulich
2015-07-14 7:55 ` Ian Campbell
2015-07-14 9:25 ` Dario Faggioli
2015-07-14 9:37 ` Ian Campbell
2015-07-14 10:52 ` Dario Faggioli
2015-07-14 14:23 ` Dario Faggioli
2015-07-14 14:48 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1435633702.25170.279.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).