On 06/13/2019 06:05 PM, Nathan Lynch wrote:
> Nathan Lynch writes:
>
>> Tyrel Datwyler writes:
>>
>>> Maybe we are ok with this behavior as I haven't dug deep enough into the
>>> memory
>>> subsystem here to really understand what the memory code is updating, but
>>> it is
>>> concerning that
On Fri, 2019-06-07 at 05:04:07 UTC, Nathan Lynch wrote:
> During post-migration device tree updates, we can oops in
> pseries_update_drconf_memory if the source device tree has an
> ibm,dynamic-memory-v2 property and the destination has a
> ibm,dynamic_memory (v1) property. The notifier processes
Nathan Lynch writes:
> Tyrel Datwyler writes:
>
>> Maybe we are ok with this behavior as I haven't dug deep enough into the
>> memory
>> subsystem here to really understand what the memory code is updating, but it
>> is
>> concerning that we are doing it in some cases, but not all.
>
> I hope
Tyrel Datwyler writes:
> On 06/06/2019 10:04 PM, Nathan Lynch wrote:
>> During post-migration device tree updates, we can oops in
>> pseries_update_drconf_memory if the source device tree has an
>> ibm,dynamic-memory-v2 property and the destination has a
>> ibm,dynamic_memory (v1) property. The
On 06/06/2019 10:04 PM, Nathan Lynch wrote:
> During post-migration device tree updates, we can oops in
> pseries_update_drconf_memory if the source device tree has an
> ibm,dynamic-memory-v2 property and the destination has a
> ibm,dynamic_memory (v1) property. The notifier processes an "update"
Michael Ellerman writes:
> Nathan Lynch writes:
>
>> During post-migration device tree updates, we can oops in
>> pseries_update_drconf_memory if the source device tree has an
>> ibm,dynamic-memory-v2 property and the destination has a
>> ibm,dynamic_memory (v1) property. The notifier processes
Nathan Lynch writes:
> During post-migration device tree updates, we can oops in
> pseries_update_drconf_memory if the source device tree has an
> ibm,dynamic-memory-v2 property and the destination has a
> ibm,dynamic_memory (v1) property. The notifier processes an "update"
> for the
During post-migration device tree updates, we can oops in
pseries_update_drconf_memory if the source device tree has an
ibm,dynamic-memory-v2 property and the destination has a
ibm,dynamic_memory (v1) property. The notifier processes an "update"
for the ibm,dynamic-memory property but it's really