From: Marc Zyngier <maz@kernel.org>
To: Shivam Kumar <shivam.kumar1@nutanix.com>
Cc: Sean Christopherson <seanjc@google.com>,
pbonzini@redhat.com, james.morse@arm.com,
borntraeger@linux.ibm.com, david@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: [PATCH v7 1/4] KVM: Implement dirty quota-based throttling of vcpus
Date: Sun, 12 Feb 2023 18:02:26 +0000 [thread overview]
Message-ID: <87h6vqlq31.wl-maz@kernel.org> (raw)
In-Reply-To: <4b81ddf6-86ad-ef34-3cec-3fcefc796b1b@nutanix.com>
On Sun, 12 Feb 2023 17:54:30 +0000,
Shivam Kumar <shivam.kumar1@nutanix.com> wrote:
>
>
>
> On 12/02/23 10:39 pm, Marc Zyngier wrote:
> > On Sat, 11 Feb 2023 06:52:02 +0000,
> > Shivam Kumar <shivam.kumar1@nutanix.com> wrote:
> >>
> >>>
> >>> Hi Marc,
> >>>
> >>> I'm proposing this new implementation to address the concern you
> >>> raised regarding dirty quota being a non-generic feature with the
> >>> previous implementation. This implementation decouples dirty quota
> >>> from dirty logging for the ARM64 arch. We shall post a similar
> >>> implementation for x86 if this looks good. With this new
> >>> implementation, dirty quota can be enforced independent of dirty
> >>> logging. Dirty quota is now in bytes and
> >>
> >> Hi Marc,
> >>
> >> Thank you for your valuable feedback so far. Looking forward to your
> >> feedback on this new proposition.
> >
> > I'm not sure what you are expecting from me here. I've explained in
> > great details what I wanted to see, repeatedly. This above says
> > nothing other than "we are going to do *something* that matches your
> > expectations".
> >
> > My answer is, to quote someone else, "show me the code". Until then, I
> > don't have much to add.
> >
> > Thanks,
> >
> > M.
> >
>
> Hi Marc,
>
> I had posted some code in the previous comment. Let me tag you there.
You posted a tiny snippet that is completely out of context.
I took the time to fully review your series and provide extensive
comments. You could, similarly, take the time to post a complete
series for people to review the new proposal.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2023-02-12 18:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 17:05 [PATCH v7 0/4] KVM: Dirty quota-based throttling Shivam Kumar
2022-11-13 17:05 ` [PATCH v7 1/4] KVM: Implement dirty quota-based throttling of vcpus Shivam Kumar
2022-11-14 23:29 ` Yunhong Jiang
2022-11-15 4:48 ` Shivam Kumar
2022-11-17 19:26 ` Marc Zyngier
2022-11-18 9:47 ` Shivam Kumar
2022-11-22 17:46 ` Marc Zyngier
2022-12-06 6:22 ` Shivam Kumar
2022-12-07 16:44 ` Marc Zyngier
2022-12-07 19:53 ` Sean Christopherson
2022-12-08 7:30 ` Shivam Kumar
2022-12-25 16:50 ` Shivam Kumar
2022-12-26 10:07 ` Marc Zyngier
2023-01-07 17:24 ` Shivam Kumar
2023-01-07 21:44 ` Marc Zyngier
2023-01-14 13:07 ` Shivam Kumar
2023-01-15 9:56 ` Marc Zyngier
2023-01-15 14:50 ` Shivam Kumar
2023-01-15 19:13 ` Marc Zyngier
2023-01-29 22:00 ` Shivam Kumar
2023-02-11 6:52 ` Shivam Kumar
2023-02-12 17:09 ` Marc Zyngier
2023-02-12 17:54 ` Shivam Kumar
2023-02-12 18:02 ` Marc Zyngier [this message]
2023-02-12 17:56 ` Shivam Kumar
2022-12-08 7:20 ` Shivam Kumar
2022-11-13 17:05 ` [PATCH v7 2/4] KVM: x86: Dirty " Shivam Kumar
2022-11-15 0:16 ` Yunhong Jiang
2022-11-15 4:55 ` Shivam Kumar
2022-11-15 6:45 ` Yunhong Jiang
2022-11-18 8:51 ` Shivam Kumar
2022-11-13 17:05 ` [PATCH v7 3/4] KVM: arm64: " Shivam Kumar
2022-11-15 0:27 ` Yunhong Jiang
2022-11-15 5:10 ` Shivam Kumar
2022-11-17 20:44 ` Marc Zyngier
2022-11-18 8:56 ` Shivam Kumar
2022-11-13 17:05 ` [PATCH v7 4/4] KVM: selftests: Add selftests for dirty quota throttling Shivam Kumar
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=87h6vqlq31.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=anurag.madnawat@nutanix.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=manish.mishra@nutanix.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shaju.abraham@nutanix.com \
--cc=shivam.kumar1@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;
as well as URLs for NNTP newsgroup(s).