From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Parisc List <linux-parisc@vger.kernel.org>
Subject: Notes about the latest cache patches
Date: Fri, 15 Apr 2011 12:41:50 -0500 [thread overview]
Message-ID: <1302889310.7706.8.camel@mulgrave.site> (raw)
The one that seems to make the most difference to me is not having the
kernel memory cache pages be marked executable. This cures an
intermittent segfault I was seeing with git on the pa8800.
Also note that if you apply only the speculative read prevention patch,
you'll find the incidences of segfaults and cache nasties get worse (at
least they do on ion) mainly because the aggressive TLB purging leaves
the cache hardware with fewer lines to speculate, so it tends to be more
aggressive about speculating them ... leading to more incidences.
I find that the combination of the two patches cures all the segfaults
I've been seeing in normal compiles and git operations.
James
next reply other threads:[~2011-04-15 17:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 17:41 James Bottomley [this message]
2011-04-20 14:17 ` Notes about the latest cache patches John David Anglin
2011-04-20 18:15 ` John David Anglin
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=1302889310.7706.8.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-parisc@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