From: Peter Maydell <peter.maydell@linaro.org>
To: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Bug 1363641 <1363641@bugs.launchpad.net>
Subject: Re: [Qemu-devel] [Bug 1363641] Re: Build of v2.1.0 fails on armv7l due to undeclared __NR_select
Date: Tue, 23 Sep 2014 13:27:11 +0100 [thread overview]
Message-ID: <CAFEAcA9goOQudLHw2Sby34gePzwQBB+ZB0uFM2Oce5tNXw2f-w@mail.gmail.com> (raw)
In-Reply-To: <54212E62.8000405@linux.vnet.ibm.com>
On 23 September 2014 09:25, Michael R. Hines <mrhines@linux.vnet.ibm.com> wrote:
> I could use some advice from the community on this: In particular, I have
> *zero* 32-bit machine to
> fix this on........ now, I could easily create a 32-bit machine, but I
> simply don't have any RDMA hardware
> for which to run the 32-bit virtual machine against.
>
> So, what are my options? Can I just submit a patch that completely disables
> RDMA in 32-bit environments?
That's probably better than failing to compile. You might want to
at least shake out the compile errors so you can figure out if
your protocol itself has word-size issues or if it's just the
implementation that needs fixing.
I assume there's nothing inherent to RDMA that mandates 64 bit...
-- PMM
next prev parent reply other threads:[~2014-09-23 12:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-31 11:30 [Qemu-devel] [Bug 1363641] [NEW] Build of v2.1.0 fails on armv7l due to undeclared __NR_select Karl-Philipp Richter
2014-08-31 11:30 ` [Qemu-devel] [Bug 1363641] " Karl-Philipp Richter
2014-08-31 11:30 ` Karl-Philipp Richter
2014-08-31 12:06 ` Karl-Philipp Richter
2014-08-31 17:37 ` Peter Maydell
2014-08-31 18:58 ` Peter Maydell
2014-09-08 18:09 ` Dr. David Alan Gilbert
2014-09-23 8:25 ` Michael R. Hines
2014-09-23 12:27 ` Peter Maydell [this message]
2014-09-23 8:25 ` Michael R. Hines
2014-09-07 12:09 ` Karl-Philipp Richter
2014-10-22 7:31 ` Eduardo Otubo
2014-10-22 10:01 ` Peter Maydell
2014-11-12 10:02 ` Eduardo Otubo
2014-12-01 7:12 ` Ben Gelb
2014-12-09 9:36 ` Eduardo Otubo
2014-12-19 17:08 ` Eduardo Otubo
2015-03-17 11:06 ` Eduardo Otubo
2016-06-23 7:59 ` T. 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=CAFEAcA9goOQudLHw2Sby34gePzwQBB+ZB0uFM2Oce5tNXw2f-w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=1363641@bugs.launchpad.net \
--cc=mrhines@linux.vnet.ibm.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 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).