From: Dan Malek <ppc6dev@digitaldans.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev <linuxppc-dev@ozlabs.org>, Willy Tarreau <w@1wt.eu>
Subject: Re: [PATCH 0/3] 8xx: Large page(8MB) support for 2.4
Date: Wed, 12 Oct 2011 18:08:12 -0700 [thread overview]
Message-ID: <A1820550-38CB-445E-B7EB-7D0077673686@digitaldans.com> (raw)
In-Reply-To: <OF76F1F5B7.8750C8C4-ONC1257927.00767D9A-C1257927.0076B5BE@transmode.se>
Hi Joakim.
On Oct 12, 2011, at 2:36 PM, Joakim Tjernlund wrote:
> Dan, where did you go? I figured you would throw yourself at this as
> this is
> something you been meaning to do yourself for years :)
Too many things to do :-) I did have the wired page version that I've
been using now and then.
I had the bad thought yesterday that we need to check the
implementation for coherent memory. It appears we set the
pages non-cached, which could cause some trouble. We
have to ensure we never access the same physical page
with different attributes from the 8M mapping and the single
page "coherent" mapping.
I'll try to get some testing done.
Thanks.
-- Dan
next prev parent reply other threads:[~2011-10-13 1:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 11:38 [PATCH 0/3] 8xx: Large page(8MB) support for 2.4 Joakim Tjernlund
2011-10-10 11:38 ` [PATCH 1/3] 8xx: replace _PAGE_EXEC with _PAGE_PSE Joakim Tjernlund
2011-10-10 11:38 ` [PATCH 2/3] 8xx: Support LARGE pages in TLB code Joakim Tjernlund
2011-10-10 11:38 ` [PATCH 3/3] 8xx: Use LARGE pages for kernel RAM Joakim Tjernlund
2011-10-10 16:22 ` [PATCH 0/3] 8xx: Large page(8MB) support for 2.4 Dan Malek
2011-10-10 16:29 ` Willy Tarreau
2011-10-10 16:45 ` Joakim Tjernlund
2011-10-10 18:03 ` Dan Malek
2011-10-11 7:42 ` Joakim Tjernlund
[not found] ` <OF5A487DD5.BE515A85-ONC1257926.0029F008-C1257926.002A6323@LocalDomain>
2011-10-12 21:36 ` Joakim Tjernlund
2011-10-13 1:08 ` Dan Malek [this message]
2011-10-13 14:00 ` Joakim Tjernlund
2011-10-13 15:48 ` Dan Malek
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=A1820550-38CB-445E-B7EB-7D0077673686@digitaldans.com \
--to=ppc6dev@digitaldans.com \
--cc=joakim.tjernlund@transmode.se \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
--cc=w@1wt.eu \
/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