From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36183) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UOSr2-0006Du-Mo for qemu-devel@nongnu.org; Sat, 06 Apr 2013 09:08:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UOSr1-00063A-HY for qemu-devel@nongnu.org; Sat, 06 Apr 2013 09:08:24 -0400 Received: from mail-la0-x22d.google.com ([2a00:1450:4010:c03::22d]:34948) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UOSr1-00062r-A4 for qemu-devel@nongnu.org; Sat, 06 Apr 2013 09:08:23 -0400 Received: by mail-la0-f45.google.com with SMTP id fn20so750713lab.32 for ; Sat, 06 Apr 2013 06:08:22 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <2B42F309-792B-4CD6-B2A1-8F82B310E0D8@suse.de> References: <1365007213-27603-1-git-send-email-chouteau@adacore.com> <1365007213-27603-4-git-send-email-chouteau@adacore.com> <7C0E04C3-1FDF-460E-8F78-1E24E5759C93@suse.de> <515D3BDE.20400@adacore.com> <8FE7E3AF-D822-4DBF-8A7E-BD0EA80AD07A@suse.de> <515D69B8.9040007@suse.de> <1365202829.17535.15@snotra> <7DE52476-7B80-40E3-8B9B-F2ABEFE0268B@suse.de> <2B42F309-792B-4CD6-B2A1-8F82B310E0D8@suse.de> From: Peter Maydell Date: Sat, 6 Apr 2013 14:08:02 +0100 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH 3/3] PPC PReP: can run without bios image List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: qemu-devel , Fabien Chouteau , "" , Scott Wood , =?UTF-8?Q?Herv=C3=A9_Poussineau?= , =?UTF-8?Q?Andreas_F=C3=A4rber?= , Artyom Tarasenko On 6 April 2013 12:38, Alexander Graf wrote: > > On 06.04.2013, at 13:27, Peter Maydell wrote: > >> On 6 April 2013 10:07, Alexander Graf wrote: >>> On ARM, look at highbank. Because we're not running we're lacking >>> a monitor mode blob that provides sys calls for flushing caches. >>> Thus today the highbank machine doesn't boot anymore with Linux. >>> If we ran firmware like the real board, that would provide for the >>> sys call. >> >> We also flat out don't implement enough monitor mode to allow >> a hypothetical firmware blob to work. > > Why don't we implement enough monitor mode? Because (a) I haven't got round to it (b) doing it properly is a huge job (c) KVM can't do monitor mode so we need a plan for a "not really monitor mode" anyway (d) it isn't yet causing problems on the boards I primarily care about. I'm happy to review patches if somebody wants to submit them. > Bottom line is that Linux validly expects that firmware exists. I agree that we're going to want to run UEFI at some point. My current plan for this is that we should get a version of the UEFI firmware which runs in non-secure mode. -- PMM