Re: [Xen-devel] [locking/paravirt] static_key_disable_cpuslocked(): static key 'virt_spin_lock_key+0x0/0x20' used before call to jump_label_init()

2017-10-30 Thread Fengguang Wu
On Mon, Oct 30, 2017 at 09:38:35AM +0100, Fengguang Wu wrote: On Mon, Oct 30, 2017 at 08:47:08AM +0100, Juergen Gross wrote: On 30/10/17 08:35, Fengguang Wu wrote: On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: Hi Linus, Up to now we see the below boot error/warnings when

Re: [Xen-devel] [locking/paravirt] static_key_disable_cpuslocked(): static key 'virt_spin_lock_key+0x0/0x20' used before call to jump_label_init()

2017-10-30 Thread Fengguang Wu
On Mon, Oct 30, 2017 at 08:47:08AM +0100, Juergen Gross wrote: On 30/10/17 08:35, Fengguang Wu wrote: On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: Hi Linus, Up to now we see the below boot error/warnings when testing v4.14-rc6. They hit the RC release mainly due to various

Re: [Xen-devel] [PATCH 0/9] xen: build fixes with gcc5 and binutils 2.25.0

2016-02-06 Thread Fengguang Wu
Hi Doug, > > 0 day build tests the kernel all the time, even if my patch gets > > missed, after a few days other will immediately notice. These days > > its extremely hard for me to build linux-next and have a build > > issue. > > > > I recommend we push on the momentum to see if we can piggy bac

Re: [Xen-devel] Adding Xen to the kbuild bot?

2016-02-05 Thread Fengguang Wu
On Fri, Feb 05, 2016 at 12:10:56PM -0800, Andy Lutomirski wrote: > On Feb 4, 2016 7:11 PM, "Fengguang Wu" wrote: > > > > Hi Andy, > > > > CC more people on Xen testing -- in case OSStest already (or plans to) > > cover such test case. > > &

Re: [Xen-devel] Adding Xen to the kbuild bot?

2016-02-04 Thread Fengguang Wu
Hi Andy, CC more people on Xen testing -- in case OSStest already (or plans to) cover such test case. On Tue, Feb 02, 2016 at 07:31:30PM -0800, Andy Lutomirski wrote: > Hi all- > > Would it make sense to add some basic Xen PV testing to the kbuild bot? Do you mean to run basic Xen testing on th

[Xen-devel] [x86/xen] WARNING: CPU: 0 PID: 1 at arch/x86/xen/apic.c:73 xen_apic_write()

2015-03-05 Thread Fengguang Wu
Greetings, 0day kernel testing robot got the below dmesg and the first bad commit is git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip revert-3f4560207f796d5f79c18329d5a5d383fe3c97bb-3f4560207f796d5f79c18329d5a5d383fe3c97bb commit 3f4560207f796d5f79c18329d5a5d383fe3c97bb Author: Konrad