From: tixy@yxit.co.uk (Tixy)
To: linux-arm-kernel@lists.infradead.org
Subject: How to handle kprobe bugs?
Date: Wed, 30 Mar 2011 14:53:33 +0100 [thread overview]
Message-ID: <1301493213.2488.41.camel@computer2.home> (raw)
Now that I'm writing some test code for kprobes I'm quickly finding
further bugs with the instruction emulation. E.g. ALU ops with an
immediate operand are broke. Shall I wait until I have completed writing
all test cases before submitting a single fix patch? (It could be a
couple of weeks.)
I also find that instruction emulation for some (all?) ARMv6K and newer
instructions are missing. E.g. hint instructions like NOP and WFI. Shall
I produce a second patch to add these?
At some point I will also get around to doing my original task of adding
Thumb support to kprobes. I'm assuming that fixing ARM code is higher
priority than adding Thumb support?
--
Tixy
next reply other threads:[~2011-03-30 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 13:53 Tixy [this message]
2011-03-30 14:10 ` How to handle kprobe bugs? Dave Martin
2011-03-30 18:34 ` Tixy
2011-03-31 8:54 ` Dave Martin
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=1301493213.2488.41.camel@computer2.home \
--to=tixy@yxit.co.uk \
--cc=linux-arm-kernel@lists.infradead.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 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).