From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Thomas Huth <thuth@redhat.com>,
Rebecca Cran <rebecca@bluestop.org>,
qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Yuval Shaia <yuval.shaia@oracle.com>,
Kamil Rytarowski <kamil@netbsd.org>,
Brad Smith <brad@comstyle.com>
Subject: Re: [Qemu-devel] RDMA wrongly detected as being supported on FreeBSD
Date: Sat, 11 Aug 2018 19:47:49 +0300 [thread overview]
Message-ID: <5434c03d-7d03-8255-ea0f-d85ec96ac844@gmail.com> (raw)
In-Reply-To: <1feb3cc1-86ee-f708-6dc7-b9e20a7588ac@redhat.com>
Hi,
On 08/06/2018 11:51 AM, Thomas Huth wrote:
> On 07/28/2018 05:50 AM, Rebecca Cran wrote:
>> On 7/25/18 5:14 AM, Thomas Huth wrote:
>>
>>> Note that the error has been reported to happen on FreeBSD - so I doubt
>>> that this <linux/types.h> header should be here.
>>>
>>> Anyway, our include/standard-headers/linux/types.h is also empty ... so
>>> could you try whether it compiles if you simply remove this #include
>>> line, Rebecca?
>>
>> Sorry for the delay, I'm just getting back to this. Removing the include
>> causes it to fail later on, with:
>>
>> /home/bcran/workspace/qemu/hw/rdma/vmw/pvrdma_cmd.c:60:17: warning:
>> implicit declaration of function 'mremap' is invalid in C99
>> [-Wimplicit-function-declaration]
>> host_virt = mremap(curr_page, 0, length, MREMAP_MAYMOVE);
> OK, thanks for checking. According to
>
> https://www.freebsd.org/cgi/man.cgi?query=mremap&manpath=NetBSD+5.0
>
> that syscall should also be available on FreeBSD. So could you please do
> one more test and see whether it works when you add the following line
> somewhere at the beginning of the file:
>
> #include <sys/mman.h>
It took some time, but I finally have a FreeBSD VM with RDMA enabled.
My findings:
- The RDMA libraries are there, so the flag "RDMA"=yes is set correctly.
- include of <linux/types.h> is not needed, I will remove it.
- In FreeBSD mremap is not implemented in all configurations, it depends
on some SANITIZER_LINUX flag (Linux emulation?), I think;
so pvrdma cannot be compiled. I think we should have a different
QEMU configuration
flag --enable-pvrdma that will specifically check it is not a "bsd"
platform.
I'll send a patch for that too.
Thanks,
Marcel
>
> Thanks,
> Thomas
next prev parent reply other threads:[~2018-08-11 16:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 4:47 [Qemu-devel] RDMA wrongly detected as being supported on FreeBSD Rebecca Cran
2018-07-25 7:32 ` Thomas Huth
2018-07-25 10:48 ` Marcel Apfelbaum
2018-07-25 10:59 ` Dr. David Alan Gilbert
2018-07-26 16:11 ` Marcel Apfelbaum
2018-07-25 11:14 ` Thomas Huth
2018-07-28 3:50 ` Rebecca Cran
2018-08-06 8:51 ` Thomas Huth
2018-08-11 16:47 ` Marcel Apfelbaum [this message]
2018-08-12 8:39 ` Yuval Shaia
2018-08-12 12:10 ` Marcel Apfelbaum
2018-08-15 13:37 ` Kamil Rytarowski
2018-08-16 8:55 ` Marcel Apfelbaum
2018-08-16 9:02 ` Thomas Huth
2018-08-16 9:07 ` Marcel Apfelbaum
2018-07-29 3:08 ` Rebecca Cran
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=5434c03d-7d03-8255-ea0f-d85ec96ac844@gmail.com \
--to=marcel.apfelbaum@gmail.com \
--cc=brad@comstyle.com \
--cc=kamil@netbsd.org \
--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).