From: Arjan van de Ven <arjan@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: [patch] x86: test case for the RODATA config option
Date: Wed, 23 Jan 2008 08:04:38 -0800 [thread overview]
Message-ID: <20080123080438.490b0c3e@laptopd505.fenrus.org> (raw)
In-Reply-To: <200801231627.28715.andi@firstfloor.org>
On Wed, 23 Jan 2008 16:27:28 +0100
Andi Kleen <andi@firstfloor.org> wrote:
>
> > What it does is check if the rodata marking was succesful.
>
> The only difference I see is that you check that the TLB flush works,
> but for that it looks awfully incomplete.
you think one level too small.
It tests if mark_rodata_ro() operated correctly.
Yes internally that uses c-p-a, but there's more code there, including a set of boundary conditions etc.
And for the page table to work, cr0 needs to be set up correctly etc etc etc.
> Other than it is identical [modulo the kernel mapping bit on 64bit]--
it's a test of mark_rodata_ro(), not of c-p-a. Not the same thing.
> What I meant using the more extensive test in pageattr-test.c
> to test a few changes in the 64bit kernel mapping too, not moving your
> code. I don't think moving your code makes sense. Sorry for being
> unclear.
then I just don't get your comment at all; sorry.
--
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-01-23 16:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 22:44 Arjan van de Ven
2008-01-23 0:04 ` Ingo Molnar
2008-01-23 1:11 ` Nick Piggin
2008-01-23 5:29 ` Arjan van de Ven
2008-01-23 9:09 ` Andi Kleen
2008-01-23 14:49 ` Arjan van de Ven
2008-01-23 15:27 ` Andi Kleen
2008-01-23 16:04 ` Arjan van de Ven [this message]
2008-01-23 16:54 ` Andi Kleen
2008-01-23 17:49 ` Arjan van de Ven
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=20080123080438.490b0c3e@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®