From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [RFC v2] ARM VM System Specification
Date: Wed, 11 Jun 2014 10:16:03 +0200
Message-ID: <53981043.3010300@redhat.com>
References: <20140328184517.GA27219@cbox> <CAFEAcA-isiLax0UASTMkedwGXWOaBdR7N1t2o87XYDkj5nt5ig@mail.gmail.com> <53973AA8.9020301@codeaurora.org> <CAFEAcA8RttCvbOAw-m-W6C-mh1o4hj6nqGMkDbRsSF6ZoQZ7Kg@mail.gmail.com> <539754E5.3030408@redhat.com> <53975A0A.8090802@redhat.com> <20140611065412.GA24286@lvm>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Christopher Covington <cov@codeaurora.org>,
	"cross-distro@lists.linaro.org" <cross-distro@lists.linaro.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	kvm-devel <kvm@vger.kernel.org>,
	Michael Casadevall <Michael.casadevall@linaro.org>,
	"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
	Rob Herring <rob.herring@linaro.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	Grant Likely <grant.likely@linaro.org>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	arm-mail-list <linux-arm-kernel@lists.infradead.org>
To: Christoffer Dall <christoffer.dall@linaro.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:28448 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755681AbaFKIQp (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 11 Jun 2014 04:16:45 -0400
In-Reply-To: <20140611065412.GA24286@lvm>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Il 11/06/2014 08:54, Christoffer Dall ha scritto:
> The problem is that the most common user problem with ARM VMs are that
> they boot the thing, and then get no output.  So we wanted some way to
> make sure we know that the kernel should be able to print to a console.
>
> UEFI does provide DBG2 output, but that's only during boot time service
> (so I'm told), and we need to mandate something that will work  when
> the kernel boots.

Doh, indeed the console is not part of run-time services (so it's not 
even available for earlyprintk).

> If kernels actually do use the UEFI runtime services and have no need
> for direct access to an RTC when runing in a UEFI compliant system, then
> I agree with not specifying the hardware details.

The RTC is not needed for ordinary operation of the kernel and, in the 
current kernel, the EFI RTC driver is only used for IA64.  However, it 
seems to be platform independent.  I'll give it a shot (on x86, since 
that's the only architecture for which I know how to get UEFI firmware).

Paolo