From: Alexander Graf <agraf@suse•de>
To: Tabi Timur-B04825 <B04825@freescale•com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Yoder Stuart-B08248 <B08248@freescale•com>,
David Howells <dhowells@redhat•com>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
Paul Mackerras <paulus@samba•org>,
"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>
Subject: Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree
Date: Thu, 11 Oct 2012 15:04:58 +0200 [thread overview]
Message-ID: <6201AAAD-F575-4D2C-9A97-3EB41DA3491C@suse.de> (raw)
In-Reply-To: <6AE080B68D46FC4BA2D2769E68D765B7080FA9F8@039-SN2MPN1-023.039d.mgd.msft.net>
On 11.10.2012, at 05:32, Tabi Timur-B04825 wrote:
> On Wed, Oct 10, 2012 at 9:47 PM, Stephen Rothwell <sfr@canb•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
next prev parent reply other threads:[~2012-10-11 13:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 1:18 linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree Stephen Rothwell
2012-10-11 1:47 ` Tabi Timur-B04825
2012-10-11 2:47 ` Stephen Rothwell
2012-10-11 3:32 ` Tabi Timur-B04825
2012-10-11 13:04 ` Alexander Graf [this message]
2012-10-11 15:50 ` Scott Wood
2012-10-11 15:56 ` Alexander Graf
2012-10-11 16:33 ` Scott Wood
2012-10-11 15:55 ` Timur Tabi
2012-10-11 16:37 ` Scott Wood
2012-10-11 17:24 ` Timur Tabi
2012-10-11 17:28 ` Scott Wood
2012-10-11 17:30 ` Timur Tabi
2012-10-11 9:28 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2012-10-11 1:05 Stephen Rothwell
2012-10-11 9:27 ` David Howells
2012-10-11 13:08 ` Alexander Graf
2012-10-11 16:05 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6201AAAD-F575-4D2C-9A97-3EB41DA3491C@suse.de \
--to=agraf@suse$(echo .)de \
--cc=B04825@freescale$(echo .)com \
--cc=B08248@freescale$(echo .)com \
--cc=dhowells@redhat$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox