From: Dario Faggioli <dario.faggioli@citrix.com>
To: Julien Grall <julien.grall@arm.com>,
osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Cc: Stefano Stabellini <stefano@stabellini.net>,
Meng Xu <xumengpanda@gmail.com>
Subject: Re: Guest start issue on ARM (maybe related to Credit2) [Was: Re: [xen-unstable test] 113807: regressions - FAIL]
Date: Thu, 28 Sep 2017 11:38:55 +0200 [thread overview]
Message-ID: <1506591535.5001.2.camel@citrix.com> (raw)
In-Reply-To: <4143b0c0-18c7-4758-d3a5-1be4b0669dbb@arm.com>
[-- Attachment #1.1: Type: text/plain, Size: 1631 bytes --]
On Thu, 2017-09-28 at 00:52 +0100, Julien Grall wrote:
> On 09/28/2017 12:51 AM, Julien Grall wrote:
> > > Things *should really not* explode (like as in Xen crashes) if
> > > that
> > > happens; actually, from a scheduler perspective, it should really
> > > not
> > > be too big of a deal (especially if the overload is transient,
> > > like I
> > > guess it should be in this case). However, it's entirely possible
> > > that
> > > some specific vCPUs failing to be scheduler for a certain amount
> > > of
> > > time, causes something _inside_ the guest to timeout, or get
> > > stuck or
> > > wedged, which may be what happens here.
> >
> > Looking at the log I don't see any crash of Xen and it seems to
> > be responsive.
>
> I forgot to add that I don't see any timeout on the guest console
> but can notice slow down (waiting for some PV device).
>
Exactly! And in fact, I'm saying that, even if nothing breaks, maybe
there are intervals during which --due to the combination of the
overload, the non work-conserving nature and the fact that these CPUs
are slow-- Dom0 is slow in dealing with the backends, to the point that
OSSTest times out.
Then, after the "load spike", everything goes back to normal, the
system is responsive, the logs (like the runqueue dump you posted)
depicts a normal semi-idle system.
Regards,
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: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-09-28 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 9:46 [xen-unstable test] 113807: regressions - FAIL osstest service owner
2017-09-25 14:07 ` Guest start issue on ARM (maybe related to Credit2) [Was: Re: [xen-unstable test] 113807: regressions - FAIL] Dario Faggioli
2017-09-25 16:23 ` Julien Grall
2017-09-25 17:29 ` Dario Faggioli
2017-09-26 7:33 ` Dario Faggioli
2017-09-26 17:28 ` Julien Grall
2017-09-26 20:51 ` Dario Faggioli
2017-09-27 23:51 ` Julien Grall
2017-09-27 23:52 ` Julien Grall
2017-09-28 9:38 ` Dario Faggioli [this message]
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=1506591535.5001.2.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=julien.grall@arm.com \
--cc=osstest-admin@xenproject.org \
--cc=stefano@stabellini.net \
--cc=xen-devel@lists.xensource.com \
--cc=xumengpanda@gmail.com \
/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).