From: Andreas Werner <wernerandy@gmx.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: tglx@linutronix.de, 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: Sun, 3 Nov 2013 19:14:28 +0100 [thread overview]
Message-ID: <20131103181427.GA1346@thinkpad.fritz.box> (raw)
In-Reply-To: <52768B8E.1060902@zytor.com>
On Sun, Nov 03, 2013 at 09:44:46AM -0800, H. Peter Anvin wrote:
> On 11/03/2013 04:02 AM, Andreas Werner wrote:
> >
> > Since marking IO Memory as cachable is not valid, WT is the
> > best way for caching/bursting on MMIO Devices.
> >
>
> Uh... WT *is* cachable...
>
> -hpa
>
>
Sorry my mistake, i mean "marking IO Memory as WB is not valid"
regards
Andy
next prev parent reply other threads:[~2013-11-03 18:14 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 [this message]
2013-11-19 2:24 ` H. Peter Anvin
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=20131103181427.GA1346@thinkpad.fritz.box \
--to=wernerandy@gmx.de \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox