From: Nathan Fontenot <nfont@linux.vnet.ibm.com>
To: Tyrel Datwyler <tyreld@linux.vnet.ibm.ocm>,
linuxppc-dev@lists.ozlabs.org
Cc: nacc@linux.vnet.ibm.com,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] powerpc/pseries: hibernation/migration should honor topology update policy
Date: Tue, 05 May 2015 21:11:07 -0500 [thread overview]
Message-ID: <5549783B.4010605@linux.vnet.ibm.com> (raw)
In-Reply-To: <1430848434-25793-1-git-send-email-tyreld@linux.vnet.ibm.ocm>
On 05/05/2015 12:53 PM, Tyrel Datwyler wrote:
> From: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
>
> The suspend call paths for hibernation and migration operations call
> stop_topology_update() and start_topology_update() respectively prior to
> suspending the LPAR and upon resume. Topology updating can be
> enabled/disabled from userspace and no check is currently done to determine
> the current policy. This results in topology updates being started upon
> resume from hibernation/migration even in the case where topology updates
> were disabled initially.
>
> This fixes the issue by storing the current policy and only calling
> start_topology_update() in the case where either PRRN/VPHN were enabled to
> start with.
>
> Fixes: e04fa61214a3 (powerpc/pseries: Add /proc interface to control topology updates)
>
> Signed-off-by: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
> Cc: Nathan Fontenot <nfont@linux.vnet.ibm.com>
> Cc: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
> Cc: stable@vger.kernel.org
Reviewed-by: Nathan Fontenot <nfont@linux.vnet.ibm.com>
next parent reply other threads:[~2015-05-06 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1430848434-25793-1-git-send-email-tyreld@linux.vnet.ibm.ocm>
2015-05-06 2:11 ` Nathan Fontenot [this message]
2015-10-02 20:57 ` [PATCH] powerpc/pseries: hibernation/migration should honor topology update policy Tyrel Datwyler
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=5549783B.4010605@linux.vnet.ibm.com \
--to=nfont@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nacc@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--cc=tyreld@linux.vnet.ibm.com \
--cc=tyreld@linux.vnet.ibm.ocm \
/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 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).