From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:58073)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <arnd@arndb.de>) id 1UJttx-0008LR-Mm
	for qemu-devel@nongnu.org; Sun, 24 Mar 2013 19:00:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <arnd@arndb.de>) id 1UJttg-0006qH-Ss
	for qemu-devel@nongnu.org; Sun, 24 Mar 2013 19:00:33 -0400
Received: from moutng.kundenserver.de ([212.227.17.10]:59607)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <arnd@arndb.de>) id 1UJttg-0006nd-IF
	for qemu-devel@nongnu.org; Sun, 24 Mar 2013 19:00:16 -0400
From: Arnd Bergmann <arnd@arndb.de>
Date: Sun, 24 Mar 2013 22:59:02 +0000
References: <1364124760-5794-1-git-send-email-peter.maydell@linaro.org>
	<201303242116.28340.arnd@arndb.de>
	<20130324213736.GC31631@redhat.com>
In-Reply-To: <20130324213736.GC31631@redhat.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201303242259.02738.arnd@arndb.de>
Subject: Re: [Qemu-devel] [PATCH 00/10] Fix versatile_pci (and break
	versatilepb linux guests!)
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, patches@linaro.org, Will Deacon <will.deacon@arm.com>, qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>, Andreas =?iso-8859-1?q?F=E4rber?= <afaerber@suse.de>, Aurelien Jarno <aurelien@aurel32.net>

On Sunday 24 March 2013, Michael S. Tsirkin wrote:
> For future kernels, let's build in some hook that let
> qemu detect a non broken guest. How about writing
> some magic value into revision ID or some other
> readonly field?

Yes, makes sense.