All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: alarson@ddci.com, David Gibson <david@gibson.dropbear.id.au>,
	agraf@suse.de
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] Determining interest in PPC e500spin, yield, and openpic patches
Date: Thu, 16 Jun 2016 08:25:45 +0200	[thread overview]
Message-ID: <57624669.2080205@redhat.com> (raw)
In-Reply-To: <OFB9FC4520.28F3555F-ON86257FD3.006DFC02-86257FD3.006F050A@ddci.com>

 Hi,

On 15.06.2016 22:12, alarson@ddci.com wrote:
[...]
> 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.

Thanks for your patch! However, patches have to follow certain rules
before they can be included in QEMU. Please read through
 http://qemu-project.org/Contribute/SubmitAPatch
to get a basic understanding of these rules first. Especially important
for your patch:

- You need to add a "Signed-off-by" line to the patch description to
  state that you've read and understood http://developercertificate.org/

- Run your patch through scripts/checkpatch.pl and the fix style issue

- Please address only one issue per patch. The issue that you've
  mentioned in the comment should be handled with a separate discussion
  (and a separate patch once there is a solution)

Thanks!

 Thomas

  reply	other threads:[~2016-06-16  6:25 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 [this message]
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=57624669.2080205@redhat.com \
    --to=thuth@redhat.com \
    --cc=agraf@suse.de \
    --cc=alarson@ddci.com \
    --cc=david@gibson.dropbear.id.au \
    --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.