Re: [Xen-devel] [PATCH v3] xen-apic: Enable on domU as well

2015-08-10 Thread Jason A. Donenfeld
On Mon, Aug 10, 2015 at 3:41 PM, David Vrabel wrote: > On 10/08/15 14:40, Jason A. Donenfeld wrote: >> It turns out that domU also requires the Xen APIC driver. Otherwise we >> get stuck in busy loops that never exit, such as in this stack trace: > > What's the differ

[Xen-devel] [PATCH v3] xen-apic: Enable on domU as well

2015-08-10 Thread Jason A. Donenfeld
ty=0, level=, dict=0x0 , dictlen=, fmt=, args=) at kernel/printk/printk.c:1778 #7 0x816010c8 in printk (fmt=) at kernel/printk/printk.c:1868 #8 0xc00013ea in ?? () #9 0x in ?? () Mailing-list-thread: https://lkml.org/lkml/2015/8/4/755 Signed-off-by: Jas

Re: [Xen-devel] [PATCH v2] xen-apic: Enable on domU as well

2015-08-07 Thread Jason A. Donenfeld
On Fri, Aug 7, 2015 at 4:23 PM, Konrad Rzeszutek Wilk wrote: > Anyhow, your patch seems to fix a regression my patch > feb44f1f7a4ac299d1ab1c3606860e70b9b89d69 > "x86/xen: Provide a "Xen PV" APIC driver to support >255 VCPUs" > introduced. Ahhh, good, okay. That explains why I didn't encounter th

[Xen-devel] [PATCH v2] xen-apic: Enable on domU as well

2015-08-06 Thread Jason A. Donenfeld
ty=0, level=, dict=0x0 , dictlen=, fmt=, args=) at kernel/printk/printk.c:1778 #7 0x816010c8 in printk (fmt=) at kernel/printk/printk.c:1868 #8 0xc00013ea in ?? () #9 0x in ?? () Mailing-list-thread: https://lkml.org/lkml/2015/8/4/755 Signed-off-by: Jas

[Xen-devel] [PATCH] xen-apic: Enable on domU as well

2015-08-06 Thread Jason A. Donenfeld
ty=0, level=, dict=0x0 , dictlen=, fmt=, args=) at kernel/printk/printk.c:1778 #7 0x816010c8 in printk (fmt=) at kernel/printk/printk.c:1868 #8 0xc00013ea in ?? () #9 0x in ?? () Mailing-list-thread: https://lkml.org/lkml/2015/8/4/755 Signed-off-by: Jas

Re: [Xen-devel] printk from softirq on xen: hard lockup

2015-08-06 Thread Jason A. Donenfeld
In that case, it doesn't compile. arch/x86/xen/apic.c:204:13: error: redefinition of ‘xen_init_apic’ void __init xen_init_apic(void) ^ In file included from arch/x86/xen/apic.c:9:0: arch/x86/xen/xen-ops.h:110:27: note: previous definition of ‘xen_init_apic’ was here static inline vo

Re: [Xen-devel] printk from softirq on xen: hard lockup

2015-08-06 Thread Jason A. Donenfeld
On Thu, Aug 6, 2015 at 12:02 PM, David Vrabel wrote: > Linux PV guests must use the "Xen PV" APIC driver. You need to > investigate why your PV guest is not using this (although I'm surprised > it works at all with the wrong one). Actually it appears this PV Guest is using the "flat" APIC driver

Re: [Xen-devel] printk from softirq on xen: hard lockup

2015-08-05 Thread Jason A. Donenfeld
(&init_net, s, &tunnel); return ret; } static void __exit mod_exit(void) { if (s) udp_tunnel_sock_release(s); } module_init(mod_init); module_exit(mod_exit); MODULE_LICENSE("GPL"); MODULE_DESCRIPTION("Send a UDP packet to port 32812"); MODULE_AUTHOR(&quo

Re: [Xen-devel] printk from softirq on xen: hard lockup

2015-08-04 Thread Jason A. Donenfeld
Hey David, Sorry for the premature response on my phone earlier. Real reply follows. >> rcu_read_lock, when using Xen PV. Relevant excerpts of the > ^^ PV guest? Yes. The lockup occurs on a PV guest. Nothing special at all about the configuration. Vanilla upstream

Re: [Xen-devel] printk from softirq on xen: hard lockup

2015-08-04 Thread Jason A. Donenfeld
PV guest domU. PV host dom0. On Aug 4, 2015 7:14 PM, "David Vrabel" wrote: > On 04/08/15 17:41, Jason A. Donenfeld wrote: > > Hi folks, > > > > Paul McKenney and I had an offline discussion about some rcu questions > > that eventually lead into me inv

[Xen-devel] printk from softirq on xen: hard lockup

2015-08-04 Thread Jason A. Donenfeld
Hi folks, Paul McKenney and I had an offline discussion about some rcu questions that eventually lead into me investigating a strange full lock-up I'm experiencing as a consequence of a printk in softirq inside of an rcu_read_lock, when using Xen PV. Relevant excerpts of the conversation follow: