All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Gonglei <arei.gonglei@huawei.com>, qemu-devel@nongnu.org
Cc: famz@redhat.com, peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] [PATCH 0/3] memory: some little optimzation
Date: Mon, 9 May 2016 13:41:49 +0200	[thread overview]
Message-ID: <5730777D.4070606@redhat.com> (raw)
In-Reply-To: <1461123261-15408-1-git-send-email-arei.gonglei@huawei.com>



On 20/04/2016 05:34, Gonglei wrote:
> Please see the details in each patch.
> 
> Gonglei (3):
>   memory: drop find_ram_block()
>   exec: adjuest rcu_read_lock requiement
>   memory: pass RAMBlock as a agrument

Hi,

patches 1 and 2 look good.  Please send v2 according to Fam remarks.

For patch 3, I think it's okay if memory.c touches block->fd directly.
Then the functions can be just removed.  I have a patch pending for 2.7
that I'll send in the next weeks.

Thanks,

Paolo

  parent reply	other threads:[~2016-05-09 11:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  3:34 [Qemu-devel] [PATCH 0/3] memory: some little optimzation Gonglei
2016-04-20  3:34 ` [Qemu-devel] [PATCH 1/3] memory: drop find_ram_block() Gonglei
2016-04-29  7:48   ` Fam Zheng
2016-04-29  8:57     ` Gonglei (Arei)
2016-04-20  3:34 ` [Qemu-devel] [PATCH 2/3] exec: adjuest rcu_read_lock requiement Gonglei
2016-04-29  7:56   ` Fam Zheng
2016-04-29  8:59     ` Gonglei (Arei)
2016-04-20  3:34 ` [Qemu-devel] [PATCH 3/3] memory: pass RAMBlock as a agrument Gonglei
2016-04-29  8:06   ` Fam Zheng
2016-04-29  9:03     ` Gonglei (Arei)
2016-05-09 11:41 ` Paolo Bonzini [this message]
2016-05-10  2:05   ` [Qemu-devel] [PATCH 0/3] memory: some little optimzation Gonglei (Arei)

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=5730777D.4070606@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=famz@redhat.com \
    --cc=peter.huangpeng@huawei.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.