From: "Kani, Toshimitsu" <toshi.kani@hpe.com>
To: "stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "eswierk@skyportsystems.com" <eswierk@skyportsystems.com>,
"x86@kernel.org" <x86@kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"paul.gortmaker@windriver.com" <paul.gortmaker@windriver.com>
Subject: x86 PAT fixes for stable
Date: Tue, 24 May 2016 17:42:47 +0000 [thread overview]
Message-ID: <1464111184.3504.60.camel@hpe.com> (raw)
Hello,
The following patches fix two x86 PAT issues reported in 4.4 [1][2]. Can
you please backport them up to 4.4?
1/7 x86/mm/pat: Add support of non-default PAT MSR setting
02f037d641dc6672be5cfe7875a48ab99b95b154
2/7 x86/mm/pat: Add pat_disable() interfacecommit
224bb1e5d67ba0f2872c98002d6a6f991ac6fd4a
3/7 x86/mm/pat: Replace cpu_has_pat with boot_cpu_has
d63dcf49cf5ae5605f4d14229e3888e104f294b1
4/7 x86/mtrr: Fix Xorg crashes in Qemu sessions
edfe63ec97ed8d4496225f7ba54c9ce4207c5431
5/7 x86/mtrr: Fix PAT init handling when MTRR is disabled
ad025a73f0e9344ac73ffe1b74c184033e08e7d5
6/7 x86/xen,pat: Remove PAT table init code from Xen
88ba281108ed0c25c9d292b48bd3f272fcb90dd0
7/7 x86/pat: Document PAT initialization
b6350c21cfe8aa9d65e189509a23c0ea4b8362c2
1/1 x86/mm/pat: Fix BUG_ON in mmap_mem on QEMU/i386
1886297ce0c8d563a08c8a8c4c0b97743e06cd37
Thanks,
-Toshi
[1] https://lkml.org/lkml/2016/3/3/828
[2] http://www.gossamer-threads.com/lists/xen/devel/432189?page=last
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2016-05-24 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 17:42 Kani, Toshimitsu [this message]
2016-05-25 6:29 ` x86 PAT fixes for stable Ingo Molnar
2016-05-25 11:17 ` Ed Swierk
2016-05-25 15:20 ` Ed Swierk
2016-08-14 15:42 ` Greg KH
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=1464111184.3504.60.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=eswierk@skyportsystems.com \
--cc=mingo@kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).