Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Amit Machhiwal <amachhiw@linux.ibm.com>
To: Anushree Mathur <anushree.mathur@linux.ibm.com>
Cc: Vaibhav Jain <vaibhav@linux.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
	kvm-ppc@vger.kernel.org,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Anushree Mathur <anushree.mathur@linux.vnet.ibm.com>
Subject: Re: [PATCH] KVM: PPC: Book3S HV nestedv2: Don't drop pending doorbell across L2 entry
Date: Wed, 19 Aug 2026 16:42:27 +0530	[thread overview]
Message-ID: <20260819163954.3b08c1c2-55-amachhiw@linux.ibm.com> (raw)
In-Reply-To: <aceec38a-7405-4020-b682-5a8c31af30f9@linux.ibm.com>

On 2026/08/19 04:32 PM, Anushree Mathur wrote:
> 
> 

<...snip...>

> 
> b) Even after applying the patch also it is giving same softlockup issue as
> mentioned above:

Hi Anushree,

There was a v2 of this patch sent here:

  https://lore.kernel.org/all/20260812034628.1122115-1-vaibhav@linux.ibm.com/

Did you get a chance to test it? Could you verify if the issue persists
with the v2 as well?

Thanks,
Amit

> Though I have enough vcpus and memory on the guest (16 vcpus , 13Gi of
> memory)  and ample amount of memory and cpus
> present on host still these softlockups are happening after applying the
> patch too. I tried reducing stress also on the guest
> but still this issue is seen.
> 
> stress-ng --cpu 4 --vm 2 --vm-bytes 1G --hdd 2 --hdd-bytes 1G --sched other
> --timeout 3600000s
> 
> If you are planning to send next version of this patch,
> Please do add my reported-by:
> Reported-by: Anushree Mathur <anushree.mathur@linux.ibm.com>
> 

  reply	other threads:[~2026-08-19 11:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  3:44 [PATCH] KVM: PPC: Book3S HV nestedv2: Don't drop pending doorbell across L2 entry Vaibhav Jain
2026-08-03  3:58 ` sashiko-bot
2026-08-10 11:23 ` Gautam Menghani
2026-08-11  5:23   ` Gautam Menghani
2026-08-15  0:46 ` kernel test robot
2026-08-19 11:02 ` Anushree Mathur
2026-08-19 11:12   ` Amit Machhiwal [this message]
2026-08-19 17:43     ` Anushree Mathur

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=20260819163954.3b08c1c2-55-amachhiw@linux.ibm.com \
    --to=amachhiw@linux.ibm.com \
    --cc=anushree.mathur@linux.ibm.com \
    --cc=anushree.mathur@linux.vnet.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=vaibhav@linux.ibm.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