public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Incorrect definition of pal cache_check info
Date: Wed, 05 Nov 2003 06:34:19 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106801411302949@msgid-missing> (raw)

Both 2.4 and 2.6 kernels define struct pal_cache_check_info_s as

typedef struct pal_cache_check_info_s {
   u64	reserved1       : 16,
	way             : 5,    /* Way in which the
				 * error occurred
				 */
	reserved2       : 1,
	mc              : 1,    /* Machine check corrected */
	tv              : 1,    /* Target address
				 * structure is valid
				 */

	wv              : 1,    /* Way field valid */
	op              : 3,    /* Type of cache
				 * operation that
				 * caused the machine
				 * check.
				 */

	dl              : 1,    /* Failure in data part
				 * of cache line
				 */
	tl              : 1,    /* Failure in tag part
				 * of cache line
				 */
	dc              : 1,    /* Failure in dcache */
	ic              : 1,    /* Failure in icache */
	index           : 24,   /* Cache line index */
	mv              : 1,    /* mesi valid */
	mesi            : 3,    /* Cache line state */
	level           : 4;    /* Cache level */
} pal_cache_check_info_t;

which bears very little resemblance to the Cache_Check layout described
in Intel Itanium Architecture Software Developer's Manual Volume 2:
System Architecture, under PAL_MC_ERROR_INFO.  It looks like struct
pal_tlb_check_info_s is wrong as well.  What gives?


             reply	other threads:[~2003-11-05  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05  6:34 Keith Owens [this message]
2003-11-05 13:13 ` Incorrect definition of pal cache_check info 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=marc-linux-ia64-106801411302949@msgid-missing \
    --to=kaos@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