From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] Memory Error Handling Improvement
Date: Thu, 23 Jun 2005 22:18:53 +0000 [thread overview]
Message-ID: <17083.13645.585589.85631@napali.hpl.hp.com> (raw)
In-Reply-To: <200506231730.j5NHUNa96698484@clink.americas.sgi.com>
>>>>> On Thu, 23 Jun 2005 14:30:20 -0500 (CDT), Russ Anderson <rja@sgi.com> said:
Russ> David Mosberger wrote:
>>
Russ> -ENTRY(interrupt) +GLOBAL_ENTRY(interrupt)
>> Please don't create such name-space pollution.
>> AFAICS, you should be able to use ia64_ivt and the architected
>> offset for the external-interrupt handler instead.
Russ> I assume you mean usage like in
Russ> arch/ia64/oprofile/backtrace.c, so the usage in mca_drv.c
Russ> would be along the lines of:
Russ> extern char ia64_ivt[];
Russ> if (psr1->cpl != 0 || (pmsa->pmsa_iip >= (unsigned
Russ> long)ia64_ivt+0x3000 &&
Russ> Do you have the same objection for interrupt_pnr? If so, what
Russ> is the best way to calculate the offset in ivt.S (which looks
Russ> hardcoded for other routines)?
I thought interrupt_pnr was at the end of the vector. Now that I look
closer, the whole thing looks rather doubious/fragile to me. What
exactly are you trying to do there?
--david
next prev parent reply other threads:[~2005-06-23 22:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 17:30 [patch] Memory Error Handling Improvement Russ Anderson
2005-06-23 17:52 ` David Mosberger
2005-06-23 19:30 ` Russ Anderson
2005-06-23 22:11 ` Andreas Schwab
2005-06-23 22:18 ` David Mosberger [this message]
2005-06-23 22:22 ` Russ Anderson
2005-06-23 22:54 ` Andreas Schwab
2005-06-24 1:12 ` Hidetoshi Seto
2005-06-24 20:11 ` Russ Anderson
2005-06-24 20:18 ` Russ Anderson
2005-06-24 20:36 ` David Mosberger
2005-06-24 21:05 ` Luck, Tony
2005-06-24 21:11 ` David Mosberger
2005-06-24 21:20 ` Luck, Tony
2005-06-24 21:25 ` David Mosberger
2005-06-24 21:31 ` Luck, Tony
2005-06-24 21:36 ` Russ Anderson
2005-06-24 21:36 ` David Mosberger
2005-06-24 21:53 ` David Mosberger
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=17083.13645.585589.85631@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.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