From: Ray Bryant <raybry@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] size of spinlock_t
Date: Fri, 15 Feb 2002 15:47:08 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905110@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905101@msgid-missing>
Yes that was it. Thanks. I am totally amazed that "make clean; make
vmlinux" did not remake offsets.h.
David Mosberger wrote:
>
> >>>>> On Fri, 15 Feb 2002 00:14:55 -0600, Ray Bryant <raybry@engr.sgi.com> said:
>
> Ray> In experimenting with new numa lock implementation, I changed
> Ray> the size of spinlock_t to 16 bytes. The resulting kernel hangs
> Ray> on our SN hardware just after printing "All processors have
> Ray> done init_idle". Now it is possible this is something peculiar
> Ray> to the SGI kernels, but I was wondering if anyone knew of
> Ray> places in the IA64 kernel that "know" that
> Ray> sizeof(spinlock_t)=8 and don't work correctly if this is
> Ray> changed.
>
> Are you sure it's not just include/asm/offsets.h that's out of date?
> Make sure you have no stray arch/ia64/tools/print_offsets.s file and
> then rerun make dep.
>
> --david
>
> _______________________________________________
> Linux-IA64 mailing list
> Linux-IA64@linuxia64.org
> http://lists.linuxia64.org/lists/listinfo/linux-ia64
--
Best Regards,
Ray
-----------------------------------------------
Ray Bryant SGI
512-453-9679 (work) 512-507-7807 (cell)
raybry@sgi.com raybry@austin.rr.com
Computers are like air conditioners.
They stop working when you open Windows.
-----------------------------------------------
prev parent reply other threads:[~2002-02-15 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-15 6:14 [Linux-ia64] size of spinlock_t Ray Bryant
2002-02-15 6:24 ` David Mosberger
2002-02-15 15:47 ` Ray Bryant [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=marc-linux-ia64-105590701905110@msgid-missing \
--to=raybry@engr.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 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.