All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
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: Fri, 8 Dec 2017 11:49:07 +0000	[thread overview]
Message-ID: <CAFEAcA-5F2GMx9UNoH=LJAa-m1DXg2HW8PJZ47kurjx5x3NhWA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qNnqYEbW_m8LG0E0HBKUE38YjUodbBihnSi2k0FrZJtw@mail.gmail.com>

On 26 October 2017 at 18:31, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
> 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.

Now that the 2.11 release is mostly out of the way, I've been
working through some of my other todo list items so I've
come back to this thread.

My suggestion is that we should add a second non-secure UART
to the virt board, so if you're using secure=no then you
get serial 1 and 2, and for secure=yes serial 1 is the first
NS uart, serial 2 is the secure uart and serial 3 is the
2nd NS uart. (I don't really want to add a 4th uart unless
there's some good reason to -- maybe we would turn out to
want it for the secure side, for instance.)

I'll probably write a patch for this next week, unless you
want to do it.

thanks
-- PMM

  reply	other threads:[~2017-12-08 11:49 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
2017-12-08 11:49                       ` Peter Maydell [this message]
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='CAFEAcA-5F2GMx9UNoH=LJAa-m1DXg2HW8PJZ47kurjx5x3NhWA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=Jason@zx2c4.com \
    --cc=drjones@redhat.com \
    --cc=f4bug@amsat.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 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.