From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43832) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e7lzx-0004gY-Us for qemu-devel@nongnu.org; Thu, 26 Oct 2017 13:31:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e7lzx-0004b0-2k for qemu-devel@nongnu.org; Thu, 26 Oct 2017 13:31:17 -0400 MIME-Version: 1.0 In-Reply-To: References: <20171023122719.17199-1-Jason@zx2c4.com> <10e16ca3-175b-9f34-65e7-031b883b7201@amsat.org> <20171026133445.kemzfgvpbmtcogsl@kamzik.brq.redhat.com> From: "Jason A. Donenfeld" Date: Thu, 26 Oct 2017 19:31:05 +0200 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH] hw/arm/virt: support 4 serial ports List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Andrew Jones , =?UTF-8?Q?Philippe_Mathieu=2DDaud=C3=A9?= , QEMU Trivial , qemu-arm , QEMU Developers On Thu, Oct 26, 2017 at 6:41 PM, Peter Maydell 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.