[Qemu-devel] [PATCH for-2.11 0/4] ppc64: add e6500

KONRAD Frederic posted 4 patches 6 years, 8 months ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/1502121048-1816-1-git-send-email-frederic.konrad@adacore.com
Test FreeBSD passed
Test checkpatch passed
Test docker passed
Test s390x passed
target/ppc/cpu-models.c     |   2 +
target/ppc/cpu-models.h     |   1 +
target/ppc/cpu.h            |  26 +++++++++++-
target/ppc/mmu_helper.c     |  16 ++++---
target/ppc/translate_init.c | 100 +++++++++++++++++++++++++++++++++++++++++---
5 files changed, 132 insertions(+), 13 deletions(-)
[Qemu-devel] [PATCH for-2.11 0/4] ppc64: add e6500
Posted by KONRAD Frederic 6 years, 8 months ago
Hi,

Those are some patches to add basic e6500 support for the moment e5500 with a
correct MMU configuration and supported instructions.
Some (maybe a lot of) things are missing (ie: the thread support) but it is
enough to boot a propietary OS on my side.

The first two patches are fixes when using MAV 2.0 MMU.
The two last patches introduces the e6500.

This can be cloned here:
https://github.com/FredKonrad/qemu.git branch e6500

Thanks,
Fred

KONRAD Frederic (4):
  booke206: fix booke206_tlbnps for mav 2.0
  booke206: fix tlbnps for fixed size TLB
  booke206: allow to specify an mmucfg value at the init
  ppc64: introduce e6500

 target/ppc/cpu-models.c     |   2 +
 target/ppc/cpu-models.h     |   1 +
 target/ppc/cpu.h            |  26 +++++++++++-
 target/ppc/mmu_helper.c     |  16 ++++---
 target/ppc/translate_init.c | 100 +++++++++++++++++++++++++++++++++++++++++---
 5 files changed, 132 insertions(+), 13 deletions(-)

-- 
1.8.3.1


Re: [Qemu-devel] [PATCH for-2.11 0/4] ppc64: add e6500
Posted by David Gibson 6 years, 8 months ago
On Mon, Aug 07, 2017 at 05:50:44PM +0200, KONRAD Frederic wrote:
> Hi,
> 
> Those are some patches to add basic e6500 support for the moment e5500 with a
> correct MMU configuration and supported instructions.
> Some (maybe a lot of) things are missing (ie: the thread support) but it is
> enough to boot a propietary OS on my side.
> 
> The first two patches are fixes when using MAV 2.0 MMU.
> The two last patches introduces the e6500.
> 
> This can be cloned here:
> https://github.com/FredKonrad/qemu.git branch e6500

Looks sane as best as my minimal knowledge of e500 goes.  Applied to
ppc-for-2.11.  Alex, if you (or anyone with knowledge of this
platform) has objections, I'll reconsider.

> 
> Thanks,
> Fred
> 
> KONRAD Frederic (4):
>   booke206: fix booke206_tlbnps for mav 2.0
>   booke206: fix tlbnps for fixed size TLB
>   booke206: allow to specify an mmucfg value at the init
>   ppc64: introduce e6500
> 
>  target/ppc/cpu-models.c     |   2 +
>  target/ppc/cpu-models.h     |   1 +
>  target/ppc/cpu.h            |  26 +++++++++++-
>  target/ppc/mmu_helper.c     |  16 ++++---
>  target/ppc/translate_init.c | 100 +++++++++++++++++++++++++++++++++++++++++---
>  5 files changed, 132 insertions(+), 13 deletions(-)
> 

-- 
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
Re: [Qemu-devel] [PATCH for-2.11 0/4] ppc64: add e6500
Posted by Alexander Graf 6 years, 8 months ago

On 09.08.17 08:13, David Gibson wrote:
> On Mon, Aug 07, 2017 at 05:50:44PM +0200, KONRAD Frederic wrote:
>> Hi,
>>
>> Those are some patches to add basic e6500 support for the moment e5500 with a
>> correct MMU configuration and supported instructions.
>> Some (maybe a lot of) things are missing (ie: the thread support) but it is
>> enough to boot a propietary OS on my side.
>>
>> The first two patches are fixes when using MAV 2.0 MMU.
>> The two last patches introduces the e6500.
>>
>> This can be cloned here:
>> https://github.com/FredKonrad/qemu.git branch e6500
> 
> Looks sane as best as my minimal knowledge of e500 goes.  Applied to
> ppc-for-2.11.  Alex, if you (or anyone with knowledge of this
> platform) has objections, I'll reconsider.

I think it's good enough. We're missing a *lot* of e6500 features, but 
if this is useful to Frederic, I don't see a good reason to hold it back.

Alex