From: david mosberger <dmosberger@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: testing mca/init patch
Date: Thu, 01 Sep 2005 19:35:21 +0000 [thread overview]
Message-ID: <ed5aea43050901123563b10726@mail.gmail.com> (raw)
In-Reply-To: <200508312343.j7VNhFOZ012157@agluck-lia64.sc.intel.com>
Keith,
On 8/31/05, Keith Owens <kaos@sgi.com> wrote:
> On Wed, 31 Aug 2005 21:58:58 -0700,
> david mosberger <dmosberger@gmail.com> wrote:
> >- In several places there are checks of the form:
> >
> >+ if ((r12 & -KERNEL_STACK_SIZE) != r13) {
> >
> > I don't understand why you're doing this. You should check for (r12
> >- r13) < KERNEL_STACK_SIZE. That does the same without relying on
> >alignments (which is something we have been careful to avoid in all
> >other ia64 code). This should also let you drop the patch to
> >vmlinux.lds.S.
>
> Paranoia. I have seen several MCA/INIT events fail because they were
> delivered while the cpu was in PAL/SAL. r12 and r13 are preserved
> around calls to PAL/SAL, but they are not preserved _within_ PAL/SAL.
> I am trying to verify as much as possible of the original stack before
> updating it, the alignment check is something useful that I can test
> for.
I'm not suggesting to get rid of the test completely, I suggesting to
replace it with a range check of the form:
(r12 - r13) < KERNEL_STACK_SIZE
that should be about as tight a check as the original without making
alignment-assumptions.
--david
--
Mosberger Consulting LLC, voice/fax: 510-744-9372,
http://www.mosberger-consulting.com/
35706 Runckel Lane, Fremont, CA 94536
prev parent reply other threads:[~2005-09-01 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 23:43 testing mca/init patch tony.luck
2005-09-01 1:38 ` david mosberger
2005-09-01 3:20 ` Keith Owens
2005-09-01 4:58 ` david mosberger
2005-09-01 5:30 ` Keith Owens
2005-09-01 16:43 ` Luck, Tony
2005-09-01 19:35 ` david mosberger [this message]
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=ed5aea43050901123563b10726@mail.gmail.com \
--to=dmosberger@gmail.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 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.