public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Oskar Andero <oskar.andero@sonymobile.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"masami.hiramatsu.pt@hitachi.com"
	<masami.hiramatsu.pt@hitachi.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"anil.s.keshavamurthy@intel.com" <anil.s.keshavamurthy@intel.com>,
	"ananth@in.ibm.com" <ananth@in.ibm.com>,
	"Lekanovic, Radovan" <Radovan.Lekanovic@sonymobile.com>,
	"Davidsson, Björn" <Bjorn.Davidsson@sonymobile.com>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH 0/4] kprobes: split blacklist into common and arch
Date: Thu, 4 Apr 2013 13:41:29 +0200	[thread overview]
Message-ID: <20130404114129.GC2481@caracas.corpusers.net> (raw)
In-Reply-To: <515D64C6.9050903@synopsys.com>

On 13:32 Thu 04 Apr     , Vineet Gupta wrote:
> Hi Oskar,
> 
> On 04/03/2013 01:58 PM, oskar.andero@sonymobile.com wrote:
> > Hi,
> > 
> > This is a slight rework of the following patches which I posted earlier:
> > [PATCH] Kprobes blacklist: Conditionally add x86-specific symbols
> > [PATCH] delay blacklist symbol lookup until we actually need it
> > 
> > This serie includes a patch that moves the architecture dependent black points
> > to the arch/ directory and the x86 patch was modified to follow that patch.
> > 
> > -Oskar
> > 
> > Björn Davidsson (1):
> >   kprobes: move x86-specific blacklist symbols to arch directory
> > 
> > Oskar Andero (2):
> >   kprobes: split blacklist into common and arch
> >   kprobes: replace printk with pr_-functions
> > 
> > Toby Collett (1):
> >   kprobes: delay blacklist symbol lookup until we actually need it
> > 
> >  arch/arc/kernel/kprobes.c      |   3 +
> >  arch/arm/kernel/kprobes.c      |   2 +
> >  arch/avr32/kernel/kprobes.c    |   3 +
> >  arch/ia64/kernel/kprobes.c     |   3 +
> >  arch/mips/kernel/kprobes.c     |   3 +
> >  arch/mn10300/kernel/kprobes.c  |   2 +
> >  arch/powerpc/kernel/kprobes.c  |   3 +
> >  arch/s390/kernel/kprobes.c     |   3 +
> >  arch/sh/kernel/kprobes.c       |   3 +
> >  arch/sparc/kernel/kprobes.c    |   3 +
> >  arch/x86/kernel/kprobes/core.c |   7 ++
> >  kernel/kprobes.c               | 149 ++++++++++++++++++++++++++---------------
> >  12 files changed, 130 insertions(+), 54 deletions(-)
> > 
> 
> For any arch changes, however trivial they might be, you need to CC the respective
> maintainers, or atleast post the patches on linux-arch so we know what's going on !

Thanks Vineet! I will make sure to add linux-arch on CC for version 2.

-Oskar

  reply	other threads:[~2013-04-04 11:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1364977734-32267-1-git-send-email-oskar.andero@sonymobile.com>
2013-04-04 11:32 ` [PATCH 0/4] kprobes: split blacklist into common and arch Vineet Gupta
2013-04-04 11:41   ` Oskar Andero [this message]
2013-04-04 11:41     ` Oskar Andero

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=20130404114129.GC2481@caracas.corpusers.net \
    --to=oskar.andero@sonymobile.com \
    --cc=Bjorn.Davidsson@sonymobile.com \
    --cc=Radovan.Lekanovic@sonymobile.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=ananth@in.ibm.com \
    --cc=anil.s.keshavamurthy@intel.com \
    --cc=davem@davemloft.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.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