From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu-system-ppc problem with PVR access from user space
Date: Fri, 2 Nov 2007 16:46:10 -0400 [thread overview]
Message-ID: <20071102204610.GA14306@caradoc.them.org> (raw)
In-Reply-To: <1194020639.8327.47.camel@jma4.dev.netgem.com>
On Fri, Nov 02, 2007 at 05:23:59PM +0100, Jocelyn Mayer wrote:
> No, it's not accidental. An application accessing priviledged SPR,
> including the PVR, is likely to be buggy. I checked in the kernel
> (2.6.23), trapping the mfpvr instruction is a huge bug because it breaks
> the virtualisation features of the PowerPC architecture. Application
> like mol will suffer of this, not being able to pretend the virtualized
> CPU is not the same as the host CPU. The PowerPC architecture has been
> designed to be fully virtualisable but the vanilla Linux kernel breaks
> this useful feature. The bug is then to be fixed in the kernel (and the
> glibc if it really uses mfpvr).
I suggest you take this up with the PowerPC kernel maintainers, which
might work, instead of making QEMU noisy about it; the people using
QEMU don't care, and they'll just disable the warning. It wasn't
an accidental decision on the kernel maintainers' part either.
I don't see the PVR read in current glibc, but I thought it was there;
I don't remember exactly what happened.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-11-02 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 13:04 [Qemu-devel] qemu-system-ppc problem with PVR access from user space Jason Wessel
2007-11-02 13:38 ` J. Mayer
2007-11-02 13:57 ` Jason Wessel
2007-11-02 16:23 ` Jocelyn Mayer
2007-11-02 20:46 ` Daniel Jacobowitz [this message]
2007-11-02 22:10 ` J. Mayer
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=20071102204610.GA14306@caradoc.them.org \
--to=drow@false.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.