Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752370Ab2JKPzw (ORCPT ); Thu, 11 Oct 2012 11:55:52 -0400 Received: from tx2ehsobe005.messaging.microsoft.com ([65.55.88.15]:2885 "EHLO tx2outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751160Ab2JKPzr (ORCPT ); Thu, 11 Oct 2012 11:55:47 -0400 X-Forefront-Antispam-Report: CIP:70.37.183.190;KIP:(null);UIP:(null);IPV:NLI;H:mail.freescale.net;RD:none;EFVD:NLI X-SpamScore: 2 X-BigFish: VS2(zz98dIzz1202h1d1ah1d2ah1082kzzz2dh2a8h668h839hd25he5bhf0ah107ah1288h12a5h12a9h12bdh137ah13b6h1441h1155h) Message-ID: <5076EBFE.5060208@freescale.com> Date: Thu, 11 Oct 2012 10:55:42 -0500 From: Timur Tabi Organization: Freescale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120312 Firefox/11.0 SeaMonkey/2.8 MIME-Version: 1.0 To: Alexander Graf CC: Stephen Rothwell , "linux-kernel@vger.kernel.org" , Yoder Stuart-B08248 , David Howells , "linux-next@vger.kernel.org" , Paul Mackerras , "linuxppc-dev@lists.ozlabs.org" Subject: Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree References: <20121011121841.1b946f996cba995d9a5a2be7@canb.auug.org.au> <6AE080B68D46FC4BA2D2769E68D765B7080FA8F8@039-SN2MPN1-023.039d.mgd.msft.net> <20121011134754.2e2cbb24842fa991e61cf97c@canb.auug.org.au> <6AE080B68D46FC4BA2D2769E68D765B7080FA9F8@039-SN2MPN1-023.039d.mgd.msft.net> <6201AAAD-F575-4D2C-9A97-3EB41DA3491C@suse.de> In-Reply-To: <6201AAAD-F575-4D2C-9A97-3EB41DA3491C@suse.de> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-OriginatorOrg: freescale.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 845 Lines: 24 Alexander Graf wrote: > This is about kvm_host.h, which is the part that is exported to user > space. It usually contains constants and structs that are required for > the API. Which API? I'm not familiar with KVM internals. My concern is that when I think of a user-space header file, I think of a user-space application that calls ioctls. I know that KVM guest kernels run as user-space processes, but that does not seem like a reason to combine all of the header files that the KVM guest kernel needs with "real" user-space header files. -- Timur Tabi Linux kernel developer at Freescale -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/