qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Riku Voipio <riku.voipio@iki.fi>
To: Michael Walle <michael@walle.cc>
Cc: Alexander Graf <agraf@suse.de>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user: ppc64: set MSR_CM bit for BookE 2.06 MMU
Date: Tue, 16 Aug 2016 16:41:30 +0300	[thread overview]
Message-ID: <20160816134130.GA19717@beaming.home> (raw)
In-Reply-To: <10394037c57ae9c3f734cd31e93d58a8@walle.cc>

On Tue, Aug 16, 2016 at 03:32:56PM +0200, Michael Walle wrote:
> Am 2016-07-22 17:57, schrieb Alexander Graf:
> >On 07/22/2016 05:18 PM, Michael Walle wrote:
> >>64 bit user mode doesn't work for the e5500 core because the MSR_CM bit
> >>is
> >>not set which enables the 64 bit mode for this MMU model. Memory
> >>addresses
> >>are truncated to 32 bit, which results in "Invalid data memory access"
> >>error messages. Fix it by setting the MSR_CM bit for this MMU model.
> >>
> >>Signed-off-by: Michael Walle <michael@walle.cc>
> >
> >Yup, I guess that's about as smart as we have to be :).
> >
> >
> >Reviewed-by: Alexander Graf <agraf@suse.de>
> 
> ping?

sorry. slipped through - looks good, but do we want this to qemu 2.7,
or is next goot enough?

Riku

  reply	other threads:[~2016-08-16 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22 15:18 [Qemu-devel] [PATCH] linux-user: ppc64: set MSR_CM bit for BookE 2.06 MMU Michael Walle
2016-07-22 15:57 ` Alexander Graf
2016-08-16 13:32   ` Michael Walle
2016-08-16 13:41     ` Riku Voipio [this message]
2016-08-16 13:56       ` Michael Walle
2016-09-21 10:59         ` Michael Walle
2016-09-21 18:41           ` Riku Voipio

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=20160816134130.GA19717@beaming.home \
    --to=riku.voipio@iki.fi \
    --cc=agraf@suse.de \
    --cc=michael@walle.cc \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).