From: Adam Borowski <kilobyte@angband.pl>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>, kvm <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kvm splat in mmu_spte_clear_track_bits
Date: Fri, 25 Aug 2017 15:14:21 +0200 [thread overview]
Message-ID: <20170825131419.r5lzm6oluauu65nx@angband.pl> (raw)
In-Reply-To: <CANRm+Cyh6xs4c8Ed2yDFGbOeuyCohTO_+AUBdwM6co5Mkj1tXQ@mail.gmail.com>
On Thu, Aug 24, 2017 at 03:43:55PM +0800, Wanpeng Li wrote:
> 2017-08-23 20:22 GMT+08:00 Paolo Bonzini <pbonzini@redhat.com>:
> > On 22/08/2017 00:32, Adam Borowski wrote:
> >> On Mon, Aug 21, 2017 at 09:58:34PM +0200, Radim Krčmář wrote:
> >>> 2017-08-21 21:12+0200, Adam Borowski:
> >>>> Also, it doesn't reproduce for me on 4.12.
> >>>
> >>> Great info ... the most suspicious between v4.12 and v4.13-rc5 is the
> >>> series with dcdca5fed5f6 ("x86: kvm: mmu: make spte mmio mask more
> >>> explicit"), does reverting it help?
> >>>
> >>> `git revert ce00053b1cfca312c22e2a6465451f1862561eab~1..995f00a619584e65e53eff372d9b73b121a7bad5`
> >>
> >> Alas, doesn't seem to help.
> >>
> >> I've first installed a Debian stretch guest, the host survived both the
> >> installation and subsequent fooling around. But then I started a win10
> >> guest which splatted as soon as the initial screen.
> >
> > Can you check if disabling THP on the host also fixes it for you?
As in: ?
echo never >/sys/kernel/mm/transparent_hugepage/enabled
echo never >/sys/kernel/mm/transparent_hugepage/defrag
Still reproduces, with or without reverting
ce00053b1cfca312c22e2a6465451f1862561eab~1..995f00a619584e65e53eff372d9b73b121a7bad5
> > I would also try commit 1372324b328cd5dabaef5e345e37ad48c63df2a9 to
> > identify whether it was caused by a KVM change in 4.13 or something
> > else.
I've ran different guests for a couple of hours, no explosions. Thus it
looks like updating Cornelia's email address isn't the cause.
Too bad, there's 15k commits between 1372324b and 7f680d7ec315.
> For the OOM testcase, the splat will disappear if disabling THP.
Meow!
--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
⠈⠳⣄⠀⠀⠀⠀
next prev parent reply other threads:[~2017-08-25 13:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 23:13 kvm splat in mmu_spte_clear_track_bits Adam Borowski
2017-08-21 1:26 ` Wanpeng Li
2017-08-21 19:12 ` Adam Borowski
2017-08-21 19:58 ` Radim Krčmář
2017-08-21 22:32 ` Adam Borowski
2017-08-23 12:22 ` Paolo Bonzini
2017-08-24 7:43 ` Wanpeng Li
2017-08-25 13:14 ` Adam Borowski [this message]
2017-08-25 13:40 ` Paolo Bonzini
2017-08-27 12:35 ` Adam Borowski
2017-08-28 15:26 ` Bernhard Held
2017-08-28 16:01 ` Takashi Iwai
2017-08-28 16:07 ` Bernhard Held
2017-08-28 16:17 ` Takashi Iwai
2017-08-28 16:56 ` Nadav Amit
2017-08-29 9:19 ` Bernhard Held
[not found] ` <s5hh8wq8ruy.wl-tiwai@suse.de>
2017-08-29 12:59 ` Adam Borowski
2017-08-29 14:09 ` Andrea Arcangeli
2017-08-29 16:10 ` Linus Torvalds
2017-08-29 18:28 ` Jerome Glisse
2017-08-29 18:34 ` Jerome Glisse
2017-08-29 19:06 ` Linus Torvalds
2017-08-29 19:13 ` Jerome Glisse
2017-08-29 19:38 ` Linus Torvalds
2017-08-29 20:49 ` Andrea Arcangeli
2017-08-29 20:59 ` Linus Torvalds
2017-08-30 8:19 ` Michal Hocko
2017-08-29 15:53 ` Nadav Amit
2017-08-29 12:57 ` Mike Galbraith
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=20170825131419.r5lzm6oluauu65nx@angband.pl \
--to=kilobyte@angband.pl \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
/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).