linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: benh@kernel.crashing.org, paulus@samba.org,
	rusty@rustcorp.com.au, ulrich.weigand@de.ibm.com,
	amodra@gmail.com, mikey@neuling.org, mjw@linux.vnet.ibm.com,
	rostedt@goodmis.org, philippe.bergheaud@fr.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org
Subject: [PATCH 0/7] Build ppc64le kernel using ABIv2, supplemental patches
Date: Fri,  4 Apr 2014 17:09:03 +1100	[thread overview]
Message-ID: <1396591750-8203-1-git-send-email-anton@samba.org> (raw)

These patches apply against my last series and fix all known
ABIv2 issues.

To stress the module loader and dynamic ftrace code, I built an
allmodconfig kernel and inserted every module I could. I found a bunch
of bugs in the modules themselves, but in the end I managed to
get quite a few modules to load:

# cat /proc/modules | wc -l
3830

It survived a fair bit of poking (enabling/disabling function tracers
etc).

Anton Blanchard (7):
  powerpc: Add _GLOBAL_TOC for ABIv2 assembly functions exported to
    modules
  powerpc: ftrace_caller, _mcount is exported to modules so needs
    _GLOBAL_TOC()
  powerpc/kprobes: Fix ABIv2 issues with kprobe_lookup_name
  powerpc/modules: Create is_module_trampoline()
  powerpc/modules: Create module_trampoline_target()
  powerpc/ftrace: Use module loader helpers to parse trampolines
  powerpc/ftrace: Fix ABIv2 issues with __ftrace_make_call

 arch/powerpc/include/asm/kprobes.h |   5 +-
 arch/powerpc/include/asm/module.h  |   3 +
 arch/powerpc/include/asm/ppc_asm.h |  12 ++++
 arch/powerpc/kernel/entry_64.S     |   7 +-
 arch/powerpc/kernel/ftrace.c       | 137 +++++++++++--------------------------
 arch/powerpc/kernel/module_64.c    |  80 ++++++++++++++++++++--
 arch/powerpc/lib/copyuser_64.S     |   2 +-
 arch/powerpc/lib/memcpy_64.S       |   2 +-
 8 files changed, 136 insertions(+), 112 deletions(-)

-- 
1.8.3.2

             reply	other threads:[~2014-04-04  6:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04  6:09 Anton Blanchard [this message]
2014-04-04  6:09 ` [PATCH 1/7] powerpc: Add _GLOBAL_TOC for ABIv2 assembly functions exported to modules Anton Blanchard
2014-04-04  6:09 ` [PATCH 2/7] powerpc: ftrace_caller, _mcount is exported to modules so needs _GLOBAL_TOC() Anton Blanchard
2014-04-04  6:09 ` [PATCH 3/7] powerpc/kprobes: Fix ABIv2 issues with kprobe_lookup_name Anton Blanchard
2014-04-04  6:09 ` [PATCH 4/7] powerpc/modules: Create is_module_trampoline() Anton Blanchard
2014-04-04  6:09 ` [PATCH 5/7] powerpc/modules: Create module_trampoline_target() Anton Blanchard
2014-04-04  6:09 ` [PATCH 6/7] powerpc/ftrace: Use module loader helpers to parse trampolines Anton Blanchard
2014-04-22  6:58   ` Rusty Russell
2014-04-04  6:09 ` [PATCH 7/7] powerpc/ftrace: Fix ABIv2 issues with __ftrace_make_call Anton Blanchard
2014-04-04  6:19 ` [PATCH 0/7] Build ppc64le kernel using ABIv2, supplemental patches Michael Neuling

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=1396591750-8203-1-git-send-email-anton@samba.org \
    --to=anton@samba.org \
    --cc=amodra@gmail.com \
    --cc=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=mjw@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=philippe.bergheaud@fr.ibm.com \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    --cc=ulrich.weigand@de.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).