All of lore.kernel.org
 help / color / mirror / Atom feed
From: "wangyanan (Y)" <wangyanan55@huawei.com>
To: Andrew Jones <drjones@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel P . Berrange" <berrange@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	Cornelia Huck <cohuck@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PULL 1/1] machine: Disallow specifying topology parameters as zero
Date: Tue, 17 Aug 2021 21:29:50 +0800	[thread overview]
Message-ID: <07d21640-847d-890c-d85d-8fff7cf4abd3@huawei.com> (raw)
In-Reply-To: <20210817122238.hb2dk2a2zmhqrv7h@gator.home>

On 2021/8/17 20:22, Andrew Jones wrote:
> On Tue, Aug 17, 2021 at 01:06:19PM +0100, Peter Maydell wrote:
>> On Tue, 17 Aug 2021 at 13:02, Andrew Jones <drjones@redhat.com> wrote:
>>> On Mon, Aug 16, 2021 at 11:37:21PM +0200, Paolo Bonzini wrote:
>>>> How do we know that no one has ever used such configuration? The conversion
>>>> was meant to be bug-compatible.
>>> We don't. But we do know that a zero input value was never documented
>>> prior to 1e63fe68580, which has not yet been released. Can we claim
>>> that an undocumented input value has undefined behavior, giving us
>>> freedom to modify that behavior until it is documented?
>> Dunno; I definitely don't want a behaviour-change patch at this
>> point in the release-cycle, though...
>>
> Can we replace this patch with the following one for now? And then
> discuss this further before committing to supporting a zero input?
Yeah, I think at least the doc needs to be fixed in 6.1.

Then we may think about deprecating this behavior since 6.2,
I have implemented the deprecation locally and it can be post
with the smp parsing improvement series.

Thanks,
Yanan
.
> Thanks,
> drew
>
> Author: Andrew Jones <drjones@redhat.com>
> Date:   Tue Aug 17 14:17:29 2021 +0200
>
>      qapi/machine.json: Remove zero value reference from SMPConfiguration documentation
>      
>      Commit 1e63fe685804 ("machine: pass QAPI struct to mc->smp_parse")
>      introduced documentation stating that a zero input value for an SMP
>      parameter indicates that its value should be automatically configured.
>      This is indeed how things work today, but we'd like to change that.
>      Avoid documenting behaviors we want to leave undefined for the time
>      being, giving us freedom to change it later.
>      
>      Fixes: 1e63fe685804 ("machine: pass QAPI struct to mc->smp_parse")
>      Signed-off-by: Andrew Jones <drjones@redhat.com>
>
> diff --git a/qapi/machine.json b/qapi/machine.json
> index c3210ee1fb24..157712f00614 100644
> --- a/qapi/machine.json
> +++ b/qapi/machine.json
> @@ -1288,7 +1288,7 @@
>   ##
>   # @SMPConfiguration:
>   #
> -# Schema for CPU topology configuration.  "0" or a missing value lets
> +# Schema for CPU topology configuration.  A missing value lets
>   # QEMU figure out a suitable value based on the ones that are provided.
>   #
>   # @cpus: number of virtual CPUs in the virtual machine
>
> .



  parent reply	other threads:[~2021-08-17 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-16 21:06 [PULL 0/1] Last minute fix for -rc4 Eduardo Habkost
2021-08-16 21:06 ` [PULL 1/1] machine: Disallow specifying topology parameters as zero Eduardo Habkost
2021-08-16 21:37   ` Paolo Bonzini
2021-08-17 12:02     ` Andrew Jones
2021-08-17 12:06       ` Peter Maydell
2021-08-17 12:22         ` Andrew Jones
2021-08-17 12:37           ` Peter Maydell
2021-08-17 12:54             ` Andrew Jones
2021-08-17 13:29           ` wangyanan (Y) [this message]
2021-08-16 21:38 ` [PULL 0/1] Last minute fix for -rc4 Paolo Bonzini

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=07d21640-847d-890c-d85d-8fff7cf4abd3@huawei.com \
    --to=wangyanan55@huawei.com \
    --cc=berrange@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=drjones@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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.