archive mirror
 help / color / mirror / Atom feed
From: Chuck Ebbert <>
To: William Lee Irwin III <>
Cc: linux-kernel <>
Subject: Re: [ANNOUNCE] desc.c -- dump the i386 descriptor tables
Date: Thu, 24 Apr 2003 05:06:58 -0400	[thread overview]
Message-ID: <> (raw)

wli wrote:

> Spiffy; this should help debug various things.

  I forgot to mention: try comparing 2.2, 2.4 and 2.5.

  Also, this is what I've been using to look at interrupt entry
point alignment.  On 2.4 for sure, and probably on 2.5 you have
a 1-in-8 chance of getting a pathologically badly aligned timer
handler on 32-byte cacheline machines every time you compile
(IRQ 0 entry address & 0x1f == 0x1c.)  OTOH the pagefault handler
has come up 8-byte aligned every time but I didn't look at the
source to see if it's coded that way.


             reply	other threads:[~2003-04-24  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24  9:06 Chuck Ebbert [this message]
2003-04-24  9:12 ` [ANNOUNCE] desc.c -- dump the i386 descriptor tables William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2003-04-24 13:59 Chuck Ebbert
2003-04-24 16:25 ` Gabriel Paubert
2003-04-24  3:02 Chuck Ebbert
2003-04-24  3:11 ` William Lee Irwin III
2003-04-24  8:53 ` Gabriel Paubert

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).