mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric B Munson <emunson@mgebm.net>
To: john stultz <johnstul@us.ibm.com>
Cc: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: soft lockup detector & virtualisation
Date: Thu, 16 Feb 2012 20:57:40 -0500	[thread overview]
Message-ID: <78aa6599cf8dddc4d44f39bcdd0bb917@mgebm.net> (raw)
In-Reply-To: <CANcMJZAfT7Sz=5D=PVQwoy_hvEYZxowUxBo4EXN-U72mecE9SQ@mail.gmail.com>

On Thu, 16 Feb 2012 17:39:38 -0800, john stultz wrote:
> On Thu, Feb 16, 2012 at 3:15 PM, Dave Jones <davej@redhat.com> wrote:
>> Lately I've noticed quite a few soft lockup bugs being reported.
>> In many of them, they're coming from inside virtual guests.
>>
>> Is the softlockup detector fundamentally broken in this situation ?
>>
>> If the host doesn't schedule the guest for whatever reason,
>> or the user suspends the VM and resumes it later ?
>>
>> Here's the most recent example:
>> https://bugzilla.redhat.com/attachment.cgi?id=563767
>>
>> In many of these, the code where it's "stuck" isn't anything
>> special, which is why I think the guest just hasn't had a
>> timeslice in 185 seconds.
>>
>> Is there some way we can perhaps detect we're running virtualised,
>> and disable the detector automatically ?
>
> I think Eric's work (See "Add check for suspended vm in softlockup
> detector" sent out today) tries to address this issue.
>
> thanks
> -john


The work I have been doing specifically handles the case where the 
hypervisor suspends the guest.  There is talk of extending that work to 
handle preemption as well, which I think will cover your use case.

Eric

      reply	other threads:[~2012-02-17  1:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-16 23:15 Dave Jones
2012-02-17  1:39 ` john stultz
2012-02-17  1:57   ` Eric B Munson [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=78aa6599cf8dddc4d44f39bcdd0bb917@mgebm.net \
    --to=emunson@mgebm.net \
    --cc=davej@redhat.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome