From: Markus Armbruster <armbru@redhat.com>
To: Hyman Huang <huangy81@chinatelecom.cn>
Cc: "Eduardo Habkost" <eduardo@habkost.net>,
"David Hildenbrand" <david@redhat.com>,
"Juan Quintela" <quintela@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Peter Xu" <peterx@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v10 3/3] cpus-common: implement dirty page limit on virtual CPU
Date: Thu, 16 Dec 2021 11:23:37 +0100 [thread overview]
Message-ID: <877dc4yhjq.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <a6dc86b7-29c2-fa08-ad16-017d8b1301d9@chinatelecom.cn> (Hyman Huang's message of "Thu, 16 Dec 2021 17:16:55 +0800")
Hyman Huang <huangy81@chinatelecom.cn> writes:
[...]
> So the final format of qmp we conclude are:
>
> case 1: setup vcpu 0 dirty page limit 100MB/s
> set-vcpu-dirty-limit cpu-index=0 dirty-rate=100
>
> case 2: setup all vcpu dirty page limit 100MB/s
> set-vcpu-dirty-limit dirty-rate=100
>
> case 3: cancel vcpu 0 dirty page limit
> cancel-vcpu-dirty-limit cpu-index=0
>
> case 4: cancel all vcpu dirty page limit
> cancel-vcpu-dirty-limit
>
> case 5: query limit infomatioin of all vcpu enabled
> query-vcpu-dirty-limit
>
> And the corresponding hmp format keep the same style:
>
> Is there any advice? :)
Looks okay to me.
next prev parent reply other threads:[~2021-12-16 10:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 11:07 [PATCH v10 0/3] support dirty restraint on vCPU huangy81
2021-12-14 11:07 ` [PATCH v10 1/3] migration/dirtyrate: implement vCPU dirtyrate calculation periodically huangy81
2021-12-23 11:12 ` Peter Xu
2021-12-26 15:58 ` Hyman
2021-12-30 5:01 ` Hyman Huang
2021-12-30 6:34 ` Peter Xu
2021-12-14 11:07 ` [PATCH v10 2/3] cpu-throttle: implement virtual CPU throttle huangy81
2021-12-15 7:15 ` Markus Armbruster
2021-12-15 7:40 ` Hyman Huang
2021-12-24 5:12 ` Peter Xu
2021-12-30 16:36 ` Hyman Huang
2022-01-04 2:32 ` Peter Xu
2022-01-04 3:27 ` Hyman Huang
2022-01-13 16:22 ` Markus Armbruster
2022-01-14 1:30 ` Hyman Huang
2022-01-14 3:35 ` Peter Xu
2021-12-14 11:07 ` [PATCH v10 3/3] cpus-common: implement dirty page limit on virtual CPU huangy81
2021-12-15 7:37 ` Markus Armbruster
2021-12-15 7:56 ` Hyman Huang
2021-12-15 8:09 ` Peter Xu
2021-12-15 8:29 ` Hyman Huang
2021-12-15 10:16 ` Hyman Huang
2021-12-15 13:41 ` Markus Armbruster
2021-12-16 6:22 ` Peter Xu
2021-12-16 9:16 ` Hyman Huang
2021-12-16 10:23 ` Markus Armbruster [this message]
2021-12-24 5:16 ` Peter Xu
2021-12-24 5:14 ` Peter Xu
2021-12-26 16:00 ` Hyman
2021-12-24 5:17 ` [PATCH v10 0/3] support dirty restraint on vCPU Peter Xu
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=877dc4yhjq.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eduardo@habkost.net \
--cc=huangy81@chinatelecom.cn \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=richard.henderson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.