netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>,
	"Jason A. Donenfeld" <Jason@zx2c4.com>,
	<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
	<xen-devel@lists.xen.org>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>
Subject: Re: [Xen-devel] printk from softirq on xen: hard lockup
Date: Thu, 6 Aug 2015 09:22:49 +0100	[thread overview]
Message-ID: <1438849369.9747.91.camel@citrix.com> (raw)
In-Reply-To: <55C0F291.7060806@citrix.com>

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.

      parent reply	other threads:[~2015-08-06  8:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04 16:41 printk from softirq on xen: hard lockup Jason A. Donenfeld
2015-08-04 17:12 ` [Xen-devel] " David Vrabel
2015-08-04 17:45   ` Jason A. Donenfeld
2015-08-04 23:01   ` [Xen-devel] " Jason A. Donenfeld
2015-08-06 10:02     ` David Vrabel
2015-08-06 15:58       ` Jason A. Donenfeld
2015-08-06 16:10         ` David Vrabel
2015-08-06 16:21           ` Jason A. Donenfeld
2015-08-06 16:29             ` [PATCH] xen-apic: Enable on domU as well Jason A. Donenfeld
2015-08-06 16:37               ` [PATCH v2] " Jason A. Donenfeld
2015-08-07 14:23                 ` [Xen-devel] " Konrad Rzeszutek Wilk
2015-08-07 14:37                   ` Jason A. Donenfeld
2015-08-10 13:40                 ` [PATCH v3] " Jason A. Donenfeld
2015-08-10 13:41                   ` David Vrabel
2015-08-10 13:44                     ` Jason A. Donenfeld
2015-08-11 10:46                   ` [Xen-devel] " David Vrabel
2015-08-05 16:37   ` [Xen-devel] printk from softirq on xen: hard lockup Jason A. Donenfeld
2015-08-06  8:22   ` Ian Campbell [this message]

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=1438849369.9747.91.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Jason@zx2c4.com \
    --cc=david.vrabel@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).