From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Laurentiu Palcu <laurentiu.palcu@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3 1/1] qemu: add wrapper for qemu-mips binary
Date: Wed, 03 Oct 2012 12:40:24 +0100 [thread overview]
Message-ID: <1349264424.18301.29.camel@ted> (raw)
In-Reply-To: <1349263406-23095-2-git-send-email-laurentiu.palcu@intel.com>
On Wed, 2012-10-03 at 14:23 +0300, Laurentiu Palcu wrote:
> qemu-mips user emulation binary segfaults when running any kind of
> binary. This is due to a MMU access fault in the virtual CPU. This
> problem has been introduced in qemu when 4GB of vmem were reserved for
> 32-on-64 bit.
>
> This workaround will need to be reverted once the proper fix is found.
>
> [YOCTO #3143]
>
> Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
> ---
> meta/recipes-devtools/qemu/qemu_1.2.0.bb | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-10-03 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 11:23 [PATCH v3 0/1] qemu: add wrapper for qemu-mips binary Laurentiu Palcu
2012-10-03 11:23 ` [PATCH v3 1/1] " Laurentiu Palcu
2012-10-03 11:40 ` Richard Purdie [this message]
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=1349264424.18301.29.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=laurentiu.palcu@intel.com \
--cc=openembedded-core@lists.openembedded.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