From: Julien Grall <julien.grall@arm.com>
To: Oleksandr Tyshchenko <olekstysh@gmail.com>,
xen-devel@lists.xenproject.org
Cc: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
sstabellini@kernel.org, mirela.simonovic@aggios.com
Subject: Re: [PATCH v2 0/2] CPU hotplug fixes for ARM32
Date: Fri, 7 Dec 2018 10:02:03 +0000 [thread overview]
Message-ID: <f7b7d683-c44d-ad52-2487-64be088ab7d0@arm.com> (raw)
In-Reply-To: <1544175931-17047-1-git-send-email-olekstysh@gmail.com>
On 07/12/2018 09:45, Oleksandr Tyshchenko wrote:
> From: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
>
> Hi, all.
>
> This is small patch series for ARM32 which needed to be able to bring
> secondary CPUs up not only during the initial boot, but at runtime also.
> For example, during CPU hotplug.
OOI, we don't have CPU hotplug in Xen at the moment. So do you have CPU hotplug
patch coming up?
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-12-07 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 9:45 [PATCH v2 0/2] CPU hotplug fixes for ARM32 Oleksandr Tyshchenko
2018-12-07 9:45 ` [PATCH v2 1/2] xen/arm: link: Link proc_info_list in .data instead of .init.data Oleksandr Tyshchenko
2018-12-07 10:05 ` Julien Grall
2018-12-07 10:32 ` Oleksandr Tyshchenko
2018-12-07 10:34 ` Julien Grall
2018-12-07 13:51 ` Oleksandr
2018-12-07 9:45 ` [PATCH v2 2/2] xen/arm32: Remove __init prefixes from funcs that are used within CPU up flow Oleksandr Tyshchenko
2018-12-07 10:02 ` Julien Grall [this message]
2018-12-07 12:21 ` [PATCH v2 0/2] CPU hotplug fixes for ARM32 Oleksandr
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=f7b7d683-c44d-ad52-2487-64be088ab7d0@arm.com \
--to=julien.grall@arm.com \
--cc=mirela.simonovic@aggios.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=olekstysh@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 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.