From: Chuck Ebbert <cebbert.lkml@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
linux-kernel@vger.kernel.org,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Jiri Kosina <jkosina@suse.cz>,
Steven Rostedt <rostedt@goodmis.org>,
Jason Baron <jbaron@akamai.com>,
yrl.pp-manager.tt@hitachi.com, Borislav Petkov <bpetkov@suse.de>,
Ingo Molnar <mingo@kernel.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: i915.ko WC writes are slow after ea8596bb2d8d379
Date: Thu, 9 Oct 2014 07:44:16 -0500 [thread overview]
Message-ID: <20141009074416.1480426a@as> (raw)
In-Reply-To: <20141009065331.GG12897@nuc-i3427.alporthouse.com>
On Thu, 9 Oct 2014 07:53:31 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:
> # cat /proc/mtrr
> reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
> reg01: base=0x080000000 ( 2048MB), size= 256MB, count=1: write-back
> reg02: base=0x08e000000 ( 2272MB), size= 32MB, count=1: uncachable
> reg03: base=0x08d000000 ( 2256MB), size= 16MB, count=1: uncachable
> reg04: base=0x100000000 ( 4096MB), size= 2048MB, count=1: write-back
> reg05: base=0x170000000 ( 5888MB), size= 256MB, count=1: uncachable
> reg06: base=0x16f000000 ( 5872MB), size= 16MB, count=1: uncachable
> reg07: base=0x16e800000 ( 5864MB), size= 8MB, count=1: uncachable
> reg08: base=0x16e600000 ( 5862MB), size= 2MB, count=1: uncachable
>
Well that's what the kernel thinks is in every CPU.
Could you try installing x86info and running "x86info --mtrr
--all-cpus" while running the broken kernel?
next prev parent reply other threads:[~2014-10-09 12:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 9:03 i915.ko WC writes are slow after ea8596bb2d8d379 Chris Wilson
2014-10-08 10:10 ` Chuck Ebbert
2014-10-08 19:49 ` Chris Wilson
2014-10-08 21:36 ` H. Peter Anvin
2014-10-09 6:53 ` Chris Wilson
2014-10-09 12:44 ` Chuck Ebbert [this message]
2014-10-09 13:00 ` Chris Wilson
2014-10-09 14:46 ` Chuck Ebbert
2014-10-09 15:14 ` Chris Wilson
2015-11-18 14:48 ` Chris Wilson
2015-11-18 15:57 ` Andy Lutomirski
2015-11-19 8:14 ` Ingo Molnar
2015-11-19 10:03 ` [PATCH] kernel: Remove stop_machine() Kconfig dependency Chris Wilson
2015-11-19 8:16 ` i915.ko WC writes are slow after ea8596bb2d8d379 Ingo Molnar
2014-10-08 17:47 ` Chuck Ebbert
2014-10-09 1:45 ` Masami Hiramatsu
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=20141009074416.1480426a@as \
--to=cebbert.lkml@gmail.com \
--cc=bpetkov@suse.de \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=hpa@linux.intel.com \
--cc=jbaron@akamai.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yrl.pp-manager.tt@hitachi.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.