All of lore.kernel.org
 help / color / mirror / Atom feed
From: tixy@yxit.co.uk (Tixy)
To: linux-arm-kernel@lists.infradead.org
Subject: How to handle kprobe bugs?
Date: Wed, 30 Mar 2011 19:34:48 +0100	[thread overview]
Message-ID: <1301510088.2488.184.camel@computer2.home> (raw)
In-Reply-To: <20110330141011.GA2844@arm.com>

On Wed, 2011-03-30 at 15:10 +0100, Dave Martin wrote:
> On Wed, Mar 30, 2011 at 02:53:33PM +0100, Tixy wrote:
> > 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?
> 
> Sure.
> 
> Note that you should emulate all the hinted NOPs as actual NOPs,
> since the event the hint waits for may happen in the meantime;
> under some circumstances that would lead to stalls.

Good point :-) Conversely, things like Send Event shouldn't be actual
NOPs.

-- 
Tixy

  reply	other threads:[~2011-03-30 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 13:53 How to handle kprobe bugs? Tixy
2011-03-30 14:10 ` Dave Martin
2011-03-30 18:34   ` Tixy [this message]
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=1301510088.2488.184.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 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.