qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Andrew Jones" <drjones@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"QEMU Trivial" <qemu-trivial@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH] hw/arm/virt: support 4 serial ports
Date: Thu, 26 Oct 2017 19:31:05 +0200	[thread overview]
Message-ID: <CAHmME9qNnqYEbW_m8LG0E0HBKUE38YjUodbBihnSi2k0FrZJtw@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-bKPNwJpcny=1azScO8bzHsi0Ou+m3rYPq-=v52Gf26g@mail.gmail.com>

On Thu, Oct 26, 2017 at 6:41 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> Those are primarily about migration compatibility -- you should
> be able to live migrate a guest from QEMU 2.6's virt-2.6 machine to
> QEMU 2.7's virt-2.6 machine. That's a stricter requirement than
> the compatibility we want to keep for non-versioned machines,
> where generally we don't want to break command lines but are OK
> to make changes if they don't break those existing uses.
>
> Command lines get baked into all sorts of scripts and so they're
> effectively part of QEMU's "ABI". People don't like it when we
> break their previously working flows :-)

Fair enough. So in that case, secure=no means serials 1-4 are for
kernel. With secure=yes, serials 1,3-5 are for kernel, with serial 2
being for trustzone. Seems like that's the best of all worlds.

  reply	other threads:[~2017-10-26 17:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 12:27 [Qemu-devel] [PATCH] hw/arm/virt: support 4 serial ports Jason A. Donenfeld
2017-10-23 12:35 ` no-reply
2017-10-23 13:11 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2017-10-23 13:48   ` Philippe Mathieu-Daudé
2017-10-24 17:57     ` Jason A. Donenfeld
2017-10-26 13:34       ` Andrew Jones
2017-10-26 14:13         ` Jason A. Donenfeld
2017-10-26 14:36           ` Peter Maydell
2017-10-26 16:15             ` Jason A. Donenfeld
2017-10-26 16:34               ` Peter Maydell
2017-10-26 16:36                 ` Jason A. Donenfeld
2017-10-26 16:41                   ` Peter Maydell
2017-10-26 17:31                     ` Jason A. Donenfeld [this message]
2017-12-08 11:49                       ` Peter Maydell
2017-12-08 18:39                         ` Jason A. Donenfeld
2017-12-10 18:15                           ` Peter Maydell
2017-10-23 14:14   ` Jason A. Donenfeld

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=CAHmME9qNnqYEbW_m8LG0E0HBKUE38YjUodbBihnSi2k0FrZJtw@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=drjones@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).