From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: yuval.shaia@oracle.com, rebecca@bluestop.org, peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH V2] config: split PVRDMA from RDMA
Date: Thu, 16 Aug 2018 18:58:50 +0300 [thread overview]
Message-ID: <9a69b82b-77a3-db58-5fe6-c0f1fccc1aa6@gmail.com> (raw)
In-Reply-To: <e69c3f04-acce-b6e8-7254-22edd5d04e4e@redhat.com>
Hi Thomas,
On 08/16/2018 06:48 PM, Thomas Huth wrote:
> On 08/16/2018 05:16 PM, Marcel Apfelbaum wrote:
>> In some BSD systems RDMA migration is possible while
>> the pvrdma device can't be used because the mremap system call
>> is missing.
>>
>> Signed-off-by: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
>> ---
>> configure | 55 ++++++++++++++++++++++++++++++++++++++++++-
>> hw/rdma/Makefile.objs | 2 +-
>> 2 files changed, 55 insertions(+), 2 deletions(-)
> [...]
>> diff --git a/hw/rdma/Makefile.objs b/hw/rdma/Makefile.objs
>> index 3504c39d21..bd36cbf51c 100644
>> --- a/hw/rdma/Makefile.objs
>> +++ b/hw/rdma/Makefile.objs
>> @@ -1,4 +1,4 @@
>> -ifeq ($(CONFIG_RDMA),y)
>> +ifeq ($(CONFIG_PVRDMA),y)
>> obj-$(CONFIG_PCI) += rdma_utils.o rdma_backend.o rdma_rm.o
>> obj-$(CONFIG_PCI) += vmw/pvrdma_dev_ring.o vmw/pvrdma_cmd.o \
>> vmw/pvrdma_qp_ops.o vmw/pvrdma_main.o
>>
> Again:
Sorry for not seeing the comment earlier.
> Shouldn't the CONFIG_PVRDMA only guard the second line? I thought
> the first list should be fine with CONFIG_RDMA?
Indeed, theoretically the first line can be compiled with CONFIG_RDMA,
however the only code that utilize the first line .o files is the pvrdma
code.
So we will simply have a bigger binary without any reason.
Thanks,
Marcel
> Thomas
next prev parent reply other threads:[~2018-08-16 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 15:16 [Qemu-devel] [PATCH V2] config: split PVRDMA from RDMA Marcel Apfelbaum
2018-08-16 15:43 ` Marcel Apfelbaum
2018-08-16 15:48 ` Thomas Huth
2018-08-16 15:58 ` Marcel Apfelbaum [this message]
2018-08-16 16:00 ` Thomas Huth
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=9a69b82b-77a3-db58-5fe6-c0f1fccc1aa6@gmail.com \
--to=marcel.apfelbaum@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rebecca@bluestop.org \
--cc=thuth@redhat.com \
--cc=yuval.shaia@oracle.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).