linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Etsushi Kato <ekato@ees.hokudai.ac.jp>
Cc: Hollis Blanchard <hollisb@us.ibm.com>,
	Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: local_irq_enable() problem...
Date: Thu, 22 Jan 2004 12:01:03 +1100	[thread overview]
Message-ID: <16399.8399.251173.659871@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <60A99FA3-4BF7-11D8-A780-00039394E428@ees.hokudai.ac.jp>


Etsushi Kato writes:

> Is there any way to check whether exception handling code is working
> correctly?  Register usage in head.S and entry.S seems to be changed
> from 2.4, so perhaps I missed porting some part.

Yes - the main difference is that we now don't save all the registers
on the common interrupt/exception entries.  We only save the volatile
registers, since the C code saves and restores all the nonvolatile
registers.  We do this for external interrupt, decrementer and system
call, at least.  Other exception entries that are likely to result in
sending a signal to the current process save all the registers.

Paul.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-01-22  1:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-20  5:34 local_irq_enable() problem Etsushi Kato
2004-01-20 10:03 ` Geert Uytterhoeven
2004-01-20 13:34   ` Etsushi Kato
2004-01-20 15:55     ` Hollis Blanchard
2004-01-21  9:51       ` Etsushi Kato
2004-01-22  1:01         ` Paul Mackerras [this message]
2004-01-20 13:49   ` Sven Luther

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=16399.8399.251173.659871@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=ekato@ees.hokudai.ac.jp \
    --cc=hollisb@us.ibm.com \
    --cc=linuxppc-dev@lists.linuxppc.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).