All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maneesh Soni <manesoni@cisco.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: David Daney <david.daney@cavium.com>,
	ananth@in.ibm.com, kamensky@cisco.com,
	linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: [PATCH 0/4] MIPS Kprobes
Date: Tue, 8 Nov 2011 22:33:36 +0530	[thread overview]
Message-ID: <20111108170336.GA16526@cisco.com> (raw)


Hi Ralf,

Here is a set of 4 patches for MIPS kprobes. The first two are addressing 
a couple of baseline issues and the remaining two are the 2nd attempt for
allowing kprobes on jump and branch instructions based on the comments I got
earlier
	https://lkml.org/lkml/2011/10/13/106

1) Fix OOPS in arch_prepare_kprobe for MIPS 
2) Deny probes on ll sc instructions for MIPS
3) Refactoring Branch emulation
4) Support for branch instructions probing (v2)


Thanks
Maneesh

             reply	other threads:[~2011-11-08 17:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08 17:03 Maneesh Soni [this message]
2011-11-08 17:04 ` [PATCH 1/4] MIPS Kprobes: Fix OOPS in arch_prepare_kprobe() Maneesh Soni
2011-11-08 19:57   ` David Daney
2011-11-09  5:26     ` Maneesh Soni
2011-11-17 23:17   ` Ralf Baechle
2011-11-08 17:05 ` [PATCH 2/4] MIPS Kprobes: Deny probes on ll/sc instructions Maneesh Soni
2011-11-08 20:01   ` David Daney
2011-11-08 23:26     ` Victor Kamensky
2011-11-16 12:12       ` Ralf Baechle
2011-11-16 17:39         ` Victor Kamensky
2011-11-17 23:18   ` Ralf Baechle
2011-11-08 17:07 ` [PATCH 3/4] MIPS Kprobes: Refactoring Branch emulation Maneesh Soni
2011-11-17 23:18   ` Ralf Baechle
2011-11-08 17:08 ` [PATCH 4/4] MIPS Kprobes: Support branch instructions probing - v2 Maneesh Soni
2011-11-17 23:18   ` Ralf Baechle

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=20111108170336.GA16526@cisco.com \
    --to=manesoni@cisco.com \
    --cc=ananth@in.ibm.com \
    --cc=david.daney@cavium.com \
    --cc=kamensky@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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.