From: julien.grall@citrix•com (Julien Grall)
To: linux-arm-kernel@lists•infradead.org
Subject: [Xen-devel] xen,arm: enable cpu_hotplug
Date: Fri, 16 Oct 2015 16:45:55 +0100 [thread overview]
Message-ID: <56211BB3.9020605@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510161635520.27957@kaball.uk.xensource.com>
On 16/10/15 16:41, Stefano Stabellini wrote:
> It is possible to shut down cpu1 (psci->cpu_off, which pauses the vcpu)
> but it is not possible to remove cpu1 without removing cpu2 first.
>
> If the user configures the target to be cpu 2-4, then shuts down cpu2, it
> won't receive any interrupts any more. This is not a cpu-hotplug bug.
> Maybe is a do_psci_cpu_off bug, which should be improved to handle this
> case.
It's neither a PSCI cpu off bug. It's a bug in our vGIC implementation.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-10-16 15:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 17:49 xen,arm: enable cpu_hotplug Stefano Stabellini
2015-10-14 17:49 ` [PATCH 1/3] xen/arm: Enable cpu_hotplug.c Stefano Stabellini
2015-10-14 18:05 ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-10-14 18:17 ` Stefano Stabellini
2015-10-16 15:21 ` Stefano Stabellini
2015-10-14 22:51 ` Julien Grall
2015-10-16 15:23 ` Stefano Stabellini
2015-10-14 17:49 ` [PATCH 2/3] xen, cpu_hotplug: call device_offline instead of cpu_down Stefano Stabellini
2015-10-14 17:49 ` [PATCH 3/3] xen/arm: don't try to re-register vcpu_info on cpu_hotplug Stefano Stabellini
2015-10-14 22:32 ` Julien Grall
2015-10-16 15:31 ` Stefano Stabellini
2015-10-14 23:23 ` xen,arm: enable cpu_hotplug Julien Grall
2015-10-15 8:39 ` [Xen-devel] " Ian Campbell
2015-10-15 9:57 ` Julien Grall
2015-10-15 9:58 ` Julien Grall
2015-10-16 15:44 ` Stefano Stabellini
2015-10-16 15:41 ` Stefano Stabellini
2015-10-16 15:45 ` Julien Grall [this message]
2015-10-16 15:45 ` Stefano Stabellini
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=56211BB3.9020605@citrix.com \
--to=julien.grall@citrix$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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