From: Dario Faggioli <dfaggioli@suse.com>
To: Milan Boberic <milanboberic94@gmail.com>
Cc: xen-devel@lists.xenproject.org, stefano@stabellini.net
Subject: Re: null scheduler bug
Date: Thu, 13 Sep 2018 19:39:02 +0200 [thread overview]
Message-ID: <529d38d04b140d90d33e424a064d401cf06f14cf.camel@suse.com> (raw)
In-Reply-To: <CADJ6SV2wis2kOz9j4OGTzRLd+2O2f_SuxktFWRq2A_tbng_3Ug@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1887 bytes --]
On Thu, 2018-09-13 at 17:18 +0200, Milan Boberic wrote:
> Commits are there and I will definitely continue with 4.10 version.
> But it didn't solve my problem entirely.
>
> I create my bare-metal application (with xl create) and destroy it
> with xl destroy (it disappears from xl list) and when I try to create
> it again same error pops but if I immediately run xl create command
> again it creates it without error.
> If I run xl create twice fast sometimes bare-metal application isn't
> in any state (it should be in "running" state).
> If I wait some time (approximately between 30 and 90 seconds) after
> destruction of that bm app and then run xl create it will create it
> without error.
>
Ok, thanks for trying and reporting back.
If possible, help me understand things a bit better.
So, can you confirm that the situation _actually_improves_ with Xen
4.10 ?
Basically, as far as I've understood things, with Xen 4.9, you destroy
a guest, and you can _never_ re-create it, not even after 30 seconds,
90 seconds, 2 minutes, 1 hour, ecc. Is that correct?
With Xen 4.10, it may still fail, if you try to re-create it within ~30
to 90 seconds, but after that, it works. Is that also correct?
I need to know this, because I want to understand if the issue is, at
least partially, cured by the RCU fixes, although having to wait 30
seconds is definitely not what I was expecting (i.e., there might be
something else).
Another question, in case I manage to produce a debug patch, are you ok
to put it in your source tree, build with it, and tell us what you see?
Thanks again and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Software Engineer @ SUSE https://www.suse.com/
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-09-13 17:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 23:03 null scheduler bug Stefano Stabellini
2018-09-13 7:04 ` Dario Faggioli
[not found] ` <CADJ6SV2G=51BK2p-bouNGfiS5sP2tiV6ztZZ7PFGjiptRw_P3w@mail.gmail.com>
2018-09-13 8:24 ` Dario Faggioli
2018-09-13 15:18 ` Milan Boberic
2018-09-13 17:39 ` Dario Faggioli [this message]
2018-09-14 9:21 ` Milan Boberic
2018-09-20 13:04 ` Milan Boberic
2018-09-20 16:09 ` Dario Faggioli
2018-09-21 14:14 ` Milan Boberic
2018-09-21 16:20 ` Dario Faggioli
2018-09-24 21:46 ` Julien Grall
2018-09-25 9:02 ` Dario Faggioli
2018-09-25 10:12 ` Milan Boberic
2018-09-25 10:56 ` Julien Grall
2018-09-25 11:15 ` Julien Grall
2018-09-25 11:51 ` Milan Boberic
2018-09-25 17:49 ` Dario Faggioli
2018-09-27 9:50 ` Dario Faggioli
2018-09-27 13:15 ` Milan Boberic
2018-09-27 14:23 ` Dario Faggioli
2018-09-27 14:32 ` Dario Faggioli
2018-09-27 15:09 ` Julien Grall
2018-09-27 17:06 ` Dario Faggioli
2018-09-28 8:18 ` Milan Boberic
2018-10-01 12:03 ` Julien Grall
-- strict thread matches above, loose matches on Subject: below --
2018-09-13 8:15 Milan Boberic
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=529d38d04b140d90d33e424a064d401cf06f14cf.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=milanboberic94@gmail.com \
--cc=stefano@stabellini.net \
--cc=xen-devel@lists.xenproject.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).