From: Andi Kleen <andi@firstfloor.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Jerome Glisse <glisse@freedesktop.org>,
suresh.b.siddha@intel.com, venkatesh.pallipadi@intel.com,
thellstrom@vmware.com, airlied@linux.ie, currojerez@riseup.net,
linux-kernel@vger.kernel.org
Subject: Re: Uncool feature for TTM introduced by x86, pat: Use page flags to track memtypes of RAM pages
Date: Thu, 18 Feb 2010 21:27:54 +0100 [thread overview]
Message-ID: <20100218202753.GI5964@basil.fritz.box> (raw)
In-Reply-To: <4B7D7AF9.9060600@zytor.com>
On Thu, Feb 18, 2010 at 09:38:01AM -0800, H. Peter Anvin wrote:
> On 02/18/2010 09:27 AM, Andi Kleen wrote:
> > Jerome Glisse <glisse@freedesktop.org> writes:
> >>
> >> Can we modify the interface to support again changing from uc to wc
> >> or wc to uc ? (i can try to do a patch for that).
> >
> > At least on Intel CPUs that support self-snoop (all modern
> > ones) that should really be very cheap.
> >
>
> The UC/WC transition should be particularly trivial; I don't see any
> reason it should have to go through any other procedure on *any* CPU --
> selfsnoop shouldn't even figure into it, since neither UC nor WC
> actually caches anything. For the WC->UC direction, all we should need
> to do is to flush the write combiners; a simple wmb() will do that.
I'm not sure that is sanctioned by the SDM rules; AFAIK they don't
make any special exception for this case.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-02-18 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 15:30 Uncool feature for TTM introduced by x86, pat: Use page flags to track memtypes of RAM pages Jerome Glisse
2010-02-18 16:35 ` Jerome Glisse
2010-02-18 18:46 ` Suresh Siddha
2010-02-18 17:27 ` Andi Kleen
2010-02-18 17:38 ` H. Peter Anvin
2010-02-18 20:27 ` Andi Kleen [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=20100218202753.GI5964@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=airlied@linux.ie \
--cc=currojerez@riseup.net \
--cc=glisse@freedesktop.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suresh.b.siddha@intel.com \
--cc=thellstrom@vmware.com \
--cc=venkatesh.pallipadi@intel.com \
/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.