From: Peter Maydell <peter.maydell@linaro.org>
To: Andrew Jones <drjones@redhat.com>
Cc: "Daniel P . Berrange" <berrange@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Yanan Wang <wangyanan55@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PULL 1/1] machine: Disallow specifying topology parameters as zero
Date: Tue, 17 Aug 2021 13:06:19 +0100 [thread overview]
Message-ID: <CAFEAcA_fOa4uV3sA5kxJ1gKTGS3ASgvx2+FrG=5cr0wWaQ48-Q@mail.gmail.com> (raw)
In-Reply-To: <20210817120250.fdpujloefaqtawwo@gator.home>
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...
-- PMM
next prev parent reply other threads:[~2021-08-17 12:08 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 [this message]
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)
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='CAFEAcA_fOa4uV3sA5kxJ1gKTGS3ASgvx2+FrG=5cr0wWaQ48-Q@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wangyanan55@huawei.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 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.