LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Christopher S. Aker" <caker@theshore.net>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	xming <xmingske@gmail.com>
Subject: Re: [Xen-devel] Re: Xen paravirt frontend block hang
Date: Tue, 18 Mar 2008 09:01:31 -0700	[thread overview]
Message-ID: <47DFE75B.7080404@goop.org> (raw)
In-Reply-To: <47CACFBE.5010007@theshore.net>

Christopher S. Aker wrote:
> Jeremy Fitzhardinge wrote:
>> Are you running an SMP or UP domain?  I found I could get hangs very 
>> easily with UP (but I need confirm it isn't a result of some other 
>> very experimental patches).
>
> The hang occurs with both SMP and UP compiled pv_ops kernels.  SMP 
> kernels are still slightly responsive after the hang occurs, which 
> makes me think only one proc gets stuck at a time, not the entire kernel. 

The patch I posted yesterday - "xen: fix RMW when unmasking events" - 
should definitively fix the hanging-under-load bugs (I hope).  It 
problem came from returning to userspace with pending events, which 
would leave them hanging around on the vcpu unprocessed, and eventually 
everything would deadlock.  This was caused by using an unlocked 
read-modify-write operation on the event pending flag - which can be set 
by another (real) cpu - meaning that the pending event wasn't noticed 
until too late.  It would only be a problem on an SMP host.

The patch should back-apply to 2.6.24.

    J

  reply	other threads:[~2008-03-19 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4772AC8E.7010007@theshore.net>
2008-02-28 20:00 ` Jeremy Fitzhardinge
2008-03-02  0:43   ` Christopher S. Aker
2008-03-02 15:35     ` Jeremy Fitzhardinge
2008-03-02 16:03       ` Christopher S. Aker
2008-03-18 16:01         ` Jeremy Fitzhardinge [this message]
2008-03-25  1:37           ` [Xen-devel] " Christopher S. Aker
     [not found] ` <47758352.5040504@goop.org>
     [not found]   ` <479E71B7.7060207@theshore.net>
     [not found]     ` <479E75E3.6030601@goop.org>
     [not found]       ` <479E7BA4.5050306@theshore.net>
     [not found]         ` <519a8b110802060437k70c099b7y7faefe63dd82039@mail.gmail.com>
     [not found]           ` <47AA845E.8020708@goop.org>
     [not found]             ` <519a8b110802070612j2a1717f3s6aa25eeea8b7d18a@mail.gmail.com>
2008-02-28 20:03               ` Jeremy Fitzhardinge

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=47DFE75B.7080404@goop.org \
    --to=jeremy@goop.org \
    --cc=caker@theshore.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=xmingske@gmail.com \
    --subject='Re: [Xen-devel] Re: Xen paravirt frontend block hang' \
    /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

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).