Re: [Qemu-devel] KVM call for 2017-03-14

From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>,
	QEMU Developer <qemu-devel@nongnu.org>,
	KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] KVM call for 2017-03-14
Date: Tue, 14 Mar 2017 11:32:34 +0100	[thread overview]
Message-ID: <CAFEAcA8MW1cWDu6bOXC-CeKD-hPo3eiZ4Kpc-_==fdoM=QKXUw@mail.gmail.com> (raw)
In-Reply-To: <6559d50e-b8d5-eaa2-4a14-48608644ad29@redhat.com>

On 14 March 2017 at 10:24, Thomas Huth <thuth@redhat.com> wrote:
> On 13.03.2017 11:02, Peter Maydell wrote:
>> Are we trying to be:
>>     . a dev platform before easy h/w availability?
>>       [not easy for QEMU for several reasons]
>
> What reasons exactly do you mean here?

The main ones I had in mind are:
 * to do this you need really to have access to the specs for
   new hardware features early. If you wait for publication
   of official specs to start implementation then you won't
   be done until most of the "window" before h/w is available
   has already closed
 * you need to actually implement new features, which requires
   more work than we're currently putting in -- for instance
   for ARM we still haven't finished implementing virtualization
   emulation, and we haven't even started with v8.1 features yet
 * you need to do better testing than just "does it boot
   Linux?" if you're trying to provide a dev platform for
   people to use for developing Linux...

thanks
-- PMM