From: Fabiano Rosas <farosas@suse.de>
To: Hyman Huang <yong.huang@smartx.com>, qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Hyman Huang <yong.huang@smartx.com>
Subject: Re: [PATCH 2/6] system/dirtylimit: Drop the reduplicative check
Date: Thu, 19 Oct 2023 16:36:06 -0300 [thread overview]
Message-ID: <87wmvi5rrt.fsf@suse.de> (raw)
In-Reply-To: <b370a33be0a1c393cfcb2552c6305c42463f8156.1697502089.git.yong.huang@smartx.com>
Hyman Huang <yong.huang@smartx.com> writes:
> Checking if dirty limit is in service is done by the
> dirtylimit_query_all function, drop the reduplicative
> check in the qmp_query_vcpu_dirty_limit function.
>
> Signed-off-by: Hyman Huang <yong.huang@smartx.com>
Reviewed-by: Fabiano Rosas <farosas@suse.de>
next prev parent reply other threads:[~2023-10-19 19:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 11:36 [PATCH 0/6] dirtylimit: miscellaneous patches Hyman Huang
2023-10-17 11:36 ` [PATCH 1/6] system/dirtylimit: Fix a race situation Hyman Huang
2023-10-19 19:33 ` Fabiano Rosas
2023-10-17 11:36 ` [PATCH 2/6] system/dirtylimit: Drop the reduplicative check Hyman Huang
2023-10-19 19:36 ` Fabiano Rosas [this message]
2023-10-17 11:36 ` [PATCH 3/6] tests: Add migration dirty-limit capability test Hyman Huang
2023-10-19 20:01 ` Fabiano Rosas
2023-10-17 11:36 ` [PATCH 4/6] tests/migration: Introduce dirty-ring-size option into guestperf Hyman Huang
2023-10-17 11:36 ` [PATCH 5/6] tests/migration: Introduce dirty-limit " Hyman Huang
2023-10-17 11:36 ` [PATCH 6/6] docs/migration: Add the dirty limit section Hyman Huang
2023-10-19 19:57 ` Fabiano Rosas
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=87wmvi5rrt.fsf@suse.de \
--to=farosas@suse.de \
--cc=leobras@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@redhat.com \
--cc=yong.huang@smartx.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).