All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Shaposhnik <roman@zededa.com>
To: "Jürgen Groß" <jgross@suse.com>
Cc: "Stefano Stabellini" <sstabellini@kernel.org>,
	Xen-devel <xen-devel@lists.xenproject.org>,
	"Jan Beulich" <jbeulich@suse.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>,
	"George Dunlap" <george.dunlap@citrix.com>
Subject: Re: Linux DomU freezes and dies under heavy memory shuffling
Date: Wed, 17 Feb 2021 00:12:07 -0800	[thread overview]
Message-ID: <CAMmSBy8k0Y50Xkq9Kq+oES27gsoG==T++Hz9SiR0gDgAKnpvRA@mail.gmail.com> (raw)
In-Reply-To: <45b8ef4c-6d36-e91b-ca1a-a82eeca5aaf5@suse.com>

Hi Jürgen, thanks for taking a look at this. A few comments below:

On Tue, Feb 16, 2021 at 10:47 PM Jürgen Groß <jgross@suse.com> wrote:
>
> On 16.02.21 21:34, Stefano Stabellini wrote:
> > + x86 maintainers
> >
> > It looks like the tlbflush is getting stuck?
>
> I have seen this case multiple times on customer systems now, but
> reproducing it reliably seems to be very hard.

It is reliably reproducible under my workload but it take a long time
(~3 days of the workload running in the lab).

> I suspected fifo events to be blamed, but just yesterday I've been
> informed of another case with fifo events disabled in the guest.
>
> One common pattern seems to be that up to now I have seen this effect
> only on systems with Intel Gold cpus. Can it be confirmed to be true
> in this case, too?

I am pretty sure mine isn't -- I can get you full CPU specs if that's useful.

> In case anybody has a reproducer (either in a guest or dom0) with a
> setup where a diagnostic kernel can be used, I'd be _very_ interested!

I can easily add things to Dom0 and DomU. Whether that will disrupt the
experiment is, of course, another matter. Still please let me know what
would be helpful to do.

Thanks,
Roman.


  reply	other threads:[~2021-02-17  8:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 20:03 Linux DomU freezes and dies under heavy memory shuffling Roman Shaposhnik
2021-02-16 20:34 ` Stefano Stabellini
2021-02-17  6:47   ` Jürgen Groß
2021-02-17  8:12     ` Roman Shaposhnik [this message]
2021-02-17  8:29       ` Jürgen Groß
2021-02-18  5:21         ` Roman Shaposhnik
2021-02-18  9:34           ` Jürgen Groß
2021-02-23 13:17           ` Jürgen Groß
2021-02-25  3:06             ` Roman Shaposhnik
2021-02-25  3:44               ` Elliott Mitchell
2021-02-25  4:30                 ` Roman Shaposhnik
2021-02-25  4:47                   ` Elliott Mitchell
2021-03-12 21:33               ` Roman Shaposhnik
2021-03-13  7:18                 ` Jürgen Groß

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='CAMmSBy8k0Y50Xkq9Kq+oES27gsoG==T++Hz9SiR0gDgAKnpvRA@mail.gmail.com' \
    --to=roman@zededa.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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.