From: Eric Blake <eblake@redhat.com>
To: Timothy Pearson <tpearson@raptorengineering.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/7] QEMU does not currently support host pages that are larger than guest pages, likely due to glibc using fixed mmap requests.
Date: Mon, 20 Jun 2016 10:39:31 -0600 [thread overview]
Message-ID: <57681C43.3070108@redhat.com> (raw)
In-Reply-To: <1841580212.1359461.1466295316691.JavaMail.zimbra@raptorengineeringinc.com>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
On 06/18/2016 06:15 PM, Timothy Pearson wrote:
> Attempting to use host pages larger than the guest leads to
> alignment errors during ELF load in the best case, and an
> initialization failure inside NPTL in the worst case, causing
> all fork() requests inside the guest to fail.
Long subject line. Try to keep subject lines in the form:
topic: short description
with at most 65 characters (reading 'git shortlog' adds indentation and
commit ids, and you still want the lines to be legible in an 80-column
window).
Improperly threaded; this showed up as its own top-level message instead
of in-reply-to the 0/7 cover letter.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-06-20 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 0:15 [Qemu-devel] [PATCH 2/7] QEMU does not currently support host pages that are larger than guest pages, likely due to glibc using fixed mmap requests Timothy Pearson
2016-06-20 16:39 ` Eric Blake [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-19 0:11 Timothy Pearson
2016-06-19 9:46 ` Peter Maydell
2016-06-19 18:24 ` Richard Henderson
2016-06-20 13:25 ` Peter Maydell
2016-06-22 0:55 ` Richard Henderson
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=57681C43.3070108@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tpearson@raptorengineering.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).