mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andi Kleen <ak@suse.de>, Dave <dave.jiang@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: x86_64 segfault error codes
Date: Thu, 15 Dec 2005 10:59:49 +0100	[thread overview]
Message-ID: <20051215095949.GZ23384@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0512150949570.6445@goblin.wat.veritas.com>

On Thu, Dec 15, 2005 at 09:55:40AM +0000, Hugh Dickins wrote:
> On Wed, 14 Dec 2005, Andi Kleen wrote:
> > 
> > Don't know what kernel you're looking at, but 2.6.15rc5 has
> > 
> >  *      bit 0 == 0 means no page found, 1 means protection fault
> >  *      bit 1 == 0 means read, 1 means write
> >  *      bit 2 == 0 means kernel, 1 means user-mode
> >  *      bit 3 == 1 means use of reserved bit detected
> >  *      bit 4 == 1 means fault was an instruction fetch
> 
> I can't see it there in 2.6.15-rc5 or 2.6.15-rc5-git; but it is there
> in 2.6.15-rc5-mm3: which seems to contains a lot of x86_64 patches,
> perhaps some of which you're expecting already to be in 2.6.15?

Yah it's only in the 2.6.16 queue. Sorry for the confusion.

Anyways nobody should rely on these comments. If you want the details
look at the architecture manuals.

-Andi

  reply	other threads:[~2005-12-15  9:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 18:17 Dave
2005-12-14 18:31 ` Andi Kleen
2005-12-14 19:24   ` Dave
2005-12-14 19:58     ` Andi Kleen
2005-12-14 20:09       ` Dave
2005-12-15  9:55       ` Hugh Dickins
2005-12-15  9:59         ` Andi Kleen [this message]
2005-12-15 14:49         ` Andi Kleen

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=20051215095949.GZ23384@wotan.suse.de \
    --to=ak@suse.de \
    --cc=dave.jiang@gmail.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®