From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH for-2.10] numa: Move numa_legacy_auto_assign_ram to pc-i440fx-2.9
Date: Fri, 18 Aug 2017 16:15:34 -0300 [thread overview]
Message-ID: <20170818191534.GE3108@localhost.localdomain> (raw)
In-Reply-To: <20170818190943.23858-1-ehabkost@redhat.com>
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 <ehabkost@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?
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.
--
Eduardo
next prev parent reply other threads:[~2017-08-18 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 19:09 [Qemu-devel] [PATCH for-2.10] numa: Move numa_legacy_auto_assign_ram to pc-i440fx-2.9 Eduardo Habkost
2017-08-18 19:15 ` Eduardo Habkost [this message]
2017-08-21 11:17 ` Igor Mammedov
2017-08-21 12:00 ` Peter Maydell
2017-08-23 12:47 ` Igor Mammedov
2017-08-23 15:13 ` Peter Maydell
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=20170818191534.GE3108@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).