From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: Isaku Yamahata <yamahata@private.email.ne.jp>,
quintela@redhat.com, qemu-devel@nongnu.org, owasserm@redhat.com,
mrhines@us.ibm.com, pbonzini@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/2] rdma: simplify qemu_rdma_register_and_get_keys()
Date: Fri, 20 Sep 2013 13:44:33 -0400 [thread overview]
Message-ID: <523C8981.9030701@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130920165936.GQ16551@valinux.co.jp>
On 09/20/2013 12:59 PM, Isaku Yamahata wrote:
> On Wed, Sep 18, 2013 at 11:01:16AM -0400, Michael R. Hines wrote:
>> The value of chunk_end changes based on whether or not the value of
>> block->is_ram_block is true of false.
> When is block->is_ram_block set to false?
> Looking at __qemu_rdma_add_block() and qemu_rdma_init_ram_blocks(),
> is_ram_block seems to be always set to true because local->init = false
> when __qemu_rdma_add_block() is called.
That's correct, but I have other patches (not yet posted)
that depend on block->is_ram_block.
Please don't delete it =)
- Michael
next prev parent reply other threads:[~2013-09-20 17:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 2:32 [Qemu-devel] [PATCH 1/2] rdma: constify ram_chunk_{index, start, end} Isaku Yamahata
2013-09-04 2:32 ` [Qemu-devel] [PATCH 2/2] rdma: simplify qemu_rdma_register_and_get_keys() Isaku Yamahata
2013-09-18 13:00 ` Juan Quintela
2013-09-18 15:01 ` Michael R. Hines
2013-09-20 16:59 ` Isaku Yamahata
2013-09-20 17:44 ` Michael R. Hines [this message]
2013-09-18 12:55 ` [Qemu-devel] [PATCH 1/2] rdma: constify ram_chunk_{index, start, end} Juan Quintela
2013-09-18 14:28 ` Michael R. Hines
2013-09-20 7:55 ` Isaku Yamahata
2013-09-20 14:11 ` Michael R. Hines
2013-09-24 16:36 ` Juan Quintela
2013-09-24 17:21 ` Michael R. Hines
2013-09-24 17:38 ` Juan Quintela
2013-09-24 17:44 ` Michael R. Hines
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=523C8981.9030701@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=mrhines@us.ibm.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=yamahata@private.email.ne.jp \
--cc=yamahata@valinux.co.jp \
/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.