From: rsmadhvesh@vsnl.net
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, madhvesh.s@ap.sony.com
Subject: Re: [RFC][PATCH]Kprobes for PPC32(BOOKE)
Date: Mon, 23 Apr 2007 19:36:24 +0500 [thread overview]
Message-ID: <e38e8f4d2093d.462d0ab8@vsnl.net> (raw)
In-Reply-To: <382B116B-1892-441F-9F4D-9E0F3F01FC92@kernel.crashing.org>
Hi Kumar,
Kumar Gala <galak@kernel.crashing.org> wrote on Saturday, April 21, 2007 1:04 am
>
> On Apr 20, 2007, at 2:24 AM, rsmadhvesh@vsnl.net wrote:
>
> > Hi Kumar,
> >
> > This is regarding the kprobes patches for
> > PPC32 BOOKE version. The attached patches
> > contain the implementation for this version.
> >
> > I saw your earlier postings and commits to 2.6.21
> > regarding kprobes for PPC32. Since the single
> > step mechanism in BookE is quite different, I
> > thought i can share some of the issues faced
> > in this implementation and get your review
> > feedback for those patches.
>
> I'd love to review these patches. Is there any possibility that I
> could get you to build them for arch/powerpc on top of David
> Gibson's
> port of ebony to arch/powerpc.
>
> http://ozlabs.org/pipermail/linuxppc-dev/2007-April/034483.html
>
> I dont see much value in adding kprobes into arch/ppc and have been
>
> trying to push any 'new' functionality get added to arch/powerpc
> and
> only bug fixes to arch/ppc.
Thanks for taking interest in reviewing my patches.
I understand the recent discussions in merging ppc to
powerpc and now i can as well start merging my patches
to powerpc. I will repost my patches after this, but if you find
any bugs in my code, please let me know.
-Madhvesh
prev parent reply other threads:[~2007-04-23 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 7:24 [RFC][PATCH]Kprobes for PPC32(BOOKE) rsmadhvesh
2007-04-20 19:33 ` Kumar Gala
2007-04-23 14:36 ` rsmadhvesh [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=e38e8f4d2093d.462d0ab8@vsnl.net \
--to=rsmadhvesh@vsnl.net \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=madhvesh.s@ap.sony.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).