From: Michael Reinelt <michael@reinelt.co.at>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: MTRR cleanup does not kick in
Date: Tue, 22 May 2012 04:18:19 +0200 [thread overview]
Message-ID: <4FBAF76B.8060704@reinelt.co.at> (raw)
In-Reply-To: <4F6430F7.70207@reinelt.co.at>
Hello all,
may I draw your attention again to this issue?
I just run linux-3.4.0, seems to have still this problem (where I am not sure if this is a problem at all)
regards, Michael
Am 2012-03-17 07:36, schrieb Michael Reinelt:
> Hi there,
>
> I am (again) suffering from:
> kernel: mtrr: no more MTRRs available
> kernel: [drm] MTRR allocation failed. Graphics performance may suffer.
>
> kernel is vanilla 3.2.11
>
> I know that this *used* to work, but I had to specify mtrr_gran_size=16M mtrr_chunk_size=128M on the kernel command line.
>
> Now, with the current kernel, I could not find *any* MTRR cleanup debug messages at all.
>
> I debugged a bit, and probably found the cause:
>
> arch/x86/kernel/cpu/mtrr/cleanup.c:mtrr_need_cleanup(void)
>
> /* Check if we only had WB and UC */
> if (num[MTRR_TYPE_WRBACK] + num[MTRR_TYPE_UNCACHABLE] !=
> num_var_ranges - num[MTRR_NUM_TYPES])
> return 0;
>
> This one kicks in, and disables the MTRR cleanup, resulting in all 10 MTRR registers in use, and no more MTRRs
> available for DRM.
>
> I disabled this check, and now the MTRR cleaner works fine, even finding a optimal value for my system with only 9
> registers, leaving one available for DRM.
>
>
> maybe the mtrr_need_cleanup() function should take nr_mtrr_spare_reg into account?
>
>
>
>
> regards, Michael
>
> PS please keep me on CC as I'm not subscribed. thanks!
>
--
Michael Reinelt<michael@reinelt.co.at>
http://home.pages.at/reinelt
GPG-Key 0xDF13BA50
ICQ #288386781
prev parent reply other threads:[~2012-05-22 2:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-17 6:36 Michael Reinelt
2012-05-22 2:18 ` Michael Reinelt [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=4FBAF76B.8060704@reinelt.co.at \
--to=michael@reinelt.co.at \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®