From: Russ Anderson <rja@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch] per cpu MCA/INIT save areas (take 2)
Date: Fri, 03 Dec 2004 21:33:45 +0000 [thread overview]
Message-ID: <200412032133.iB3LXj81161506@ben.americas.sgi.com> (raw)
In-Reply-To: <200411122327.iACNRR5h131335@ben.americas.sgi.com>
Tony Luck wrote:
>
> Nit: Patch needs to be applied with "patch -p2" ... rather
> than the preferred "patch -p1".
Sorry. My new work area has the quilt patches directory at the
right level.
> The initialization of ar.k3 is quite messy, but when I tried
> to fix it I saw why. I thought that I could just initialize
> it at the top of ia64_mmu_init() ... but that doesn't work because
> you use it in efi_map_pal_code(), which is called long before
> ia64_mmu_init().
That is the "fun" of the early init code. :-)
> Your patch initializes it for non-boot cpus in discontig.c, which
> doesn't work for me because I have CONFIG_DISCONTIGMEM=n ... so
> all my non-boot cpus die on a bad dereference in efi_map_pal_code().
I was afraid that non-discontig may have problems. I'll take that
into account.
> We either need to
> 1) add a contig.c equivalent initialization
> or
> 2) do something different in efi_map_pal_code() where we want to
> save the TR_PALCODE data in per-cpu space.
>
> I'd prefer '2' because then we can make the ar.k3 initialization
> symmetric across boot and non-boot cpus ... but that leaves the
> problem of where to stash the TR_PALCODE information :-(
One alternative would be to have a stripped down version of
efi_map_pal_code() that is called later to get the pal_base
and pal_paddr. That would avoid having to stash the values.
--
Russ Anderson, OS RAS/Partitioning Project Lead
SGI - Silicon Graphics Inc rja@sgi.com
next prev parent reply other threads:[~2004-12-03 21:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-12 23:27 [patch] per cpu MCA/INIT save areas (take 2) Russ Anderson
2004-11-13 7:05 ` David Mosberger
2004-11-13 23:24 ` Russ Anderson
2004-11-14 0:07 ` Jack Steiner
2004-11-14 20:07 ` Luck, Tony
2004-11-15 19:13 ` David Mosberger
2004-11-17 17:47 ` Russ Anderson
2004-11-17 18:59 ` Luck, Tony
2004-11-18 21:36 ` Russ Anderson
2004-11-18 22:18 ` Luck, Tony
2004-11-18 22:56 ` Russ Anderson
2004-11-23 23:36 ` Russ Anderson
2004-11-24 2:41 ` Keith Owens
2004-11-24 23:32 ` Luck, Tony
2004-12-03 21:33 ` Russ Anderson [this message]
2004-12-09 4:15 ` Russ Anderson
2004-12-09 4:35 ` 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=200412032133.iB3LXj81161506@ben.americas.sgi.com \
--to=rja@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