From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Hyman Huang <yong.huang@smartx.com>, qemu-devel@nongnu.org
Subject: Re: [PULL 0/2] Dirty page rate and dirty page limit 20231009 patches
Date: Mon, 9 Oct 2023 15:47:06 +0200 [thread overview]
Message-ID: <817dc2a2-c2ee-f836-3333-51789ce3b45e@linaro.org> (raw)
In-Reply-To: <cover.1696855875.git.yong.huang@smartx.com>
Hi Hyman,
On 9/10/23 14:57, Hyman Huang wrote:
> The following changes since commit 2f3913f4b2ad74baeb5a6f1d36efbd9ecdf1057d:
>
> Merge tag 'for_upstream' of https://git.kernel.org/pub/scm/virt/kvm/mst/qemu into staging (2023-10-05 09:01:01 -0400)
>
> are available in the Git repository at:
>
> https://github.com/newfriday/qemu.git tags/dirtylimit-dirtyrate-pull-request-20231009
>
> for you to fetch changes up to 84719f6d0b75448400068adb78d85000e884f0cd:
>
> migration/dirtyrate: use QEMU_CLOCK_HOST to report start-time (2023-10-08 15:06:12 +0800)
>
> ----------------------------------------------------------------
> Dirtylimit and dirtyrate 20231009 patches PULL request
>
> Dirty page rate measurement optimization.
> Please apply, thanks, Yong.
>
> ----------------------------------------------------------------
> Andrei Gudkov via (2):
> migration/calc-dirty-rate: millisecond-granularity period
> migration/dirtyrate: use QEMU_CLOCK_HOST to report start-time
Invalid author Andrei Gudkov via <qemu-devel@nongnu.org> in patches :/
Please correct and repost.
next prev parent reply other threads:[~2023-10-09 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 12:57 [PULL 0/2] Dirty page rate and dirty page limit 20231009 patches Hyman Huang
2023-10-09 12:57 ` [PULL 1/2] migration/calc-dirty-rate: millisecond-granularity period Hyman Huang
2023-10-09 12:57 ` [PULL 2/2] migration/dirtyrate: use QEMU_CLOCK_HOST to report start-time Hyman Huang
2023-10-09 13:47 ` Philippe Mathieu-Daudé [this message]
2023-10-09 14:21 ` [PULL 0/2] Dirty page rate and dirty page limit 20231009 patches Stefan Hajnoczi
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=817dc2a2-c2ee-f836-3333-51789ce3b45e@linaro.org \
--to=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).