From: Qian Cai <cai@lca.pw>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Elver Marco <elver@google.com>,
"paul E. McKenney" <paulmck@kernel.org>,
kasan-dev <kasan-dev@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Subject: Re: KCSAN + KVM = host reset
Date: Wed, 8 Apr 2020 17:29:18 -0400 [thread overview]
Message-ID: <017E692B-4791-46AD-B9ED-25B887ECB56B@lca.pw> (raw)
In-Reply-To: <fb39d3d2-063e-b828-af1c-01f91d9be31c@redhat.com>
> On Apr 8, 2020, at 5:25 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 08/04/20 22:59, Qian Cai wrote:
>> Running a simple thing on this AMD host would trigger a reset right away.
>> Unselect KCSAN kconfig makes everything work fine (the host would also
>> reset If only "echo off > /sys/kernel/debug/kcsan” before running qemu-kvm).
>
> Is this a regression or something you've just started to play with? (If
> anything, the assembly language conversion of the AMD world switch that
> is in linux-next could have reduced the likelihood of such a failure,
> not increased it).
I don’t remember I had tried this combination before, so don’t know if it is a
regression or not.
next prev parent reply other threads:[~2020-04-08 21:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 20:59 KCSAN + KVM = host reset Qian Cai
2020-04-08 21:25 ` Paolo Bonzini
2020-04-08 21:29 ` Qian Cai [this message]
2020-04-09 7:03 ` Marco Elver
2020-04-09 15:10 ` Qian Cai
2020-04-09 15:22 ` Marco Elver
2020-04-09 15:30 ` Qian Cai
2020-04-09 16:03 ` Marco Elver
2020-04-09 21:28 ` Qian Cai
2020-04-09 23:00 ` Qian Cai
2020-04-10 9:47 ` Marco Elver
2020-04-10 11:25 ` Qian Cai
2020-04-10 11:35 ` Marco Elver
2020-04-10 15:50 ` Qian Cai
2020-04-10 16:04 ` Paolo Bonzini
2020-04-10 16:06 ` Sean Christopherson
2020-04-10 19:57 ` Qian Cai
2020-04-13 8:35 ` Marco Elver
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=017E692B-4791-46AD-B9ED-25B887ECB56B@lca.pw \
--to=cai@lca.pw \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=pbonzini@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).