From: Arjan van de Ven <arjan@infradead.org>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@tglx.de, hpa@zytor.com
Subject: Re: [patch] x86: add code to dump the (kernel) page tables for visual inspection
Date: Tue, 5 Feb 2008 13:50:30 -0800 [thread overview]
Message-ID: <20080205135030.30ea97a9@laptopd505.fenrus.org> (raw)
In-Reply-To: <47A8CB3C.1090101@cosmosbay.com>
On Tue, 05 Feb 2008 21:46:52 +0100
Eric Dumazet <dada1@cosmosbay.com> wrote:
> Arjan van de Ven a écrit :
> > Subject: x86: add code to dump the (kernel) page tables for visual
> > inspection by kernel developers From: Arjan van de Ven
> > <arjan@linux.intel.com>
> >
> > This patch adds code to the kernel to have an (optional)
> > /proc/kernel_page_tables debug file that basically dumps the kernel
> > pagetables; this allows us kernel developers to verify that nothing
> > fishy is going on and that the various mappings are set up
> > correctly. This was quite useful in finding various
> > change_page_attr() bugs, and is very likely to be useful in the
> > future as well.
> >
>
> Seems nice Arjan, but could we also add NUMA information ?
>
ok maybe I'm missing something, but the kernel VA space currently
is totally not numa dependent in any shape or form...
so can you explain what kind of information you're looking for?
(I guess I just don't really understand your request; can you expand a bit on it?)
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-02-05 21:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 6:26 Arjan van de Ven
2008-02-05 20:46 ` Eric Dumazet
2008-02-05 21:50 ` Arjan van de Ven [this message]
2008-02-09 13:18 ` Pavel Machek
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=20080205135030.30ea97a9@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=dada1@cosmosbay.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@tglx.de \
/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®