From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Cc: libvir-list@redhat.com, rth@twiddle.net, qemu-devel@nongnu.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] smp: drop support for deprecated (invalid topologies)
Date: Sun, 20 Sep 2020 14:10:02 +0200 [thread overview]
Message-ID: <5a023af0-72b2-0e6e-b3cc-24e4f71c5aa8@redhat.com> (raw)
In-Reply-To: <20200918205742.GB8041@habkost.net>
On 18/09/20 22:57, Eduardo Habkost wrote:
> On Mon, Sep 14, 2020 at 09:37:20AM +0200, Igor Mammedov wrote:
>> On Fri, 11 Sep 2020 11:04:47 -0400
>> "Michael S. Tsirkin" <mst@redhat.com> wrote:
>>
>>> On Fri, Sep 11, 2020 at 09:32:02AM -0400, Igor Mammedov wrote:
>>>> it's was deprecated since 3.1
>>>>
>>>> Support for invalid topologies is removed, the user must ensure
>>>> that topologies described with -smp include all possible cpus,
>>>> i.e. (sockets * cores * threads) == maxcpus or QEMU will
>>>> exit with error.
>>>>
>>>> Signed-off-by: Igor Mammedov <imammedo@redhat.com>
>>>
>>> Acked-by:
>>>
>>> memory tree I guess?
>>
>> It would be better for Paolo to take it since he has
>> queued numa deprecations, due to context confilict in
>> deprecated.rst.
>>
>> Paolo,
>> can you queue this patch as well?
>
> I'm queueing this in machine-next (sorry for not noticing it
> before I sent today's pull request).
It's not part of my pending pull request, so whoever comes second will
drop the patch.
Paolo
prev parent reply other threads:[~2020-09-20 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 13:32 [PATCH] smp: drop support for deprecated (invalid topologies) Igor Mammedov
2020-09-11 15:04 ` Michael S. Tsirkin
2020-09-14 7:37 ` Igor Mammedov
2020-09-18 20:57 ` Eduardo Habkost
2020-09-20 12:10 ` Paolo Bonzini [this message]
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=5a023af0-72b2-0e6e-b3cc-24e4f71c5aa8@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.