From: Takashi Iwai <tiwai@suse.de>
To: Bernhard Held <berny156@gmx.de>
Cc: "Adam Borowski" <kilobyte@angband.pl>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Wanpeng Li" <kernellwp@gmail.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: Mon, 28 Aug 2017 18:17:38 +0200 [thread overview]
Message-ID: <s5h8ti3650d.wl-tiwai@suse.de> (raw)
In-Reply-To: <c709fc41-a15b-2fbb-218a-9e7b8dc33708@gmx.de>
On Mon, 28 Aug 2017 18:07:37 +0200,
Bernhard Held wrote:
>
> On 08/28/2017 at 06:01 PM, Takashi Iwai wrote:
> > On Mon, 28 Aug 2017 17:26:05 +0200,
> > Bernhard Held wrote:
> >> I get crashes with Win10 in kvm
> >>
> > Did you get the crash reliably?
> > I've been struggling how to trigger it efficiently, but currently in
> > vain. The memory pressure isn't a single key to trigger it, as it
> > seems...
>
> Yes, I get the crash pretty reliable with Win10 in kvm after 10 to 30 minutes. Some workload in Windows seems to be necessary to trigger the bug.
OK, thanks, it's good to know.
Unfortunately I have no Windows on my machine, so it doesn't work for
me ;) But it implies that rather the workload in VM is likely more
essential than the workload on host.
Takashi
next prev parent reply other threads:[~2017-08-28 16:17 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
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 [this message]
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=s5h8ti3650d.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=berny156@gmx.de \
--cc=kernellwp@gmail.com \
--cc=kilobyte@angband.pl \
--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