From: Paolo Bonzini <pbonzini@redhat.com>
To: Adam Borowski <kilobyte@angband.pl>, Wanpeng Li <kernellwp@gmail.com>
Cc: "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:40:50 +0200 [thread overview]
Message-ID: <0a85df4b-ca0a-7e70-51dc-90bd1c460c85@redhat.com> (raw)
In-Reply-To: <20170825131419.r5lzm6oluauu65nx@angband.pl>
On 25/08/2017 15:14, Adam Borowski wrote:
>>> 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.
So:
- 4.12 works
- 1372324b328cd5dabaef5e345e37ad48c63df2a9 works
- 4.13-rc6 fails
The next ones to test are going to be
c136b84393d4e340e1b53fc7f737dd5827b19ee5 and 4.13-rc1.
This can be a starting point for bisection or pointing the finger at
someone else.
next prev parent reply other threads:[~2017-08-25 13:41 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
2017-08-25 13:40 ` Paolo Bonzini [this message]
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=0a85df4b-ca0a-7e70-51dc-90bd1c460c85@redhat.com \
--to=pbonzini@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kilobyte@angband.pl \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.