qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Riku Voipio <riku.voipio@iki.fi>
To: Martin Mohring <martin.mohring@opensuse.org>
Cc: qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 0/6] Multi-level page tables and userland mapping fixes, v3
Date: Mon, 15 Mar 2010 07:45:56 +0000	[thread overview]
Message-ID: <20100315074556.GA1261@afflict.kos.to> (raw)
In-Reply-To: <4B9B9A94.4000700@opensuse.org>

On Sat, Mar 13, 2010 at 03:00:52PM +0100, Martin Mohring wrote:
> I am sorry to bring us all down to earth, we all had wished that this stuff gets finally fixed, but it seems that those patches applied to QEMU master have killed QEMU user mode.
 
sid and maemo userlands work for me like before (64bit and 32bit hosts).

> I am referring to the user mode fixes after commit 0aef4261ac0ec9089ade0e3a92f986cb4ba7317e
> 
> I had QEMU working on PowerPC and ARM in chroots from the Linux versions:
> 
> - Fedora 11 / 12
> - Ubuntu 9.04, 9.10, 10.04
> - Debian 4, 5 and Sid
> 
> for ARM and PowerPC. My host OS is openSUSE 11.2 using a 2.6.31 kernel, or openSUSE 11.1. All machines are 64 Bit machines.
> 
> Now I have the situation that all the listed target chroots fail, except:
> - Fedora 11 / 12 @ ARM

Please try to be more specific. What is killed? what do you mean by 
"chroots fail". qemu segfault? some binary doesn't work that before did?
some syscall doesn't work anymore?

  reply	other threads:[~2010-03-15  7:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10 23:59 [Qemu-devel] [PATCH 0/6] Multi-level page tables and userland mapping fixes, v3 Richard Henderson
2010-03-10 22:33 ` [Qemu-devel] [PATCH 1/6] Move TARGET_PHYS_ADDR_SPACE_BITS to target-*/cpu.h Richard Henderson
2010-03-11 11:11   ` Aurelien Jarno
2010-03-11 15:19     ` Richard Henderson
2010-03-10 22:36 ` [Qemu-devel] [PATCH 2/6] Use TARGET_VIRT_ADDR_SPACE_BITS in h2g_valid Richard Henderson
2010-03-10 22:38 ` [Qemu-devel] [PATCH 3/6] linux-user: Use h2g_valid in qemu_vmalloc Richard Henderson
2010-03-10 23:39 ` [Qemu-devel] [PATCH 4/6] linux-user: Fix mmap_find_vma returning invalid addresses Richard Henderson
2010-03-10 23:53 ` [Qemu-devel] [PATCH 5/6] Implement multi-level page tables Richard Henderson
2010-03-13 22:48   ` Stefan Weil
2010-03-14 15:02     ` Paul Brook
2010-03-14 16:41       ` Aurelien Jarno
2010-03-10 23:57 ` [Qemu-devel] [PATCH 6/6] Fix last page errors in page_check_range and page_set_flags Richard Henderson
2010-03-12 18:51 ` [Qemu-devel] [PATCH 0/6] Multi-level page tables and userland mapping fixes, v3 Paul Brook
2010-03-12 19:26   ` Blue Swirl
2010-03-12 23:28     ` Paul Brook
2010-03-13 12:45   ` Aurelien Jarno
2010-03-13 14:00     ` Martin Mohring
2010-03-15  7:45       ` Riku Voipio [this message]
2010-03-15 12:46         ` Jan-Simon Möller
2010-03-15 14:48           ` Riku Voipio
2010-03-15 15:08             ` Jan-Simon Möller
2010-03-17 11:48               ` Riku Voipio
2010-03-17 14:32                 ` 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=20100315074556.GA1261@afflict.kos.to \
    --to=riku.voipio@iki.fi \
    --cc=aurelien@aurel32.net \
    --cc=martin.mohring@opensuse.org \
    --cc=paul@codesourcery.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).