All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: lkp@lists.01.org
Subject: Re: [Xen-devel] [PATCH v3 0/7] Enhance PAT init to fix Xorg crashes
Date: Wed, 30 Mar 2016 14:58:33 -0400	[thread overview]
Message-ID: <20160330185833.GA3323@char.us.oracle.com> (raw)
In-Reply-To: <CAB=NE6VZD3gJicAzm3068APmVeKmFdF-gavNjEoVCz51hV262g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]

On Wed, Mar 30, 2016 at 11:02:13AM -0700, Luis R. Rodriguez wrote:
> On Tue, Mar 29, 2016 at 8:49 AM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > 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!
> 
> Hoping Boris or someone on the Xen front would test this prior to
> merging helps but it also slows us down, a while ago we discussed the

Boris did test it _before_ it was merged.

> possibility of getting Linux Xen guests automatically tested as part
> of 0-day, this way then when a developer (in this case Toshi) pushes
> to his own tree, he'd be able to just sit and wait for the results,
> without having to hope Boris or someone goes out and tests.

In Fedora you just need to do:

#yum install xen
#reboot
And pick the Xen option. 

Probably the same thing with Debian and Ubuntu - just 'apt-get install xen'

> 
> Its a major undertaking to get Linux Xen guests boot strapped into

It is?

> 0-day, however such prospects were raised a while ago and it seems we
> may be able to get there. Just wanted to send a reminder about this
> possibility, and highlight this patch set as an ideal candidate where
> a proactive test could have helped as well. I proactively caught the
> original Xen issue, but git logs shows we are not doing so great in
> this area, so any help on the Xen side as well to help with 0-day
> integration would be appreciated.
> 
> I'll follow up on another thread on that.

Sure. It never hurts to have more coverage.
> 
>  Luis
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel(a)lists.xen.org
> http://lists.xen.org/xen-devel

WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: Toshi Kani <toshi.kani@hpe.com>,
	lkp@ml01.01.org, "Hao, Xudong" <xudong.hao@intel.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Olaf Hering <ohering@suse.de>,
	Ingo Molnar <mingo@kernel.org>, X86 ML <x86@kernel.org>,
	Robert Schweikert <rjschwei@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Borislav Petkov <bp@suse.de>,
	elliott@hpe.com, Charles Arnold <carnold@suse.com>,
	Olaf Hering <olaf@aepfle.de>, Michal Marek <mmarek@suse.cz>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Juergen Gross <jgross@suse.com>, Mike Latimer <mlatimer@suse.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Lars Kurth <lars.kurth@xen.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	Fengguang Wu <fengguang.wu@intel.com>
Subject: Re: [PATCH v3 0/7] Enhance PAT init to fix Xorg crashes
Date: Wed, 30 Mar 2016 14:58:33 -0400	[thread overview]
Message-ID: <20160330185833.GA3323@char.us.oracle.com> (raw)
In-Reply-To: <CAB=NE6VZD3gJicAzm3068APmVeKmFdF-gavNjEoVCz51hV262g@mail.gmail.com>

On Wed, Mar 30, 2016 at 11:02:13AM -0700, Luis R. Rodriguez wrote:
> On Tue, Mar 29, 2016 at 8:49 AM, Toshi Kani <toshi.kani@hpe.com> wrote:
> > 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!
> 
> Hoping Boris or someone on the Xen front would test this prior to
> merging helps but it also slows us down, a while ago we discussed the

Boris did test it _before_ it was merged.

> possibility of getting Linux Xen guests automatically tested as part
> of 0-day, this way then when a developer (in this case Toshi) pushes
> to his own tree, he'd be able to just sit and wait for the results,
> without having to hope Boris or someone goes out and tests.

In Fedora you just need to do:

#yum install xen
#reboot
And pick the Xen option. 

Probably the same thing with Debian and Ubuntu - just 'apt-get install xen'

> 
> Its a major undertaking to get Linux Xen guests boot strapped into

It is?

> 0-day, however such prospects were raised a while ago and it seems we
> may be able to get there. Just wanted to send a reminder about this
> possibility, and highlight this patch set as an ideal candidate where
> a proactive test could have helped as well. I proactively caught the
> original Xen issue, but git logs shows we are not doing so great in
> this area, so any help on the Xen side as well to help with 0-day
> integration would be appreciated.
> 
> I'll follow up on another thread on that.

Sure. It never hurts to have more coverage.
> 
>  Luis
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-03-30 18:58 UTC|newest]

Thread overview: 43+ 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 1/7] " Toshi Kani
2016-03-23 21:41 ` [PATCH v3 2/7] x86/mm/pat: Add pat_disable() interface Toshi Kani
2016-03-23 21:41   ` 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-23 21:41 ` 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-23 21:42   ` 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 5/7] " 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-23 21:42   ` [PATCH v3 6/7] x86/xen, pat: " Toshi Kani
2016-03-29 10:39   ` [tip:x86/mm] " tip-bot for Toshi Kani
2016-03-23 21:42 ` [PATCH v3 7/7] x86/pat: Document PAT initialization Toshi Kani
2016-03-23 21:42 ` 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 10:34 ` 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
2016-03-30 18:02         ` Luis R. Rodriguez
2016-03-30 18:02         ` [Xen-devel] " Luis R. Rodriguez
2016-03-30 18:02           ` Luis R. Rodriguez
2016-03-30 18:58           ` Konrad Rzeszutek Wilk [this message]
2016-03-30 18:58             ` Konrad Rzeszutek Wilk
2016-03-30 20:10             ` [LKP] " Luis R. Rodriguez
2016-03-30 20:10             ` [Xen-devel] " Luis R. Rodriguez
2016-03-30 20:10               ` [LKP] " Luis R. Rodriguez
2016-03-30 20:29               ` Konrad Rzeszutek Wilk
2016-03-30 20:29                 ` [LKP] " Konrad Rzeszutek Wilk
2016-03-30 20:47                 ` Luis R. Rodriguez
2016-03-30 20:47                 ` [Xen-devel] " Luis R. Rodriguez
2016-03-30 20:47                   ` [LKP] " Luis R. Rodriguez
2016-03-29 15:49       ` Toshi Kani
2016-03-29 14:46     ` Boris Ostrovsky
2016-03-29 14:19   ` Toshi Kani

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=20160330185833.GA3323@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=lkp@lists.01.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.