From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755499Ab2GaGXK (ORCPT ); Tue, 31 Jul 2012 02:23:10 -0400 Received: from mail-wg0-f44.google.com ([74.125.82.44]:51612 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752014Ab2GaGXI (ORCPT ); Tue, 31 Jul 2012 02:23:08 -0400 Date: Tue, 31 Jul 2012 09:22:57 +0300 (EEST) From: Pekka Enberg X-X-Sender: penberg@tux.localdomain To: Michael Ellerman cc: Matt Evans , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org, prerna@linux.vnet.ibm.com, David Gibson , Sasha Levin , Asias He , Cyrill Gorcunov , Ingo Molnar Subject: Re: [RFC/PATCH] Use kernel supplied MMU info for kvm tool In-Reply-To: <1342577283.25827.8.camel@concordia> Message-ID: References: <1342501220-10209-1-git-send-email-michael@ellerman.id.au> <3e2231e9bf466549d1f9b12359f2f8f6@ozlabs.org> <1342577283.25827.8.camel@concordia> User-Agent: Alpine 2.02 (LFD 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 18 Jul 2012, Michael Ellerman wrote: > It occurred to me overnight that I forgot to mention that in order to > build the new code you need the headers from a 3.5-rc1 era kernel (for > the ioctl & KVM_CAP definitions). > > The easiest way to do that is to merge linus' tree into kvmtool. > > Are you planning on doing that in the master kvmtool tree anytime soon? > It's still based on 3.4-rc1 it seems. Done. Sorry for the delay!