From: Riku Voipio <riku.voipio@iki.fi>
To: Martin Mohring <martinmohring@linuxfoundation.org>
Cc: "Jan-Simon Möller" <jsmoeller@linuxfoundation.org>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: QEMU: current user mode breakage
Date: Tue, 4 May 2010 17:27:20 +0300 [thread overview]
Message-ID: <20100504142720.GA13644@afflict.kos.to> (raw)
In-Reply-To: <4BDAA64F.70509@linuxfoundation.org>
On Fri, Apr 30, 2010 at 11:43:43AM +0200, Martin Mohring wrote:
> not sure how to handle the situation. But since the commit of the new
> memory allocator for QEMU user mode, my test suites show it is broken.
The "0 sized write" patch still isn't applied upstream. Is that the issue
(eg visible by ldconfig.real not working) for you, or is "everything broken"
even with that patch applied?
Just run ltp tests without any noticable regressions on debian/armel/sid.
No performance slowdown was observerd either.
parent reply other threads:[~2010-05-04 14:27 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4BDAA64F.70509@linuxfoundation.org>]
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=20100504142720.GA13644@afflict.kos.to \
--to=riku.voipio@iki.fi \
--cc=jsmoeller@linuxfoundation.org \
--cc=martinmohring@linuxfoundation.org \
--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).