From: Paul Mackerras <paulus@samba.org>
To: "K.Prasad" <prasad@linux.vnet.ibm.com>
Cc: Michael Neuling <mikey@neuling.org>,
Benjamin Herrenschmidt <benh@au1.ibm.com>,
shaggy@linux.vnet.ibm.com,
Frederic Weisbecker <fweisbec@gmail.com>,
David Gibson <dwg@au1.ibm.com>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Alan Stern <stern@rowland.harvard.edu>,
Roland McGrath <roland@redhat.com>
Subject: Re: [Patch 1/2] PPC64-HWBKPT: Disable interrupts for data breakpoint exceptions
Date: Mon, 3 May 2010 15:04:47 +1000 [thread overview]
Message-ID: <20100503050447.GA19365@drongo> (raw)
In-Reply-To: <20100414034809.GB6571@in.ibm.com>
On Wed, Apr 14, 2010 at 09:18:09AM +0530, K.Prasad wrote:
> Data address breakpoint exceptions are currently handled along with page-faults
> which require interrupts to remain in enabled state. Since exception handling
> for data breakpoints aren't pre-empt safe, we handle them separately.
>
> Signed-off-by: K.Prasad <prasad@linux.vnet.ibm.com>
Acked-by: Paul Mackerras <paulus@samba.org>
next prev parent reply other threads:[~2010-05-03 5:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100414033555.746326035@pr>
2010-04-14 3:48 ` [Patch 1/2] PPC64-HWBKPT: Disable interrupts for data breakpoint exceptions K.Prasad
2010-05-03 5:04 ` Paul Mackerras [this message]
2010-04-14 3:48 ` [Patch 2/2] PPC64-HWBKPT: Implement hw-breakpoints for PPC64 K.Prasad
2010-05-03 6:23 ` Paul Mackerras
2010-05-04 20:33 ` K.Prasad
2010-05-12 3:34 ` K.Prasad
2010-05-12 6:32 ` Paul Mackerras
2010-05-14 6:55 ` K.Prasad
2010-05-17 12:32 ` Paul Mackerras
2010-05-20 4:06 ` K.Prasad
2010-05-20 13:10 ` Paul Mackerras
2010-05-24 15:49 ` K.Prasad
[not found] <20100330095040.565675261@pr>
2010-03-30 9:59 ` [Patch 1/2] PPC64-HWBKPT: Disable interrupts for data breakpoint exceptions K.Prasad
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=20100503050447.GA19365@drongo \
--to=paulus@samba.org \
--cc=benh@au1.ibm.com \
--cc=dwg@au1.ibm.com \
--cc=fweisbec@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=roland@redhat.com \
--cc=shaggy@linux.vnet.ibm.com \
--cc=stern@rowland.harvard.edu \
/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.