From: Michael Bringmann <mwb@linux.vnet.ibm.com>
To: Michael Ellerman <patch-notifications@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org
Cc: Nathan Fontenot <nfont@linux.vnet.ibm.com>,
minkim@us.ibm.com, Thomas Falcon <tlfalcon@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
Subject: RESCIND Re: [v02] REPOST powerpc/migration: Handle unitialized timer reset
Date: Wed, 26 Sep 2018 09:54:03 -0500 [thread overview]
Message-ID: <8816c05c-efc5-0b99-2de4-9cdf5480dd1a@linux.vnet.ibm.com> (raw)
In-Reply-To: <3b78a11a-296e-00ac-3648-b26ce7c8aaac@linux.vnet.ibm.com>
Hello, Michael:
I am an idiot this morning. Not enough coffee.
I confused this posting with another. Please forget the request.
We do want to omit
[PATCH v08 0/5] powerpc/hotplug: Update affinity for migrated CPUs
https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-July/176301.html
though.
Very sorry for the inconvenience.
Michael
On 09/26/2018 09:44 AM, Michael Bringmann wrote:
> Hello, Michael:
> Please look at v03 of the patch set which was posted
> just on 09/25/2018. We had a last minute brainstorm of how
> to simplify the code after the v02 REPOST.
> Also, note that we would like to invalidate the set,
>
> [PATCH v08 0/5] powerpc/hotplug: Update affinity for migrated CPUs
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2018-July/176301.html
>
> as we think it is covered now by other code.
>
> Thanks for your attention and assistance.
>
> Michael
>
> On 09/26/2018 07:13 AM, Michael Ellerman wrote:
>> On Thu, 2018-09-20 at 16:45:13 UTC, Michael Bringmann wrote:
>>> After migration of a powerpc LPAR, the kernel executes code to
>>> update the system state to reflect new platform characteristics.
>>> Such changes include modifications to device tree properties
>>> provided to the system by PHYP. Property notifications received
>>> by the powerpc 'migration_store' code are passed along to the
>>> kernel in general through a call to 'of_update_property' which
>>> in turn passes such events back to all modules through entries like
>>> the '.notifier_call' function within the NUMA module. When the
>>> NUMA module updates its state, it resets its event timer. If this
>>> occurs after a previous call to 'stop_topology_update' or on a
>>> system without VPHN enabled, the code runs into an unitialized
>>> timer structure and crashes. This patch adds a safety check
>>> along this path toward the problem code.
>>>
>>> Note: This crash was observed on every LPM in the 4.17-rc7 kernel
>>> (and in the 4.18 kernel) of a system with dedicated CPUs enabled.
>>> An example crash log without the patch is as follows.
>>>
>> ...
>>>
>>> Signed-off-by: Michael Bringmann <mwb@linux.vnet.ibm.com>
>>
>> Applied to powerpc fixes, thanks.
>>
>> https://git.kernel.org/powerpc/c/8604895a34d92f5e186ceb931b0d1b
>>
>> cheers
>>
>>
>
--
Michael W. Bringmann
Linux Technology Center
IBM Corporation
Tie-Line 363-5196
External: (512) 286-5196
Cell: (512) 466-0650
mwb@linux.vnet.ibm.com
next prev parent reply other threads:[~2018-09-26 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 16:45 [PATCH v02] REPOST powerpc/migration: Handle unitialized timer reset Michael Bringmann
2018-09-26 12:13 ` [v02] " Michael Ellerman
2018-09-26 14:44 ` Michael Bringmann
2018-09-26 14:54 ` Michael Bringmann [this message]
2018-09-27 6:57 ` RESCIND " Michael Ellerman
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=8816c05c-efc5-0b99-2de4-9cdf5480dd1a@linux.vnet.ibm.com \
--to=mwb@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=minkim@us.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=patch-notifications@ellerman.id.au \
--cc=tlfalcon@linux.vnet.ibm.com \
--cc=tyreld@linux.vnet.ibm.com \
/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).