All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Sealey <matt@genesi-usa.com>
To: ganesh subramonian <gun_raj@yahoo.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Handling machine check exception
Date: Thu, 12 Oct 2006 12:34:05 +0200	[thread overview]
Message-ID: <452E1A1D.1050601@genesi-usa.com> (raw)
In-Reply-To: <20061012045943.9389.qmail@web52403.mail.yahoo.com>

The G2 core definitely has a DAR register (SPR 19).

Look on the Freescale site for G2CORERM.pdf - this is
your reference manual, not the one specifically for the
8247.

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations

ganesh subramonian wrote:
> Hi,
> 
> I am trying to modify the machinecheck exception
> handler so that checks caused by data access to a
> particular address range can be ignored. In mpc866
> there is a register called DAR(Data Address Register)
> which gives the address[access to] which caused the
> exception. However this is not mentioned in the
> MPC8247 manual. Is there some equivalent register for
> 8247. (It seemed to me that the DAR should be a core
> register and hence should be there on 8247 also. but
> if i try to read i really dont get the address causing
> the error).
> 
> Or is there some way i can specify that access to a
> particular range of address should not cause a machine
> check?? Please help.
> 
> thanks
> ganesh
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev

  reply	other threads:[~2006-10-12 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-12  4:59 Handling machine check exception ganesh subramonian
2006-10-12 10:34 ` Matt Sealey [this message]
2006-10-12 14:51   ` Benjamin Herrenschmidt
2006-10-12 20:05     ` Segher Boessenkool
2006-10-14 14:04       ` ganesh subramonian

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=452E1A1D.1050601@genesi-usa.com \
    --to=matt@genesi-usa.com \
    --cc=gun_raj@yahoo.com \
    --cc=linuxppc-dev@ozlabs.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.