Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755243AbbHFIXT (ORCPT ); Thu, 6 Aug 2015 04:23:19 -0400 Received: from smtp.citrix.com ([66.165.176.89]:39046 "EHLO SMTP.CITRIX.COM" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754524AbbHFIXQ (ORCPT ); Thu, 6 Aug 2015 04:23:16 -0400 X-IronPort-AV: E=Sophos;i="5.15,622,1432598400"; d="scan'208";a="288639805" Message-ID: <1438849369.9747.91.camel@citrix.com> Subject: Re: [Xen-devel] printk from softirq on xen: hard lockup From: Ian Campbell To: David Vrabel , "Jason A. Donenfeld" , , , CC: Paul McKenney Date: Thu, 6 Aug 2015 09:22:49 +0100 In-Reply-To: <55C0F291.7060806@citrix.com> References: <55C0F291.7060806@citrix.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.3-1 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-DLP: MIA2 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1371 Lines: 33 On Tue, 2015-08-04 at 18:12 +0100, 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 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 > ^^ PV guest? > > > (gdb) target remote localhost:9999 > > Remote debugging using localhost:9999 > > __xapic_wait_icr_idle () at ./arch/x86/include/asm/ipi.h:56 > > 56 while (native_apic_mem_read(APIC_ICR) & APIC_ICR_BUSY) > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ => HVM guest > > Which is it? Aren't there still some code paths for PV guests which hit the native APIC case (emulated in Xen even for PV these days, since pvops in the early days didn't accept the hooks needed to make use of the hypercall versions of apic read/write). In particular I'm thinking of the IPI which is (or was) used by the sysrq to trigger the backtrace on all CPUs. Ian. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/