[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <6201AAAD-F575-4D2C-9A97-3EB41DA3491C@suse.de>
Date: Thu, 11 Oct 2012 15:04:58 +0200
From: Alexander Graf <agraf@...e.de>
To: Tabi Timur-B04825 <B04825@...escale.com>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Yoder Stuart-B08248 <B08248@...escale.com>,
David Howells <dhowells@...hat.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
Paul Mackerras <paulus@...ba.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree
On 11.10.2012, at 05:32, Tabi Timur-B04825 wrote:
> On Wed, Oct 10, 2012 at 9:47 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
>> Commit 549d62d889b4 ("KVM: PPC: use definitions in epapr header
>> for hcalls") from the kvm-ppc tree added an include of asm/epapr_hcall.h
>> to the user visible part of asm/kvm_para.h so asm/epapr_hcall.h became a
>> user visible header file.
>
> Any real user-space code that tries to call any of the functions in
> epapr_hcall.h will cause an exception.
>
> Claiming that kernel header files that KVM needs are suddenly
> user-space header files doesn't make much sense to me, but I guess
> it's not my decision.
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.
Alex
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists