From: Hyman Huang <yong.huang@smartx.com> To: qemu-devel@nongnu.org Cc: Hyman Huang <yong.huang@smartx.com> Subject: [PULL 0/3] Dirty page rate and dirty page limit 20230829 patches Date: Tue, 29 Aug 2023 01:19:19 +0800 [thread overview] Message-ID: <cover.1693241678.git.yong.huang@smartx.com> (raw) Merge tag 'pull-target-arm-20230824' of https://git.linaro.org/people/pmaydell/qemu-arm into staging (2023-08-24 10:08:33 -0400) are available in the Git repository at: https://github.com/newfriday/qemu.git tags/dirtylimit-dirtyrate-fixes-pull-request for you to fetch changes up to e424d9f7e749c84de4a6ce532981271db1c14b23: migration/dirtyrate: Fix precision losses and g_usleep overshoot (2023-08-28 21:03:58 +0800) ---------------------------------------------------------------- Dirty page limit and dirty page rate PULL request Hi, this is the fix for dirty page limit and dirty page rate. Please ignore the previous PULL request that accidentally failed to send and apply this patchset. Thanks, Yong. ---------------------------------------------------------------- Andrei Gudkov (1): migration/dirtyrate: Fix precision losses and g_usleep overshoot alloc.young (2): softmmu: Fix dirtylimit memory leak softmmu/dirtylimit: Convert free to g_free migration/dirtyrate.c | 10 ++++++++-- softmmu/dirtylimit.c | 26 ++++++++++++-------------- 2 files changed, 20 insertions(+), 16 deletions(-) -- 2.39.1
WARNING: multiple messages have this Message-ID (diff)
From: Hyman Huang <yong.huang@smartx.com> To: qemu-devel@nongnu.org Cc: Hyman Huang <yong.huang@smartx.com> Subject: [PULL 0/3] Dirty page rate and dirty page limit 20230829 patches Date: Tue, 29 Aug 2023 01:32:49 +0800 [thread overview] Message-ID: <cover.1693241678.git.yong.huang@smartx.com> (raw) Message-ID: <20230828173249.Tu-CtA0qhgtvKd75nAWQ_-C4r5dgz-1NgpP_djYAFUQ@z> (raw) The following changes since commit 50e7a40af372ee5931c99ef7390f5d3d6fbf6ec4: Merge tag 'pull-target-arm-20230824' of https://git.linaro.org/people/pmaydell/qemu-arm into staging (2023-08-24 10:08:33 -0400) are available in the Git repository at: https://github.com/newfriday/qemu.git tags/dirtylimit-dirtyrate-fixes-pull-request for you to fetch changes up to e424d9f7e749c84de4a6ce532981271db1c14b23: migration/dirtyrate: Fix precision losses and g_usleep overshoot (2023-08-28 21:03:58 +0800) ---------------------------------------------------------------- Dirty page limit and dirty page rate PULL request Hi, this is the fix for dirty page limit and dirty page rate. Please ignore the previous PULL requests that accidentally failed to send and apply this patchset. :) Thanks, Yong. ---------------------------------------------------------------- Andrei Gudkov (1): migration/dirtyrate: Fix precision losses and g_usleep overshoot alloc.young (2): softmmu: Fix dirtylimit memory leak softmmu/dirtylimit: Convert free to g_free migration/dirtyrate.c | 10 ++++++++-- softmmu/dirtylimit.c | 26 ++++++++++++-------------- 2 files changed, 20 insertions(+), 16 deletions(-) -- 2.39.1
next reply other threads:[~2023-08-28 17:21 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-28 17:19 Hyman Huang [this message] 2023-08-28 17:19 ` [PULL 1/3] softmmu: Fix dirtylimit memory leak Hyman Huang 2023-08-28 17:32 ` Hyman Huang 2023-08-28 17:19 ` [PULL 2/3] softmmu/dirtylimit: Convert free to g_free Hyman Huang 2023-08-28 17:32 ` Hyman Huang 2023-08-28 17:19 ` [PULL 3/3] migration/dirtyrate: Fix precision losses and g_usleep overshoot Hyman Huang 2023-08-28 17:32 ` Hyman Huang 2023-08-28 17:32 ` [PULL 0/3] Dirty page rate and dirty page limit 20230829 patches Hyman Huang -- strict thread matches above, loose matches on Subject: below -- 2023-08-29 15:29 Hyman Huang 2023-08-30 16:22 ` 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=cover.1693241678.git.yong.huang@smartx.com \ --to=yong.huang@smartx.com \ --cc=qemu-devel@nongnu.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: linkBe 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).