All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Borislav Petkov <bp@alien8.de>, Namhyung Kim <namhyung@gmail.com>
Cc: David Howells <dhowells@redhat.com>,
	mingo@kernel.org, tglx@linutronix.de, davem@davemloft.net,
	torvalds@linux-foundation.org, paulus@samba.org,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org
Subject: Re: [RFC][PATCH 0/5] tools, perf: Fix up for x86 UAPI disintegration
Date: Wed, 24 Oct 2012 11:43:37 -0700	[thread overview]
Message-ID: <20121024184337.GD13993@ghostprotocols.net> (raw)
In-Reply-To: <20121019165558.23037.40181.stgit@warthog.procyon.org.uk>

Em Fri, Oct 19, 2012 at 05:55:58PM +0100, David Howells escreveu:
> 
> Here are some potential fix ups for perf and other tools.  They need to be
> applied on top of the x86 UAPI disintegration patch.

Borislav, Namhyung, can you take a look at this series?

- Arnaldo
 
> There are five patches:
> 
>  (1) Use a makefile $(call ...) function in tools/Makefile to make it easier
>      to deal with.
> 
>      [NOTE!  I think the rule for selftests_install is wrong since it attempts
>       to discard '_clean' from the end of the target name instead of
>       '_install']
> 
>  (2) Fix handling of O= with a relative path when doing something like:
> 
> 	make tools/perf O=foo
> 
>      from the top-level directory in the kernel source tree for all tools.
> 
>  (3) Make perf work for x86 by adding -I flags and changing long #includes
>      with "../../include" in them into short <asm/foo.h> type things.
> 
> Now there are two patches that I'm not sure whether you want.  There are three
> header files with bits used by perf that are not in the UAPI.  If these are
> disintegrated then perf does not need to look in any KAPI headers at all and
> the -I flag pointing there can be dropped after the first of these patches.
> 
>  (4) UAPI disintegrate asm/svm.h and asm/vmx.h.
> 
>  (5) UAPI disintegrate asm/perf_regs.h and convert a "../../include" style
>      path into <asm/perf_regs.h>.
> 
> I'm not sure whether these should be exported to userspace, though this commit:
> 
> 	commit 26bf264e871a4b9a8ac09c21a2b518e7f23830d5
> 	Author: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
> 	Date:   Mon Sep 17 16:31:13 2012 +0800
> 	KVM: x86: Export svm/vmx exit code and vector code to userspace
> 
> suggests that at least the first two should be - though since it didn't modify
> Kbuild, this was not effective.
> 
> I haven't tried building perf for other arches at this time.
> 
> David
> ---
> David Howells (5):
>       x86: UAPI Disintegrate asm/perf_regs.h
>       x86: Disintegrate asm/svm.h and asm/vmx.h to produce UAPI components for perf
>       perf: Make perf build for x86 with UAPI disintegration applied
>       tools: Honour the O= flag when tool build called from a higher Makefile
>       tools: Define a Makefile function to do subdir processing
> 
> 
>  Makefile                                |    6 +
>  arch/x86/include/asm/perf_regs.h        |   33 --------
>  arch/x86/include/asm/svm.h              |  133 -------------------------------
>  arch/x86/include/asm/vmx.h              |   87 --------------------
>  arch/x86/include/uapi/asm/perf_regs.h   |   33 ++++++++
>  arch/x86/include/uapi/asm/svm.h         |  131 +++++++++++++++++++++++++++++++
>  arch/x86/include/uapi/asm/vmx.h         |  108 +++++++++++++++++++++++++
>  tools/Makefile                          |   24 +++---
>  tools/perf/Makefile                     |   15 +++
>  tools/perf/arch/x86/include/perf_regs.h |    2 
>  tools/perf/builtin-kvm.c                |    6 +
>  tools/perf/perf.h                       |   16 +---
>  tools/scripts/Makefile.include          |   18 ++++
>  13 files changed, 329 insertions(+), 283 deletions(-)
>  delete mode 100644 arch/x86/include/asm/perf_regs.h
>  create mode 100644 arch/x86/include/uapi/asm/perf_regs.h
>  create mode 100644 arch/x86/include/uapi/asm/svm.h
>  create mode 100644 arch/x86/include/uapi/asm/vmx.h

  parent reply	other threads:[~2012-10-24 18:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 16:55 [RFC][PATCH 0/5] tools, perf: Fix up for x86 UAPI disintegration David Howells
2012-10-19 16:56 ` [PATCH 1/5] tools: Define a Makefile function to do subdir processing David Howells
2012-10-19 16:56 ` [PATCH 2/5] tools: Honour the O= flag when tool build called from a higher Makefile David Howells
2012-10-26  5:34   ` Namhyung Kim
2012-10-19 16:56 ` [PATCH 3/5] perf: Make perf build for x86 with UAPI disintegration applied David Howells
2012-10-26  5:49   ` Namhyung Kim
2012-10-19 16:56 ` [PATCH 4/5] x86: Disintegrate asm/svm.h and asm/vmx.h to produce UAPI components for perf David Howells
2012-10-19 16:56 ` [PATCH 5/5] x86: UAPI Disintegrate asm/perf_regs.h David Howells
2012-10-24 18:43 ` Arnaldo Carvalho de Melo [this message]
2012-10-24 19:46   ` [RFC][PATCH 0/5] tools, perf: Fix up for x86 UAPI disintegration Borislav Petkov
2012-10-25  7:57     ` David Howells
2012-10-26  4:33       ` Namhyung Kim
2012-10-26  6:04         ` Namhyung Kim

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=20121024184337.GD13993@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=bp@alien8.de \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@gmail.com \
    --cc=paulus@samba.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.