From: Toshi Kani <toshi.kani@hpe.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Ingo Molnar <mingo@kernel.org>
Cc: jgross@suse.com, mcgrof@suse.com, x86@kernel.org,
linux-kernel@vger.kernel.org, paul.gortmaker@windriver.com,
hpa@zytor.com, xen-devel@lists.xenproject.org,
tglx@linutronix.de, bp@suse.de, elliott@hpe.com,
Olaf Hering <olaf@aepfle.de>
Subject: Re: [Xen-devel] [PATCH v3 0/7] Enhance PAT init to fix Xorg crashes
Date: Tue, 29 Mar 2016 09:49:27 -0600 [thread overview]
Message-ID: <1459266567.6393.669.camel@hpe.com> (raw)
In-Reply-To: <56FA9563.60401@oracle.com>
On Tue, 2016-03-29 at 10:46 -0400, Boris Ostrovsky wrote:
> On 03/29/2016 10:19 AM, Toshi Kani wrote:
> > On Tue, 2016-03-29 at 12:34 +0200, Ingo Molnar wrote:
> >
> > > > I'd appreciate if someone can test this patch-set on Xen to verify
> > > > that there is no change in "x86/PAT: Configuration [0-7] .."
> > > > message in dmesg.
> > > So I don't have a Xen setup, but hopefully such testing will happen
> > > once these changes show up in linux-next, tomorrow or so.
> > I will address if any issue is found in testing.
>
> I ran a subset of out nightly test. Nobody died.
>
> So this all looks good. (It actually may have also fixed another bug
> that was reported recently by Olaf, copied here)
Cool! Thanks Boris!
-Toshi
next prev parent reply other threads:[~2016-03-29 14:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 21:41 [PATCH v3 0/7] Enhance PAT init to fix Xorg crashes Toshi Kani
2016-03-23 21:41 ` [PATCH v3 1/7] x86/mm/pat: Add support of non-default PAT MSR setting Toshi Kani
2016-03-29 10:37 ` [tip:x86/mm] " tip-bot for Toshi Kani
2016-03-23 21:41 ` [PATCH v3 2/7] x86/mm/pat: Add pat_disable() interface Toshi Kani
2016-03-29 10:38 ` [tip:x86/mm] " tip-bot for Toshi Kani
2016-03-23 21:41 ` [PATCH v3 3/7] x86/mm/pat: Replace cpu_has_pat with boot_cpu_has Toshi Kani
2016-03-29 10:38 ` [tip:x86/mm] x86/mm/pat: Replace cpu_has_pat with boot_cpu_has() tip-bot for Toshi Kani
2016-03-23 21:42 ` [PATCH v3 4/6] x86/mtrr: Fix Xorg crashes in Qemu sessions Toshi Kani
2016-03-29 10:39 ` [tip:x86/mm] " tip-bot for Toshi Kani
2016-03-23 21:42 ` [PATCH v3 5/7] x86/mtrr: Fix PAT init handling when MTRR is disabled Toshi Kani
2016-03-29 10:39 ` [tip:x86/mm] " tip-bot for Toshi Kani
2016-03-23 21:42 ` [PATCH v3 6/7] x86/xen,pat: Remove PAT table init code from Xen Toshi Kani
2016-03-29 10:39 ` [tip:x86/mm] x86/xen, pat: " tip-bot for Toshi Kani
2016-03-23 21:42 ` [PATCH v3 7/7] x86/pat: Document PAT initialization Toshi Kani
2016-03-29 10:40 ` [tip:x86/mm] x86/pat: Document the PAT initialization sequence tip-bot for Toshi Kani
2016-03-29 10:34 ` [PATCH v3 0/7] Enhance PAT init to fix Xorg crashes Ingo Molnar
2016-03-29 14:19 ` Toshi Kani
2016-03-29 14:46 ` [Xen-devel] " Boris Ostrovsky
2016-03-29 15:49 ` Toshi Kani [this message]
2016-03-30 18:02 ` Luis R. Rodriguez
[not found] ` <20160330185833.GA3323@char.us.oracle.com>
2016-03-30 20:10 ` [LKP] " Luis R. Rodriguez
[not found] ` <20160330202920.GB23916@char.us.oracle.com>
2016-03-30 20:47 ` 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=1459266567.6393.669.camel@hpe.com \
--to=toshi.kani@hpe.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@suse.de \
--cc=elliott@hpe.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@suse.com \
--cc=mingo@kernel.org \
--cc=olaf@aepfle.de \
--cc=paul.gortmaker@windriver.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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