qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [for-5.0] Deprecate KVM support for AArch32
Date: Wed, 15 Apr 2020 13:42:36 +0100	[thread overview]
Message-ID: <20200415124236.GG1344391@redhat.com> (raw)
In-Reply-To: <CAFEAcA80g-Zohi0t7u51aNs58i8_zPCOcRob6zx6DYdTjYfXWQ@mail.gmail.com>

On Wed, Apr 15, 2020 at 01:41:05PM +0100, Peter Maydell wrote:
> On Wed, 15 Apr 2020 at 13:33, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Tue, Apr 14, 2020 at 01:09:35PM +0100, Peter Maydell wrote:
> > > The Linux kernel has dropped support for allowing 32-bit Arm systems
> > > to host KVM guests (kernel commit 541ad0150ca4aa663a2, which just
> > > landed upstream in the 5.7 merge window).  Mark QEMU's support for
> > > this configuration as deprecated, so that we can delete that support
> > > code in 5.2.
> > >
> > > Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> > > ---
> > > I was reading the 5.7 merge window writeup on LWN this weekend
> > > and saw that the dropping of 32-bit support had gone in; just
> > > enough time to squeeze our deprecation warning into 5.0 so we
> > > can drop the code in 5.2 rather than 6.0...
> > >
> > >  docs/system/deprecated.rst | 8 ++++++++
> > >  1 file changed, 8 insertions(+)
> >
> > The docs are sufficient to start the deprecation process, but
> > we might consider also having a warning from configure, or a
> > message on stderr at runtime to make it more visible to users.
> 
> Mmm. I didn't feel entirely comfortable making code changes to
> print messages at this point in the 5.0 release cycle, though.

Sure, that's understandable.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2020-04-15 12:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 12:09 [for-5.0] Deprecate KVM support for AArch32 Peter Maydell
2020-04-14 12:59 ` Andrew Jones
2020-04-14 16:29 ` Richard Henderson
2020-04-15 12:33 ` Daniel P. Berrangé
2020-04-15 12:41   ` Peter Maydell
2020-04-15 12:42     ` Daniel P. Berrangé [this message]
2020-04-15 15:12 ` Alex Bennée

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=20200415124236.GG1344391@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.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 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).