From: David Mozes <david.mozes@silk.us>
To: Wei Liu <wei.liu@kernel.org>
Cc: "David Moses" <mosesster@gmail.com>,
"Michael Kelley" <mikelley@microsoft.com>,
"תומר אבוטבול" <tomer432100@gmail.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] x86/hyper-v: guard against cpu mask changes in hyperv_flush_tlb_others()
Date: Sun, 22 Aug 2021 16:25:19 +0000 [thread overview]
Message-ID: <VI1PR0401MB2415F41E0D6B43411779911AF1C39@VI1PR0401MB2415.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20210822152436.mqfwv3xbqfxy33os@liuwe-devbox-debian-v2>
This is not visible since we need a very high load to reproduce.
We have tried a lot but can't achieve the desired load
On our kernel with less load, it is not reproducible as well.
-----Original Message-----
From: Wei Liu <wei.liu@kernel.org>
Sent: Sunday, August 22, 2021 6:25 PM
To: David Mozes <david.mozes@silk.us>
Cc: David Moses <mosesster@gmail.com>; Wei Liu <wei.liu@kernel.org>; Michael Kelley <mikelley@microsoft.com>; תומר אבוטבול <tomer432100@gmail.com>; linux-hyperv@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/hyper-v: guard against cpu mask changes in hyperv_flush_tlb_others()
On Thu, Aug 19, 2021 at 07:55:06AM +0000, David Mozes wrote:
> Hi Wei ,
> I move the print cpumask to other two places after the treatment on the empty mask see below
> And I got the folwing:
>
>
> Aug 19 02:01:51 c-node05 kernel: [25936.562674] Hyper-V: ERROR_HYPERV2: cpu_last=
> Aug 19 02:01:51 c-node05 kernel: [25936.562686] WARNING: CPU: 11 PID: 56432 at arch/x86/include/asm/mshyperv.h:301 hyperv_flush_tlb_others+0x23f/0x7b0
>
> So we got empty on different place on the code .
> Let me know if you need further information from us.
> How you sagest to handle this situation?
>
Please find a way to reproduce this issue with upstream kernels.
Thanks,
Wei.
next prev parent reply other threads:[~2021-08-22 16:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+qYZY3a-FHfWNL2=na6O8TRJYu9kaeyp80VNDxaDTi2EBGoog@mail.gmail.com>
2021-08-06 10:43 ` [PATCH] x86/hyper-v: guard against cpu mask changes in hyperv_flush_tlb_others() Michael Kelley
2021-08-06 17:35 ` David Mozes
[not found] ` <CAHkVu0-ZCXDRZL92d_G3oKpPuKvmY=YEbu9nbx9vkZHnhHFD8Q@mail.gmail.com>
2021-08-06 21:51 ` Michael Kelley
2021-08-07 5:00 ` David Moses
2021-08-17 9:16 ` David Mozes
2021-08-17 11:29 ` Wei Liu
2021-08-19 11:05 ` David Mozes
[not found] ` <CA+qYZY1U04SkyHo7X+rDeE=nUy_X5nxLfShyuLJFzXnFp2A6uw@mail.gmail.com>
[not found] ` <VI1PR0401MB24153DEC767B0126B1030E07F1C09@VI1PR0401MB2415.eurprd04.prod.outlook.com>
2021-08-22 15:24 ` Wei Liu
2021-08-22 16:25 ` David Mozes [this message]
2021-08-22 17:32 ` Wei Liu
[not found] <VI1PR0401MB24150B31A1D63176BBB788D2F1F19@VI1PR0401MB2415.eurprd04.prod.outlook.com>
2021-08-05 18:08 ` Michael Kelley
2020-10-01 1:38 Sasha Levin
2020-10-01 9:40 ` Vitaly Kuznetsov
2020-10-01 11:53 ` Wei Liu
2020-10-01 13:04 ` Sasha Levin
2020-10-03 17:40 ` Michael Kelley
2020-10-05 14:58 ` Wei Liu
2021-01-05 16:59 ` Michael Kelley
2021-01-05 17:10 ` Wei Liu
2021-01-08 15:22 ` Sasha Levin
2020-10-01 13:10 ` Vitaly Kuznetsov
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=VI1PR0401MB2415F41E0D6B43411779911AF1C39@VI1PR0401MB2415.eurprd04.prod.outlook.com \
--to=david.mozes@silk.us \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mosesster@gmail.com \
--cc=tomer432100@gmail.com \
--cc=wei.liu@kernel.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 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).