From: Julien Grall <julien.grall@arm.com>
To: Mirela Simonovic <mirela.simonovic@aggios.com>
Cc: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Davorin Mista <dm@aggios.com>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0/7] xen/arm: CPU hotplug fixes
Date: Mon, 16 Apr 2018 16:05:09 +0100 [thread overview]
Message-ID: <f73b88fa-0277-70b0-e928-c8e3fc6b41e7@arm.com> (raw)
In-Reply-To: <CAKPH-Ni3YvxmtcARQCvuHb4gbKnrJ+qXHQWnvvTs40uQf7pZgw@mail.gmail.com>
Hi Mirela,
On 16/04/18 15:06, Mirela Simonovic wrote:
> On Mon, Apr 16, 2018 at 1:33 PM, Julien Grall <julien.grall@arm.com> wrote:
>> On 13/04/18 11:19, Mirela Simonovic wrote:
>>> On Thu, Apr 12, 2018 at 10:43 AM, Julien Grall <julien.grall@arm.com>
>>>> On 11/04/18 17:37, Mirela Simonovic wrote:
>>>>> On Wed, Apr 11, 2018 at 6:02 PM, Julien Grall <julien.grall@arm.com
>>>>> <mailto:julien.grall@arm.com>> wrote:
>>>> So this cover interrupt routed to a virtual CPU. However, this does not
>>>> handle interrupts used by Xen. How do you handle them?
>>>>
>>>> For instance SMMUs IRQ might be routed to other interrupt than CPU #0.
>>>
>>>
>>> Interrupts used by Xen should not wake-up the system and will be
>>> disabled when we suspend the devices used by Xen.
>>
>> Here you only speak about the suspend use case. While I understand your
>> ultimate goal is suspend/resume, this series is about CPU hotplug.
>>
>
> AFAIK, the only way and occasion to hotplug a CPU is using > disable/enable_nonboot_cpus() within the Xen suspend/resume procedure.
As I mention in a previous e-mail, suspend/resume is not the only way to
hotplug a CPU. There are an interface (see XEN_SYSCTL_cpu_hotplug) to
allow that from the userland.
But I agree that it is not implemented on Arm, so suspend/resume would
be the only way to so far. To be clear, I am not asking you to implement
XEN_SYSCTL_cpu_hotplug. Althougth it should be easy to do it and easy
for testing CPU offline/online.
> We are implementing CPU hotplug only to enable Xen suspend/resume.
>
> This is how it is also done for x86 and we wanted to implement the
> equivalent behavior for ARM.
> If the cover-letter is misleading please let me know what would be
> more appropriate title.
We have multiple places in Xen that could use cpu_up/cpu_down helpers.
From the cover letter, it is quite unclear that you are only looking
after suspend/resume.
The SYSCTL interface is one of the other use case. While most of the
code can be shared, some of them may not make sense.
For instance, in the suspend/resume case routing the interrupt assigned
to Xen to CPU#0 may not be necessary because all CPUs should come back
later on. However, this should be necessary when offlining a vCPU with
SYSCTL interface.
That's why I asked it and I think it should be clarified in the cover
letter.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-04-16 15:05 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 13:19 [PATCH 0/7] xen/arm: CPU hotplug fixes Mirela Simonovic
2018-04-11 13:19 ` [PATCH 1/7] xen/arm: Added handling of the trapped access to OSLSR register Mirela Simonovic
2018-04-11 14:39 ` Julien Grall
2018-04-11 23:28 ` Stefano Stabellini
2018-04-11 13:19 ` [PATCH 2/7] xen/arm/vgic-v2: Ignore write to GICD_ISACTIVERn registers Mirela Simonovic
2018-04-11 14:43 ` Julien Grall
2018-04-11 23:31 ` Stefano Stabellini
2018-04-12 11:15 ` Mirela Simonovic
2018-04-11 13:19 ` [PATCH 3/7] xen/arm/psci: Implement CPU_OFF PSCI call (physical interface) Mirela Simonovic
2018-04-11 14:46 ` Julien Grall
2018-04-12 11:33 ` Mirela Simonovic
2018-04-12 13:31 ` Julien Grall
2018-04-16 10:02 ` Mirela Simonovic
2018-04-16 14:26 ` Julien Grall
2018-04-16 16:52 ` Mirela Simonovic
2018-04-16 17:02 ` Julien Grall
2018-04-11 13:19 ` [PATCH 4/7] xen/arm: When CPU dies, free percpu area immediatelly Mirela Simonovic
2018-04-11 14:53 ` Julien Grall
2018-04-11 23:46 ` Stefano Stabellini
2018-04-12 8:53 ` Julien Grall
2018-04-12 21:31 ` Stefano Stabellini
2018-04-16 13:14 ` Julien Grall
2018-04-16 13:41 ` Mirela Simonovic
2018-04-16 15:21 ` Julien Grall
2018-04-17 10:52 ` Mirela Simonovic
2018-04-17 11:02 ` Julien Grall
2018-04-18 22:52 ` Stefano Stabellini
2018-04-19 9:32 ` Julien Grall
2018-04-11 13:19 ` [PATCH 5/7] xen/arm: Remove __initdata and __init to enable CPU hotplug Mirela Simonovic
2018-04-12 0:07 ` Stefano Stabellini
2018-04-12 9:03 ` Julien Grall
2018-04-12 12:50 ` Mirela Simonovic
2018-04-12 12:56 ` Julien Grall
2018-04-12 13:55 ` Mirela Simonovic
2018-04-11 13:19 ` [PATCH 6/7] xen/arm: Setup virtual paging for secondary CPUs in non-boot scenario Mirela Simonovic
2018-04-11 15:11 ` Julien Grall
2018-04-17 12:54 ` Mirela Simonovic
2018-04-17 14:11 ` Julien Grall
2018-04-17 15:22 ` Mirela Simonovic
2018-04-18 9:48 ` Julien Grall
2018-04-18 10:34 ` Mirela Simonovic
2018-04-18 10:45 ` Mirela Simonovic
2018-04-18 10:58 ` Julien Grall
2018-04-18 22:56 ` Stefano Stabellini
2018-04-11 13:19 ` [PATCH 7/7] xen/arm: Restore IRQ affinity after hotplugging a CPU Mirela Simonovic
2018-04-11 14:55 ` Julien Grall
2018-04-12 0:20 ` Stefano Stabellini
2018-04-12 7:38 ` Mirela Simonovic
2018-04-12 16:49 ` Dario Faggioli
2018-04-13 10:11 ` Mirela Simonovic
2018-04-16 12:38 ` Dario Faggioli
2018-04-11 15:07 ` [PATCH 0/7] xen/arm: CPU hotplug fixes Julien Grall
2018-04-11 15:58 ` Mirela Simonovic
2018-04-11 16:02 ` Julien Grall
2018-04-11 16:37 ` Mirela Simonovic
2018-04-12 8:43 ` Julien Grall
2018-04-13 10:19 ` Mirela Simonovic
2018-04-16 11:33 ` Julien Grall
2018-04-16 14:06 ` Mirela Simonovic
2018-04-16 15:05 ` Julien Grall [this message]
2018-04-11 15:13 ` Julien Grall
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=f73b88fa-0277-70b0-e928-c8e3fc6b41e7@arm.com \
--to=julien.grall@arm.com \
--cc=dm@aggios.com \
--cc=edgar.iglesias@xilinx.com \
--cc=mirela.simonovic@aggios.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.