From: Paul Mackerras <paulus@samba.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH/RFC] Change the program check exception from EXC_XFER_STD to EXC_XFER_EE.
Date: Thu, 7 Dec 2006 09:09:38 +1100 [thread overview]
Message-ID: <17783.16290.783728.708434@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20061206215042.GA13675@ld0162-tx32.am.freescale.net>
Scott Wood writes:
> Is there any reason why ProgramCheck needs to be EXC_XFER_STD?
Yes. It used to be EXC_XFER_EE, but I changed it to EXC_XFER_STD
because I didn't want the possibility of preemption on the way from a
kernel breakpoint into a kernel debugger (xmon/kgdb/etc.).
I think the solution to your problem is to rearrange
program_check_exception a little, to make sure we do the
local_irq_enable before calling do_mathemu (but still after the
debugger_bpt call).
Paul.
next prev parent reply other threads:[~2006-12-06 22:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 21:50 [PATCH/RFC] Change the program check exception from EXC_XFER_STD to EXC_XFER_EE Scott Wood
2006-12-06 21:59 ` Kumar Gala
2006-12-06 22:09 ` Paul Mackerras [this message]
2006-12-06 22:15 ` Kumar Gala
2006-12-08 4:26 ` Paul Mackerras
2006-12-08 8:07 ` Kumar Gala
2007-01-26 6:48 ` Kumar Gala
2007-01-26 19:49 ` Kumar Gala
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=17783.16290.783728.708434@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).