xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dfaggioli@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xenproject.org, milanboberic94@gmail.com
Subject: Re: null scheduler bug
Date: Thu, 13 Sep 2018 09:04:51 +0200	[thread overview]
Message-ID: <a938e477609ae123ae61aec515daa34ccaf0b8f3.camel@suse.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1809121559330.4255@sstabellini-ThinkPad-X260>


[-- Attachment #1.1: Type: text/plain, Size: 1229 bytes --]

On Wed, 2018-09-12 at 16:03 -0700, Stefano Stabellini wrote:
> Hi Dario,
> 
> Milan has just found a bug in the null scheduler: apparently it is
> not
> possible to start a VM again after it has been destroyed.
> 
> My initial suspicion was that the VM wasn't properly destroyed, but I
> asked Milan to double check with xl list, and the VM doesn't show in
> the
> list anymore.
> 
Ok. With what version of Xen? Is PCI passthrough/device assignment
involved? I'm asking because this highly reminds me of this:

https://lists.xen.org/archives/html/xen-devel/2017-07/msg00501.html

Which then led to this:

https://www.mail-archive.com/xen-devel@lists.xen.org/msg105388.html

And to the following changes (related to RCU, which is how complete
destruction of a domain occurs):

2b936ea7b "xen: RCU: avoid busy waiting until the end of grace period."
38ad8151f "xen: RCU: don't let a CPU with a callback go idle."
...

Are these commit there?

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

  reply	other threads:[~2018-09-13  7:05 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 [this message]
     [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
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=a938e477609ae123ae61aec515daa34ccaf0b8f3.camel@suse.com \
    --to=dfaggioli@suse.com \
    --cc=milanboberic94@gmail.com \
    --cc=sstabellini@kernel.org \
    --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).