On 14/06/2019 12:37, Jan Beulich wrote:
> Aiui when resuming from S3, CPUs come back out of RESET/INIT.
From a programmers point of view, all APs are in Wait-for-SIPI after
resume, and this is confirmed by several of the BWG flowcharts. This is
a logical consequence of the CPU losing all power,
Hi Jan,
On 6/17/19 7:40 AM, Jan Beulich wrote:
On 14.06.19 at 18:52, wrote:
The title and commit message are a bit odd to read because you are modifying
common code but everything is geared towards x86.
Indeed. There's no caller of {en,dis}able_nonboot_cpus() in Arm code
at present, afaics.
>>> On 14.06.19 at 18:52, wrote:
> The title and commit message are a bit odd to read because you are modifying
> common code but everything is geared towards x86.
Indeed. There's no caller of {en,dis}able_nonboot_cpus() in Arm code
at present, afaics. Hence the code changed (but not the file)
Hi Jan,
The title and commit message are a bit odd to read because you are modifying
common code but everything is geared towards x86.
On 14/06/2019 12:37, Jan Beulich wrote:
Aiui when resuming from S3, CPUs come back out of RESET/INIT. Therefore
they need to undergo the same procedure as
Aiui when resuming from S3, CPUs come back out of RESET/INIT. Therefore
they need to undergo the same procedure as was added elsewhere by
commits d8f974f1a6 ("x86: command line option to avoid use of secondary
hyper-threads") and 8797d20a6e ("x86: possibly bring up all CPUs even
if not all are
