From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: mingo@elte.hu, "Jeremy Fitzhardinge" <jeremy@goop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] x86: corruption check: run the corruption checks from a work queue
Date: Sun, 5 Oct 2008 21:35:57 +0200 [thread overview]
Message-ID: <19f34abd0810051235u7f21da03q324d3d0bbe110075@mail.gmail.com> (raw)
In-Reply-To: <20081005120903.2dc262f4@infradead.org>
On Sun, Oct 5, 2008 at 9:09 PM, Arjan van de Ven <arjan@infradead.org> wrote:
>
> From: Arjan van de Ven <arjan@linux.intel.com>
> Date: Mon, 22 Sep 2008 13:42:15 -0700
> Subject: [PATCH] x86: corruption check: run the corruption checks from a work queue
>
> the periodic corruption checks are better off run from a work queue; there's
> nothing time critical about them and this way the amount of
> interrupt-context work is reduced.
>
> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Hi,
Did you figure out what's causing these corruptions yet?
Can't you do so by simply reserving the memory area in question,
clearing the present bit for those pages, and letting the page fault
handler catch whatever code is accessing it?
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-10-05 19:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 19:07 [PATCH 1/4] x86: corruption-check: fix some style issues Arjan van de Ven
2008-10-05 19:08 ` [PATCH 2/4] x86: corruption check: move the corruption checks into their own file Arjan van de Ven
2008-10-05 19:09 ` [PATCH 3/4] x86: corruption check: run the corruption checks from a work queue Arjan van de Ven
2008-10-05 19:35 ` Vegard Nossum [this message]
2008-10-05 19:09 ` [PATCH 4/4] x86: corruption-check: some post-move cleanups Arjan van de Ven
2008-10-27 17:11 ` [PATCH 1/4] x86: corruption-check: fix some style issues Ingo Molnar
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=19f34abd0810051235u7f21da03q324d3d0bbe110075@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=arjan@infradead.org \
--cc=jeremy@goop.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®