From: Yinghai Lu <yinghai@kernel.org>
To: Stuart Hayes <stuart.w.hayes@gmail.com>
Cc: Prarit Bhargava <prarit@redhat.com>,
"Luis R. Rodriguez" <mcgrof@suse.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"the arch/x86 maintainers" <x86@kernel.org>,
mcgrof@do-not-panic.com, Toshi Kani <toshi.kani@hp.com>
Subject: Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup
Date: Thu, 5 Nov 2015 11:14:58 -0800 [thread overview]
Message-ID: <CAE9FiQWm=PLSpiS0ggrVDLPSp7X_-cc3wUfDqsnmt4oYQc89Eg@mail.gmail.com> (raw)
In-Reply-To: <55F6DDDF.70909@gmail.com>
On Mon, Sep 14, 2015 at 7:46 AM, Stuart Hayes <stuart.w.hayes@gmail.com> wrote:
>
> Booting with 'disable_mtrr_cleanup' works, but the system I am working with
> isn't actually failing--it just gets ugly error messages. And the BIOS on the
> system I am working with had set up the MTRRs correctly.
Please post boot log and /proc/mtrr for:
1. without your patch
2. without your patch and with disable_mtrr_cleanup in boot command line.
3. with your patch.
Thanks
Yinghai
next prev parent reply other threads:[~2015-11-05 19:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55E477DE.2060106@gmail.com>
2015-08-31 16:05 ` Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup Stuart Hayes
2015-09-03 2:45 ` Luis R. Rodriguez
2015-09-03 12:17 ` Prarit Bhargava
2015-09-03 17:59 ` Luis R. Rodriguez
2015-09-03 18:10 ` Prarit Bhargava
2015-09-03 18:40 ` Luis R. Rodriguez
2015-09-03 19:22 ` Toshi Kani
2015-09-03 19:51 ` Luis R. Rodriguez
2015-09-03 21:31 ` Toshi Kani
2015-09-03 22:07 ` Luis R. Rodriguez
2015-09-03 22:25 ` Toshi Kani
2015-09-03 22:45 ` Luis R. Rodriguez
2015-09-03 23:21 ` Toshi Kani
2015-09-03 23:54 ` Luis R. Rodriguez
2015-09-04 0:48 ` Toshi Kani
2015-09-04 1:40 ` Luis R. Rodriguez
2015-09-04 14:56 ` Toshi Kani
2015-09-04 6:51 ` Jan Beulich
2015-09-14 14:46 ` Stuart Hayes
2015-11-05 19:14 ` Yinghai Lu [this message]
2015-11-05 19:43 ` Luis R. Rodriguez
2016-03-16 20:20 ` Luis R. Rodriguez
2016-03-29 17:07 ` Luis R. Rodriguez
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='CAE9FiQWm=PLSpiS0ggrVDLPSp7X_-cc3wUfDqsnmt4oYQc89Eg@mail.gmail.com' \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.com \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=stuart.w.hayes@gmail.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.com \
--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 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.