Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: hw_breakpoint: don't fault when debug is not powered
Date: Wed, 9 Nov 2011 13:42:21 +0000	[thread overview]
Message-ID: <20111109134220.GE5825@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1320843602-12278-1-git-send-email-linus.walleij@stericsson.com>

Hi Linus,

On Wed, Nov 09, 2011 at 01:00:02PM +0000, Linus Walleij wrote:
> From: Rabin Vincent <rabin.vincent@stericsson.com>
> 
> If the debug logic is not powered, the processor can unfortunately
> raise an undefined instruction exception on the instruction that
> we use to check if the debug logic is powered up or not.
> 
> Handle this with an undef hook, so that the kernel doesn't crash
> on boot on such setups.

Actually, I've done exactly this already! It got merged in the recent merge
window, so please take it for a spin.

Will

      parent reply	other threads:[~2011-11-09 13:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 13:00 [PATCH] ARM: hw_breakpoint: don't fault when debug is not powered Linus Walleij
2011-11-09 13:38 ` Jon Medhurst (Tixy)
2011-11-09 13:42 ` Will Deacon [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=20111109134220.GE5825@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --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