From: David Gibson <david@gibson.dropbear.id.au>
To: alarson@ddci.com
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] Determining interest in PPC e500spin, yield, and openpic patches
Date: Wed, 15 Jun 2016 14:17:57 +1000 [thread overview]
Message-ID: <20160615041757.GI4882@voom.fritz.box> (raw)
In-Reply-To: <OF0C52A6C2.AC06C8D6-ON86257FD1.007B3DE1-86257FD1.007F1F64@ddci.com>
[-- Attachment #1: Type: text/plain, Size: 2794 bytes --]
On Mon, Jun 13, 2016 at 06:08:30PM -0500, alarson@ddci.com wrote:
> We've used older versions of QEMU for several years as a virtual
> target for our OS. Many thanks to the community for providing this
> platform.
Hi,
Thanks for your interest.
> We've been working to get our OS running under QEMU 2.x and have
> identified a few bugs in QEMU, have made some enhancements, and are
> still tracking down some other curious behaviors. I'm looking for
> some guidance as to how, and whether, you'd like patches for the
> following.
Always interested in bug fixes. The e500 support probably doesn't get
a whole lot of attention these days, but you're proof that there are
at least a few people who care.
> 1. There is a defect in ppce500_spin.c:spin_kick() that creates an
> incorrectly sized TLB entry. This was reported as bug
> https://bugs.launchpad.net/qemu/+bug/1587535 I can provide a
> patch if desired.
Absolutely.
> 2. We have implemented the PPC "yield" instruction. I can provide a
> patch if desired.
Sounds good.
> 3. We're working on support for openpic timers. We're not finished,
> but it would be helpful to know if a patch is desired or if we
> should expect to maintain the changes independently.
I don't see a reason we wouldn't want it, unless it's horribly
invasive. By all means post patches, and I'll review as best I can.
> 4. We're currently tracking down why in our e500 (both unicore and
> multi-core) PPC QEMU 2.5 guest (x86 host), that with interrupts
> disabled, after enabling the decrementer and issuing a "wait"
> instruction QEMU continues to "busy loop", consuming an entire host
> CPU doing apparently nothing. As expected, issuing a "wait" prior
> to enabling the decrementer leaves the host process idle. We found
> the bug in the PPC "wait" instruction implementation that was
> independently reported and resolved last week, but that did not fix
> the problem. We also have our OS running on the g3beige and using
> MSR.POW which causes the host to "sleep", but we are having no joy
> with e500 and "wait". Any pointers would be appreciated. When we
> find something we'll report back.
Ok.
So, patches for ppc related code should be sent to myself and Alex
Graf <agraf@suse.de>, co-maintainers for the target-ppc and related
code. You should CC both qemu-ppc@nongnu.org and
qemu-devel@nongnu.org.
I have a (frequently rebased) git tree where I stage ppc patches at:
https://github.com/dgibson/qemu/tree/ppc-for-2.7
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-15 4:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 23:08 [Qemu-devel] Determining interest in PPC e500spin, yield, and openpic patches alarson
2016-06-14 19:09 ` [Qemu-devel] [Qemu-ppc] " Mark Cave-Ayland
2016-06-15 4:17 ` David Gibson [this message]
2016-06-15 20:12 ` alarson
2016-06-16 6:25 ` Thomas Huth
2016-06-17 22:01 ` alarson
2016-06-16 6:37 ` David Gibson
2016-06-16 6:47 ` Thomas Huth
2016-06-18 0:50 ` [Qemu-devel] PPC e500spin pir improperly initialized alarson
2016-06-20 14:01 ` Thomas Huth
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=20160615041757.GI4882@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=alarson@ddci.com \
--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 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.