From: Paolo Bonzini <pbonzini@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Tao Xu <tao3.xu@intel.com>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [PATCH 0/2] numa: stop abusing numa_mem_supported
Date: Fri, 20 Dec 2019 14:14:58 +0100 [thread overview]
Message-ID: <465595b7-eadd-7fb7-deba-fee7b0ae1440@redhat.com> (raw)
In-Reply-To: <20191219144209.3c80dd69@redhat.com>
On 19/12/19 14:42, Igor Mammedov wrote:
> On Thu, 19 Dec 2019 08:30:34 -0500
> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
>> On Thu, Dec 19, 2019 at 02:28:51PM +0100, Igor Mammedov wrote:
>>> On Thu, 12 Dec 2019 13:48:54 +0100
>>> Igor Mammedov <imammedo@redhat.com> wrote:
>>>
>>>> A fix and cleanup for a mistakes that slipped by me in
>>>> aa57020774 (numa: move numa global variable nb_numa_nodes into MachineState)
>>>
>>> ping,
>>>
>>> could someone pick it up please?
>>
>> Looks more like Eduardo's thing.
>
> Yep if he is still available,
> but I wasn't sure with coming winter break.
>
> In addition, this patch will be prerequisite for disabling
> deprecated '-numa node,mem'
> hence broadcast ping to make sure it won't get lost.
I'll take care of it (after new year).
Paolo
next prev parent reply other threads:[~2019-12-20 13:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 12:48 [PATCH 0/2] numa: stop abusing numa_mem_supported Igor Mammedov
2019-12-12 12:48 ` [PATCH 1/2] numa: remove not needed check Igor Mammedov
2019-12-19 17:45 ` Eduardo Habkost
2019-12-12 12:48 ` [PATCH 2/2] numa: properly check if numa is supported Igor Mammedov
2019-12-13 1:33 ` Tao Xu
2019-12-13 9:12 ` Igor Mammedov
2019-12-16 1:03 ` Tao Xu
2019-12-19 17:57 ` Eduardo Habkost
2019-12-19 13:28 ` [PATCH 0/2] numa: stop abusing numa_mem_supported Igor Mammedov
2019-12-19 13:30 ` Michael S. Tsirkin
2019-12-19 13:42 ` Igor Mammedov
2019-12-20 13:14 ` Paolo Bonzini [this message]
2019-12-20 15:11 ` Igor Mammedov
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=465595b7-eadd-7fb7-deba-fee7b0ae1440@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tao3.xu@intel.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).