public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH 2.6.0test5: 2 of 3] MCA/TLB recovery
Date: Wed, 08 Oct 2003 21:44:04 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106564946702005@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106522368223247@msgid-missing>

>   Tony> +/* Bitmasks of implemented registers */
>   Tony> +static u64 arbits[2] = { 0x11117f2f00ffUL, 0x7UL };
>   Tony> +static u64 crbits[2] = { 0x3fb0107UL, 0x307ffUL };
> 
> Shouldn't these masks be obtained from PAL?

You are right ... PAL_REGISTER_INFO returns this information (I
had forgotten that it existed).

>   Tony> +static u64 brbits[1] = { 0xffUL };
>   Tony> +static u64 rrbits[1] = { 0xffUL };
> 
> These look a bit weird to me (since they're architected), but I guess
> it's your call...

This just fell out of sharing the same code to print the register
values ... it might look less weird if I fix the arbits/crbits code
to use PAL_REGISTER_INFO.

Overall this part of the patch is mostly fluff.  Long term the
right thing to do is remove all these printk()s from the kernel
and leave paring of SAL error records to some user mode code (using
some mechanism like Bjorn did in 2.4).

Any comments on parts 1 & 3???

-Tony

  parent reply	other threads:[~2003-10-08 21:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03 23:27 [PATCH 2.6.0test5: 2 of 3] MCA/TLB recovery Luck, Tony
2003-10-08 20:51 ` David Mosberger
2003-10-08 21:44 ` Luck, Tony [this message]
2003-10-08 22:39 ` David Mosberger
2003-10-08 22:45 ` Jesse Barnes
2003-10-08 23:31 ` 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=marc-linux-ia64-106564946702005@msgid-missing \
    --to=tony.luck@intel.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