From: Mario Smarduch <m.smarduch@samsung.com>
To: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
Christoffer Dall <christoffer.dall@linaro.org>,
Marc Zyngier <Marc.Zyngier@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: stage2_unmap_vm - softlockup watchdog
Date: Tue, 12 Jan 2016 17:20:12 -0800 [thread overview]
Message-ID: <5695A64C.2010701@samsung.com> (raw)
While running tests on foundation and fast models. stage2_unmap_vm()
triggers the softlockup watchdog (on a reboot). I have not tried to reproduce
on hardware or work with the thresholds (watchdog_thresh()) these could
be more aggressive and usually are in more critical environments.
I think that calling 'touch_softlockup_watchdog()' someplace while walking
second stage tables should prevent this.
On hardware huge VMs may be susceptible to this.
This is only likely to happen when main memory is fragmented and 2nd stage
tables are backed by pages. With huge pages only everything appears to work fine.
- Mario
WARNING: multiple messages have this Message-ID (diff)
From: m.smarduch@samsung.com (Mario Smarduch)
To: linux-arm-kernel@lists.infradead.org
Subject: stage2_unmap_vm - softlockup watchdog
Date: Tue, 12 Jan 2016 17:20:12 -0800 [thread overview]
Message-ID: <5695A64C.2010701@samsung.com> (raw)
While running tests on foundation and fast models. stage2_unmap_vm()
triggers the softlockup watchdog (on a reboot). I have not tried to reproduce
on hardware or work with the thresholds (watchdog_thresh()) these could
be more aggressive and usually are in more critical environments.
I think that calling 'touch_softlockup_watchdog()' someplace while walking
second stage tables should prevent this.
On hardware huge VMs may be susceptible to this.
This is only likely to happen when main memory is fragmented and 2nd stage
tables are backed by pages. With huge pages only everything appears to work fine.
- Mario
next reply other threads:[~2016-01-13 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 1:20 Mario Smarduch [this message]
2016-01-13 1:20 ` stage2_unmap_vm - softlockup watchdog Mario Smarduch
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=5695A64C.2010701@samsung.com \
--to=m.smarduch@samsung.com \
--cc=Marc.Zyngier@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.