All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Jesse Millwood <jmillwood@masten.aero>
Cc: David Gibson <dgibson@redhat.com>,
	Daniel Henrique Barboza <danielhb413@gmail.com>,
	"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: Help with ppc e500 tlb usage
Date: Fri, 21 Jan 2022 18:57:32 +0100	[thread overview]
Message-ID: <f7fc4a74-2f20-451e-6a4f-d89c395c24ff@kaod.org> (raw)
In-Reply-To: <SA1P110MB1293AF07B83EE30F41B8DD58B05B9@SA1P110MB1293.NAMP110.PROD.OUTLOOK.COM>

> Thanks for the background info Cédric, I wasn't aware of the MMUv2. I see now that in target/ppc/cpu_init.c the e500v2 and e5500 have the same mmu_model, the POWREPC_MMU_BOOKE206.
> I'd like to be able to set the initial tlb entry size from the platform definition by indicating the size in kib. I'll just use the 2^TSIZE then.

Well, the approach of adding a class attribute and for a new machine
is the right one.
>> The e500 only supports the following page sizes:
>>
>>              0b0001 4KB
>>              0b0010 16KB
>>              0b0011 64KB
>>              0b0100 256KB
>>              0b1011 4GB
>>              0b0101 1MB
>>              0b0110 4MB
>>              0b0111 16MB
>>              0b1000 64MB
>>              0b1001 256MB
>>              0b1010 1GB
>>
> 
> Is that how much the emulated e500 supports? The E500 Core Reference manual states that it supports up to 4GiB.

Yes the list is out of order ! :)

Thanks,

C.


  reply	other threads:[~2022-01-21 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PH1P110MB12849EB7B10C757A6B9FEA4FB0589@PH1P110MB1284.NAMP110.PROD.OUTLOOK.COM>
2022-01-21 12:17 ` Help with ppc e500 tlb usage Cédric Le Goater
2022-01-21 17:47   ` Jesse Millwood
2022-01-21 17:57     ` Cédric Le Goater [this message]
2022-01-21 18:38       ` [EXT] - " Jesse Millwood

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=f7fc4a74-2f20-451e-6a4f-d89c395c24ff@kaod.org \
    --to=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=dgibson@redhat.com \
    --cc=jmillwood@masten.aero \
    --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.