From: ChenLiang <chenliang88@huawei.com>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: quintela@redhat.com, QEMU Trivial <qemu-trivial@nongnu.org>,
Michael Tokarev <mjt@tls.msk.ru>,
dgilbert@redhat.com, QEMU Developers <qemu-devel@nongnu.org>,
owasserm@redhat.com, arei.gonglei@huawei.com
Subject: Re: [Qemu-devel] [PATCH-trivial] arch_init.c: Always be sure that 'encoded_buf' and 'current_buf' are lock protected
Date: Tue, 3 Jun 2014 15:31:32 +0800 [thread overview]
Message-ID: <538D79D4.5000900@huawei.com> (raw)
In-Reply-To: <538C6F98.5070005@gmail.com>
On 2014/6/2 20:35, Chen Gang wrote:
> 'encoded_buf' and 'current_buf' are lock protected during using in
> save_xbzrle_page() in ram_save_page(), and during freeing in
> migration_end().
>
> So recommend to let them lock protected during starting, just like we
> have done to 'cache'.
>
>
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
> ---
> arch_init.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/arch_init.c b/arch_init.c
> index 23044c1..784922c 100644
> --- a/arch_init.c
> +++ b/arch_init.c
> @@ -783,12 +783,12 @@ static int ram_save_setup(QEMUFile *f, void *opaque)
> error_report("Error creating cache");
> return -1;
> }
> - XBZRLE_cache_unlock();
>
> /* We prefer not to abort if there is no memory */
> XBZRLE.encoded_buf = g_try_malloc0(TARGET_PAGE_SIZE);
> if (!XBZRLE.encoded_buf) {
> error_report("Error allocating encoded_buf");
> + XBZRLE_cache_unlock();
> return -1;
> }
>
> @@ -797,8 +797,10 @@ static int ram_save_setup(QEMUFile *f, void *opaque)
> error_report("Error allocating current_buf");
> g_free(XBZRLE.encoded_buf);
> XBZRLE.encoded_buf = NULL;
> + XBZRLE_cache_unlock();
> return -1;
> }
> + XBZRLE_cache_unlock();
>
> acct_clear();
> }
It isn't necessary.
Best regards.
ChenLiang
next prev parent reply other threads:[~2014-06-03 7:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 12:35 [Qemu-devel] [PATCH-trivial] arch_init.c: Always be sure that 'encoded_buf' and 'current_buf' are lock protected Chen Gang
2014-06-03 7:31 ` ChenLiang [this message]
2014-06-03 13:45 ` Chen Gang
2014-06-04 10:01 ` Dr. David Alan Gilbert
2014-06-04 10:49 ` Chen Gang
2014-06-04 8:20 ` Markus Armbruster
2014-06-04 10:32 ` Chen Gang
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=538D79D4.5000900@huawei.com \
--to=chenliang88@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=gang.chen.5i5j@gmail.com \
--cc=mjt@tls.msk.ru \
--cc=owasserm@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=quintela@redhat.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).