From: Yong Huang <yong.huang@smartx.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, Andrei Gudkov <gudkov.andrei@huawei.com>,
"alloc . young" <alloc.young@outlook.com>,
Juan Quintela <quintela@redhat.com>, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>
Subject: Re: [PULL 0/3] Dirty page rate and dirty page limit 20230828 patches
Date: Wed, 30 Aug 2023 00:30:07 +0800 [thread overview]
Message-ID: <CAK9dgmai9Q0cSYudyM8PBb1AZyxcv6G6BTrRAeJL2EaaR8CNUg@mail.gmail.com> (raw)
In-Reply-To: <CAJSP0QXLticPp0DOS=7bYQf0R0MiYpRXYu_dCRE9JVUbZd2nsw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2273 bytes --]
On Tue, Aug 29, 2023 at 4:01 AM Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Mon, 28 Aug 2023 at 10:36, Hyman Huang <yong.huang@smartx.com> wrote:
> >
> > From: Hyman <yong.huang@smartx.com>
> >
> > 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
>
> Hi,
> This is not a signed tag. Please use "git tag -s" so the tag is signed
> with your GPG key.
>
> I also noticed that this pull request email thread only has a cover
> letter. Please also send the individual patches along with the pull
> request email. This makes it easier for people to reply if they have
> comments about a patch.
>
> After pushing a signed tag, please send the pull request again with
> "PULL v2" in the subject line. Thanks!
>
Sorry for not noticing this earlier and I have sent a pull request with
"PULL"
in the subject line instead of "PULL v3" that you mentioned above, please
ping me if PULL request resending is required indeed.
Yong
> Thanks,
> Stefan
>
> >
> > 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 apply.
> >
> > 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(-)
> >
> > --
> > 1.8.3.1
> >
> >
>
--
Best regards
[-- Attachment #2: Type: text/html, Size: 4625 bytes --]
next prev parent reply other threads:[~2023-08-29 16:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 14:32 [PULL 0/3] Dirty page rate and dirty page limit 20230828 patches Hyman Huang
2023-08-28 20:01 ` Stefan Hajnoczi
2023-08-28 20:04 ` Stefan Hajnoczi
2023-08-29 16:30 ` Yong Huang [this message]
2023-08-29 17:31 ` Stefan Hajnoczi
2023-08-30 2:14 ` Yong Huang
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=CAK9dgmai9Q0cSYudyM8PBb1AZyxcv6G6BTrRAeJL2EaaR8CNUg@mail.gmail.com \
--to=yong.huang@smartx.com \
--cc=alloc.young@outlook.com \
--cc=gudkov.andrei@huawei.com \
--cc=leobras@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.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).