From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55467) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sqg5v-0007zs-Go for qemu-devel@nongnu.org; Mon, 16 Jul 2012 03:51:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sqg5p-0007a1-QX for qemu-devel@nongnu.org; Mon, 16 Jul 2012 03:51:51 -0400 Received: from ozlabs.org ([203.10.76.45]:58159) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sqg5p-0007ZP-F0 for qemu-devel@nongnu.org; Mon, 16 Jul 2012 03:51:45 -0400 From: Rusty Russell In-Reply-To: References: <878veoz5yv.fsf@rustcorp.com.au> Date: Mon, 16 Jul 2012 16:52:36 +0930 Message-ID: <87mx30xj9f.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: [Qemu-devel] [PATCH] target-arm: kvm: use KVM_SET_SREGS to set target to Cortex A15 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , Rusty Russell Cc: kvmarm@lists.cs.columbia.edu, qemu-devel@nongnu.org On Fri, 13 Jul 2012 09:06:16 +0100, Peter Maydell wrote: > On 13 July 2012 04:37, Rusty Russell wrote: > > Recent kernels use this to set the cpu and features (currently, only > > the A15 is supported). > > > > Note that this causes the registers in the CPU to be initialized, so > > it's important that all CPUs are created first (they are, as it turns > > out). > > > > This code ignores errors, for backwards compatibility with older > > kernels. > > > > Signed-off-by: Rusty Russell > > I haven't actually been posting the ARM KVM patches to qemu-devel > thus far, so this patch is a bit of a non-sequitur for qemu-devel readers. > (We've been posting patches to kvmarm only, like the kernel patches.) OK; given the wider API implications I thought I'd add them. > Anyway: > * updates to qemu's kernel headers should be separate patches > and ideally the result of running the automatic 'update headers' > script. [I'm going to squash all the kernel header changes together > before we submit a patch series properly to qemu-devel, so patches > which combine header and code changes require me to untangle them] OK. This is totally a hack until we know how we're going to transition. > * any code which includes compatibility workarounds for earlier > versions of in-development kernel code should have a FIXME comment > so we can remember to undo the workaround before submitting. Sure. It's up to you whether you want a flag day: tell me and I'll re-spin the patches? Thanks, Rusty.