public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Exception handling and recovery
Date: Wed, 13 Mar 2002 13:58:32 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905257@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905250@msgid-missing>

> 
> On Tue, 12 Mar 2002 20:51:13 -0800, 
> David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >>>>>> On Wed, 13 Mar 2002 14:53:31 +1100, Keith Owens <kaos@sgi.com> said:
> >
> >  Keith> Unlike i386, the ia64 exception table code only recovers from
> >  Keith> invalid user space addresses.  kdb can get other faults which
> >  Keith> EX() does not currently allow recovery from.  Is there any
> >  Keith> reason why I should not add exception table handling to
> >  Keith> ia64_fault(), to generalize the fault recovery mechanism?
> >
> >You mean kdb would do get_user() on a bad pointer, which triggers
> >ia64_fault() and then you want to search the exception table in
> >ia64_fault()?  I think it would be ok to do this (in the KDB patch).
> 
> Exactly.  IMHO ia64_fault should always search_exception_table(), even
> if kdb is not installed.  Other architectures use exception tables to
> detect if the hardware supports extra instructions, registers, MSR
> values etc., exception recovery should be general purpose.
> 

I may have missed the context of the question, but on IA64 if kdb 
makes a reference to a bad region 6 or 7 pointer, it may trigger an MCA.
MCAs are not recoverable via search_exception_table(). 



-- 
Thanks

Jack Steiner    (651-683-5302)   (vnet 233-5302)      steiner@sgi.com



  parent reply	other threads:[~2002-03-13 13:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13  3:53 [Linux-ia64] Exception handling and recovery Keith Owens
2002-03-13  4:51 ` David Mosberger
2002-03-13  5:22 ` Keith Owens
2002-03-13  5:32 ` David Mosberger
2002-03-13 13:58 ` Jack Steiner [this message]
2002-03-13 14:08 ` Keith Owens

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=marc-linux-ia64-105590701905257@msgid-missing \
    --to=steiner@sgi.com \
    --cc=linux-ia64@vger.kernel.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