From: David Howells <dhowells@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: dhowells@redhat.com, Ingo Molnar <mingo.kernel.org@gmail.com>,
hpa@zytor.com, Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] UAPI: Disintegrate arch/x86/include/asm
Date: Sun, 09 Dec 2012 18:02:50 +0000 [thread overview]
Message-ID: <17310.1355076170@warthog.procyon.org.uk> (raw)
In-Reply-To: <20121208144944.GF12011@gmail.com>
Ingo Molnar <mingo@kernel.org> wrote:
> arch/x86/include/asm/Kbuild | 7 ++
> arch/x86/include/asm/perf_regs.h | 33 ---------
> arch/x86/include/asm/svm.h | 132 +---------------------------------
> arch/x86/include/asm/vmx.h | 89 +----------------------
> arch/x86/include/uapi/asm/Kbuild | 3 +
> arch/x86/include/uapi/asm/perf_regs.h | 33 +++++++++
> arch/x86/include/uapi/asm/svm.h | 132 ++++++++++++++++++++++++++++++++++
> arch/x86/include/uapi/asm/vmx.h | 109 ++++++++++++++++++++++++++++
> 8 files changed, 289 insertions(+), 249 deletions(-)
>
> What are these changes - it seems perf and KVM related.
Only in passing. The header files you indicated are marked as being exported
to userspace in Kbuild - therefore they get disintegrated around __KERNEL__
conditionals just like all the other UAPI-relevant headers.
> Is the latest version above 100% bug-free, with no known
> problems whatsoever?
It builds perf for me. No idea if perf works, I've never used it. I waved a
branch including the patch on top of all my perf patches towards Arnaldo and
others, but I don't know if they've tried it.
I've also checked that x86_64 allyesconfig and i386 allmodconfig build and
that an x86_64 kernel built with my test machine's usual config builds and
boots.
So, no known problems.
David
prev parent reply other threads:[~2012-12-09 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 13:40 David Howells
2012-12-08 14:49 ` Ingo Molnar
2012-12-09 18:02 ` David Howells [this message]
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=17310.1355076170@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo.kernel.org@gmail.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
Powered by JetHome