From: David Gibson <david@gibson.dropbear.id.au>
To: alarson@ddci.com
Cc: agraf@suse.de, qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] Determining interest in PPC e500spin, yield, and openpic patches
Date: Thu, 16 Jun 2016 16:37:02 +1000 [thread overview]
Message-ID: <20160616063702.GB1642@voom.fritz.box> (raw)
In-Reply-To: <OFB9FC4520.28F3555F-ON86257FD3.006DFC02-86257FD3.006F050A@ddci.com>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
On Wed, Jun 15, 2016 at 01:12:37PM -0700, alarson@ddci.com wrote:
> David Gibson <david@gibson.dropbear.id.au> wrote on 06/14/2016 11:17:57
> PM:
> Aaron Larson <alarson@ddci.com>
>
> AL> 1. There is a defect in ppce500_spin.c:spin_kick() that creates an
> AL> incorrectly sized TLB entry. This was reported as bug
> AL> https://bugs.launchpad.net/qemu/+bug/1587535 I can provide a
> AL> patch if desired.
>
> DG> Absolutely.
>
> OK, I'll start with this one. Let me know if there is anything you'd
> like me to do
> with that bug report.
>
> When e500 PPC is booted multi-core, the non-boot cores are started via
> the spin table. ppce500_spin.c:spin_kick() calls
> mmubooke_create_initial_mapping() to allocate a 64MB TLB entry, but
> the created TLB entry is only 256KB.
>
> The root cause is that the function computing the size of the TLB
> entry, namely booke206_page_size_to_tlb assumes MAS1.TSIZE as defined
> by latter PPC cores, specifically n to the power of FOUR * 1KB. The
> result is then used by mmubooke_create_initial_mapping using
> MAS1_TSIZE_SHIFT, but MAS1_TSIZE_SHIFT is defined assuming TLB entries
> are n to the power of TWO * 1KB. I.e., a difference of shift=7 or
> shift=8.
>
> Simply changing MAS1_TSIZE_SHIFT from 7 to 8 is not appropriate since
> the macro is used elsewhere.
>
> The following patch has a fix for that, and also raises a separate
> issue that I'd be happy to resolve after getting some guidance.
Ok, thanks for sending this, but there are some procedural things
you'll need to check before we can go ahead. We generally prefer
patches to be sent inline, rather than as attachments (it makes adding
review comments much easier), and you'll need to apply a Signed-off-by
line before I could merge it. There are more details on the
procedures for submitting patches at:
http://wiki.qemu.org/Contribute/SubmitAPatch
--
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-16 11:12 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
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 [this message]
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=20160616063702.GB1642@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--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 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).