public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Shivam Kumar <shivam.kumar1@nutanix.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, peterx@redhat.com, david@redhat.com,
	quintela@redhat.com, dgilbert@redhat.com, kvm@vger.kernel.org,
	Shaju Abraham <shaju.abraham@nutanix.com>,
	Manish Mishra <manish.mishra@nutanix.com>,
	Anurag Madnawat <anurag.madnawat@nutanix.com>
Subject: Re: [RFC PATCH 1/1] Dirty quota-based throttling of vcpus
Date: Mon, 13 Feb 2023 14:47:54 +0530	[thread overview]
Message-ID: <ae726bee-9bd0-bbbb-c416-0e1762cc57be@nutanix.com> (raw)
In-Reply-To: <8cf78246-d00d-dbab-7e67-0ba09300e6ed@nutanix.com>



On 22/11/22 9:30 am, Shivam Kumar wrote:
> 
> 
> On 21/11/22 5:05 pm, Philippe Mathieu-Daudé wrote:
>> Hi,
>>
>> On 20/11/22 23:54, Shivam Kumar wrote:
>>> +
>>> +void dirty_quota_migration_start(void)
>>> +{
>>> +    if (!kvm_state->dirty_quota_supported) {
>>
>> You are accessing an accelerator-specific variable in an 
>> accelerator-agnostic file, this doesn't sound correct.
>>
>> You might introduce some hooks in AccelClass and implement them in
>> accel/kvm/. See for example gdbstub_supported_sstep_flags() and
>> kvm_gdbstub_sstep_flags().
>>
> Ack.
> 
> Thanks,
> Shivam

Hi Philippe,

I had received a suggestion on the kernel-side patchset to make dirty 
quota a more generic feature and not limit its use to live migration. 
Incorporating this ask might lead to a significant change in the dirty 
quota interface. So, I haven't been able to post the next version of the 
QEMU patchset. I intend to post it once the new proposition looks good 
to the KVM reviewers.

Thanks,
Shivam

  reply	other threads:[~2023-02-13  9:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-20 22:54 [RFC PATCH 0/1] QEMU: Dirty quota-based throttling of vcpus Shivam Kumar
2022-11-20 22:54 ` [RFC PATCH 1/1] " Shivam Kumar
2022-11-21 11:35   ` Philippe Mathieu-Daudé
2022-11-22  4:00     ` Shivam Kumar
2023-02-13  9:17       ` Shivam Kumar [this message]
2022-12-06  5:48 ` [RFC PATCH 0/1] QEMU: " Shivam Kumar
2022-12-06 16:00   ` Peter Xu
2022-12-06 17:29     ` Hyman Huang
2022-12-18 19:12       ` Shivam Kumar
2022-12-19 14:19         ` Hyman Huang

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=ae726bee-9bd0-bbbb-c416-0e1762cc57be@nutanix.com \
    --to=shivam.kumar1@nutanix.com \
    --cc=anurag.madnawat@nutanix.com \
    --cc=david@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=manish.mishra@nutanix.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=shaju.abraham@nutanix.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