From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: Vishal Chourasia <vishalc@linux.ibm.com>
Cc: peterz@infradead.org, frederic@kernel.org, npiggin@gmail.com,
mpe@ellerman.id.au, chleroy@kernel.org, sshegde@linux.ibm.com,
amachhiw@linux.ibm.com, vaibhav@linux.ibm.com,
harshpb@linux.ibm.com, gautam@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] KVM: powerpc: Use generic xfer to guest work function
Date: Mon, 3 Aug 2026 12:28:02 +0530 [thread overview]
Message-ID: <178574013459.29744.14268082002008456960.b4-ty@linux.ibm.com> (raw)
In-Reply-To: <20260709092140.1753715-2-vishalc@linux.ibm.com>
On Thu, 09 Jul 2026 14:51:38 +0530, Vishal Chourasia wrote:
> This series fixes a KVM scheduling bug on Book3S HV where a guest VM
> under a cpu.max bandwidth limit can run arbitrarily past its quota and
> then appear frozen for minutes afterwards.
>
> == Problem ==
>
> Since commit 2cd571245b43 ("sched/fair: Add related data structure for
> task based throttle"), merged in v6.18, CFS bandwidth throttling no
> longer dequeues a task directly. Instead it queues a task_work item via
> task_work_add(..., TWA_RESUME), sets TIF_NOTIFY_RESUME, and relies on
> that work running on the return path to actually dequeue the task.
>
> [...]
Applied to powerpc/next.
[1/2] KVM: powerpc: Use generic xfer to guest work function
https://git.kernel.org/powerpc/c/12013e3d4695721ef83b2e32fdfd20e2eb9b0cc9
[2/2] powerpc: enable to run posix cpu timers in task context
https://git.kernel.org/powerpc/c/c2c8844316a12c2e1a3314e4f021815dd7fc7b47
cheers
prev parent reply other threads:[~2026-08-03 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 9:21 [PATCH v4 0/2] KVM: powerpc: Use generic xfer to guest work function Vishal Chourasia
2026-07-09 9:21 ` [PATCH v4 1/2] " Vishal Chourasia
2026-07-09 9:21 ` [PATCH v4 2/2] powerpc: enable to run posix cpu timers in task context Vishal Chourasia
2026-08-03 6:58 ` Madhavan Srinivasan [this message]
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=178574013459.29744.14268082002008456960.b4-ty@linux.ibm.com \
--to=maddy@linux.ibm.com \
--cc=amachhiw@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=frederic@kernel.org \
--cc=gautam@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=sshegde@linux.ibm.com \
--cc=vaibhav@linux.ibm.com \
--cc=vishalc@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