linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Chang-Ho Cho <changho.cho11@gmail.com>
Cc: jgross@suse.com, linux-kernel@vger.kernel.org, mhocko@suse.com,
	peterz@infradead.org
Subject: Re: [PATCH v3 3/4] kernel/smp: add more data to CSD lock debugging
Date: Tue, 16 Aug 2022 08:58:41 -0700	[thread overview]
Message-ID: <20220816155841.GD2125313@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <AEF6AAF1-0529-4661-AA6D-F9E41CE9DA44@gmail.com>

On Tue, Aug 16, 2022 at 07:53:49PM +0900, Chang-Ho Cho wrote:
> Hello, 
> 
> Google search brought me into this thread.  May I have update on the progress of this issue? Has anyone find root cause, solution or workaround?
> How can I get more about the problem?
> Windows 2008 R2 VM experiencing hang on QEMU-kvm with IPI handling issue. 

Here is a blog entry describing the bug that was causing me trouble:

https://paulmck.livejournal.com/62071.html

But although this appeared to be an IPI-loss problem, it was in fact
an interrupt storm.

Juergen, who you CCed, located a race-condition issue with a non-KVM
hypervisor, if I recall correctly.

Of course, much depends on the exact versions of your various OSes
and firmware.  One useful trick is to look for fixes since whichever
version of Linux you are using, and to backport those.  Also, for issues
with Windows, you are likely better served asking elsewhere.  Since you
are asking here, I am assuming that you have somehow proven that the
interrupt is being lost in KVM or QEMU rather than in the Windows guest.

Please note that observing the hang on QEMU/KVM but not on bare metal
is insufficient, given that the difference in timing can dramatically
change the probability of bugs occuring.

							Thanx, Paul

  reply	other threads:[~2022-08-16 16:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-16 10:53 [PATCH v3 3/4] kernel/smp: add more data to CSD lock debugging Chang-Ho Cho
2022-08-16 15:58 ` Paul E. McKenney [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-02  6:28 [PATCH v3 0/4] kernel/smp.c: add more " Juergen Gross
2021-03-02  6:28 ` [PATCH v3 3/4] kernel/smp: add more data to " Juergen Gross
2021-03-24 10:18   ` Jürgen Groß
2021-03-30 17:33     ` Paul E. McKenney
2021-04-02 15:46       ` Juergen Gross
2021-04-02 16:11         ` Paul E. McKenney
2021-04-05  7:37           ` Juergen Gross
2021-04-05 15:29             ` Paul E. McKenney

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=20220816155841.GD2125313@paulmck-ThinkPad-P17-Gen-1 \
    --to=paulmck@kernel.org \
    --cc=changho.cho11@gmail.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=peterz@infradead.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).