From: "H. Peter Anvin" <hpa@zytor.com>
To: Andreas Werner <wernerandy@gmx.de>, tglx@linutronix.de
Cc: mingo@redhat.com, x86@kernel.org, linux-kernel@vger.kernel.org,
bp@alien8.de
Subject: Re: [PATCH v2] X86: MM: Add PAT Type write-through in combination with mtrr
Date: Mon, 18 Nov 2013 18:24:24 -0800 [thread overview]
Message-ID: <528ACBD8.3070804@zytor.com> (raw)
In-Reply-To: <1383480142-5665-1-git-send-email-wernerandy@gmx.de>
On 11/03/2013 04:02 AM, Andreas Werner wrote:
> Revision 2:
> added comment in code.
>
> This patch adds the Write-through memory type in combination with mtrr.
> If you call ioremap_cache to request cachable memory (write-back) the
> function tries to set the PAT to write-back only if the mtrr setting of
> the requested region is also marked as Write-Back.
>
> If the mttr regions are marked e.g. as Write-through or with other
> types, the function will always return UC- memory.
>
> If you check the Intel document " IA-32 SDM vol 3a table Effective
> Memory Type", there
> are many other combinations possible.
>
> This patch will only add the following combination:
> PAT=Write-Back + MTRR=Write-Through.
>
> Since marking IO Memory as cachable is not valid, WT is the
> best way for caching/bursting on MMIO Devices.
>
> Tested on - Intel (R) Atom E680 (Tunnel Creek)
> - Intel (R) Core(TM)2 Duo
>
> Signed-off-by: Andreas Werner <wernerandy@gmx.de>
I don't quite know where this ended up, but I am *really* not happy
about going back to using MTRRs to mark I/O devices with the chronic
problems of MTRR exhaustion that entails. As such I do insist that PAT
is properly updated to support WT if we're going to do this.
-hpa
prev parent reply other threads:[~2013-11-19 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 12:02 [PATCH v2] X86: MM: Add PAT Type write-through in combination with mtrr Andreas Werner
2013-11-03 17:44 ` H. Peter Anvin
2013-11-03 18:14 ` Andreas Werner
2013-11-19 2:24 ` H. Peter Anvin [this message]
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=528ACBD8.3070804@zytor.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=wernerandy@gmx.de \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.