From: Scott Wood <scottwood@freescale.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, Nathan Lynch <ntl@pobox.com>
Subject: Re: Kernel oops while dumping user core.
Date: Mon, 04 Feb 2008 12:23:31 -0600 [thread overview]
Message-ID: <47A75823.5050001@freescale.com> (raw)
In-Reply-To: <1202024064.7208.6.camel@pasglop>
Benjamin Herrenschmidt wrote:
> On Thu, 2008-01-31 at 16:10 -0600, Rune Torgersen wrote:
>> Scott Wood wrote:
>>> Changing update_mmu_cache() to always call flush_dcache_icache_page()
>>> fixes it, though a better performing fix would probably be to add an
>>> exception table entry for the dcbst.
>> I can confirm that this seems to fix it.
>
> Might be better to avoid the flush when the page isn't readable ?
Sure, that'd work. I was trying to avoid a tablewalk to determine that,
not noticing the pte argument staring me in the face. :-P
-Scott
next prev parent reply other threads:[~2008-02-04 18:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 13:45 Kernel oops while duming user core Rune Torgersen
2008-01-31 16:15 ` Nathan Lynch
2008-01-31 16:26 ` Rune Torgersen
2008-01-31 17:40 ` Rune Torgersen
2008-01-31 19:15 ` Kumar Gala
2008-01-31 19:18 ` Rune Torgersen
2008-01-31 20:16 ` Scott Wood
2008-01-31 20:19 ` Rune Torgersen
2008-01-31 20:38 ` Rune Torgersen
2008-01-31 20:41 ` Nathan Lynch
2008-01-31 20:45 ` Rune Torgersen
2008-01-31 20:55 ` Scott Wood
2008-01-31 21:58 ` Scott Wood
2008-01-31 22:10 ` Rune Torgersen
2008-02-03 7:34 ` Benjamin Herrenschmidt
2008-02-04 18:23 ` Scott Wood [this message]
2008-01-31 19:15 ` Kumar Gala
2008-01-31 19:23 ` Rune Torgersen
2008-01-31 19:54 ` Nathan Lynch
2008-02-01 17:38 ` Scott Wood
2008-02-02 12:05 ` Clemens Koller
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=47A75823.5050001@freescale.com \
--to=scottwood@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
/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;
as well as URLs for NNTP newsgroup(s).