From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Joshua Covington <joshuacov@googlemail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] x86, mtrr: fixs for mtrr_cleanup
Date: Tue, 18 Jun 2013 11:29:53 -0500 [thread overview]
Message-ID: <51C08B01.40200@zytor.com> (raw)
In-Reply-To: <1371154622-8929-1-git-send-email-yinghai@kernel.org>
On 06/13/2013 03:17 PM, Yinghai Lu wrote:
> Joshua reported: Commit cd7b304dfaf1 (x86, range: fix missing merge
> during add range) broke mtrr cleanup on his setup in 3.9.5.
> corresponding commit in upstream is fbe06b7bae7c.
>
> *BAD*gran_size: 64K chunk_size: 16M num_reg: 6 lose cover RAM: -0G
>
> https://bugzilla.kernel.org/show_bug.cgi?id=59491
>
> Fix it from two places, so late mtrr cleanup side and range add side.
>
> x86, mtrr: Fix original mtrr range get for mtrr_cleanup
> range: Do not add new blank slot with add_range_with_merge
>
> Please apply them for v3.10.
>
On this subject: what do we need to happen to be able to dump the MTRR
cleanup stuff?
-hpa
next prev parent reply other threads:[~2013-06-18 16:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 20:17 [PATCH v3 0/2] x86, mtrr: fixs for mtrr_cleanup Yinghai Lu
2013-06-13 20:17 ` [PATCH v3 1/2] x86, mtrr: Fix original mtrr range get " Yinghai Lu
2013-06-18 16:25 ` Josh Boyer
2013-06-18 16:52 ` [tip:x86/urgent] " tip-bot for Yinghai Lu
2013-06-13 20:17 ` [PATCH v3 2/2] range: Do not add new blank slot with add_range_with_merge Yinghai Lu
2013-06-18 16:52 ` [tip:x86/urgent] " tip-bot for Yinghai Lu
2013-06-18 16:29 ` H. Peter Anvin [this message]
2013-06-18 17:28 ` [PATCH v3 0/2] x86, mtrr: fixs for mtrr_cleanup Yinghai Lu
2013-06-18 17:33 ` H. Peter Anvin
2013-06-18 18:24 ` Yinghai Lu
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=51C08B01.40200@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=joshuacov@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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