On 18 August 2017 at 20:15, Eduardo Habkost <ehabk...@redhat.com> wrote:
> On Fri, Aug 18, 2017 at 04:09:43PM -0300, Eduardo Habkost wrote:
>> The 'm->numa_auto_assign_ram = numa_legacy_auto_assign_ram;' line
>> was supposed to be in pc_i440fx_2_9_machine_options() (see commit
>> 3bfe5716 "numa: equally distribute memory on nodes"), but the
>> merge commit adb354dd ("Merge remote-tracking branch
>> 'mst/tags/for_upstream' into staging") moved it to the
>> pc_i440fx_2_10_machine_options().
>>
>> Move the line back to pc_i440fx_2_9_machine_options().
>>
>> Signed-off-by: Eduardo Habkost <ehabk...@redhat.com>
>
> I just re-read the schedule wiki page and noticed 2017-08-22 is
> "release _or_ tag -rc4". Does this mean including this patch
> would slip the schedule for 1 week?
Yes; we have a few patches of the "include this if we're doing
an rc4 anyway" variety, but currently nothing that would mean
we need to do an rc4.
> In that case, I don't think this patch should block the release
> and cause a schedule slip. We can simply change the NUMA RAM
> assignment algorithm in pc-2.11 and keep the old one in pc-2.10.
OK.
thanks
-- PMM
