From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Andreas Werner <wernerandy@gmx.de>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, dave@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] X86: MM: Add PAT Type write-through in combination with mtrr
Date: Mon, 28 Oct 2013 11:31:32 +0100 [thread overview]
Message-ID: <20131028103132.GA6274@gmail.com> (raw)
In-Reply-To: <20131028102938.GD4314@pd.tnic>
* Borislav Petkov <bp@alien8.de> wrote:
> On Mon, Oct 28, 2013 at 11:17:49AM +0100, Ingo Molnar wrote:
>
> > And regular write-back cacheable isn't sufficient because the
> > CPU could do things like prefetch your range automatically?
>
> Yeah, he's doing a CLFLUSH anyway which basically makes it a
> write-through...
The CLFLUSH is done afterwards (making it a use-once thing), so WB
might still be faster and would avoid the PAT headache ...
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-28 10:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 12:55 [PATCH] X86: MM: Add PAT Type write-through in combination with mtrr Andreas Werner
2013-10-27 13:34 ` Borislav Petkov
2013-10-27 16:51 ` Andreas Werner
2013-10-27 17:31 ` Borislav Petkov
2013-10-27 17:56 ` Andreas Werner
2013-10-27 19:01 ` Borislav Petkov
2013-10-28 6:29 ` Andreas Werner
2013-10-28 10:17 ` Ingo Molnar
2013-10-28 10:29 ` Borislav Petkov
2013-10-28 10:31 ` Ingo Molnar [this message]
2013-10-28 10:44 ` Borislav Petkov
2013-10-28 10:45 ` Andreas Werner
2013-10-28 10:51 ` Ingo Molnar
2013-10-28 10:53 ` H. Peter Anvin
2013-10-28 11:02 ` Andreas Werner
2013-10-28 10:31 ` H. Peter Anvin
2013-10-28 10:34 ` Andreas Werner
2013-10-28 10:57 ` Borislav Petkov
2013-10-28 11:25 ` Andreas Werner
2013-10-28 11:45 ` Borislav Petkov
2013-10-28 12:03 ` Andreas Werner
2013-10-28 13:58 ` Borislav Petkov
2013-10-28 14:19 ` Andreas Werner
-- strict thread matches above, loose matches on Subject: below --
2013-08-25 7:01 Andreas Werner
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=20131028103132.GA6274@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=dave@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--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 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).