xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Anna-Maria Gleixner <anna-maria@linutronix.de>,
	David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: FROZEN transitions hotplug notifier
Date: Thu, 17 Mar 2016 10:57:26 +0000	[thread overview]
Message-ID: <56EA8D96.3060604@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1603161703170.30089@hypnos>

On 16/03/16 17:49, Anna-Maria Gleixner wrote:
> Hi,
> the hotplug notifieres in the following files don't handle the
> corresponding FROZEN transitions:
>       arch/arm/xen/enlighten.c
>       arch/x86/xen/enlighten.c
>       drivers/xen/events/events_fifo.c
> Is there a reason for it?

Xen guests do not offline/online CPUs during suspend/resume so I think
the FROZEN states will never be seen.


Xen-devel mailing list

      reply	other threads:[~2016-03-17 10:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 17:49 FROZEN transitions hotplug notifier Anna-Maria Gleixner
2016-03-17 10:57 ` David Vrabel [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56EA8D96.3060604@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=anna-maria@linutronix.de \
    --cc=boris.ostrovsky@oracle.com \
    --cc=rt@linutronix.de \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.org \


* 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).