qemu-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-commits] [qemu/qemu] 3ade1a: target-ppc: Fix breakpoint registers


From: GitHub
Subject: [Qemu-commits] [qemu/qemu] 3ade1a: target-ppc: Fix breakpoint registers for e300
Date: Thu, 20 Nov 2014 07:00:09 -0800

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: 3ade1a055c9ac6c351a008703e30fb831f23b941
      
https://github.com/qemu/qemu/commit/3ade1a055c9ac6c351a008703e30fb831f23b941
  Author: Fabien Chouteau <address@hidden>
  Date:   2014-11-20 (Thu, 20 Nov 2014)

  Changed paths:
    M target-ppc/translate_init.c

  Log Message:
  -----------
  target-ppc: Fix breakpoint registers for e300

In the previous patch, the registers were added to init_proc_G2LE
instead of init_proc_e300.

Signed-off-by: Fabien Chouteau <address@hidden>
Signed-off-by: Alexander Graf <address@hidden>


  Commit: f2a64032a14c642d0ddc9a7a846fc3d737deede5
      
https://github.com/qemu/qemu/commit/f2a64032a14c642d0ddc9a7a846fc3d737deede5
  Author: Alexander Graf <address@hidden>
  Date:   2014-11-20 (Thu, 20 Nov 2014)

  Changed paths:
    M kvm-all.c

  Log Message:
  -----------
  kvm: Fix memory slot page alignment logic

Memory slots have to be page aligned to get entered into KVM. There
is existing logic that tries to ensure that we pad memory slots that
are not page aligned to the biggest region that would still fit in the
alignment requirements.

Unfortunately, that logic is broken. It tries to calculate the start
offset based on the region size.

Fix up the logic to do the thing it was intended to do and document it
properly in the comment above it.

With this patch applied, I can successfully run an e500 guest with more
than 3GB RAM (at which point RAM starts overlapping subpage memory regions).

Cc: address@hidden
Signed-off-by: Alexander Graf <address@hidden>


  Commit: 76cb6584196b6f35d6e9b5124974d3eba643f772
      
https://github.com/qemu/qemu/commit/76cb6584196b6f35d6e9b5124974d3eba643f772
  Author: Tom Musta <address@hidden>
  Date:   2014-11-20 (Thu, 20 Nov 2014)

  Changed paths:
    M target-ppc/translate.c

  Log Message:
  -----------
  target-ppc: Altivec's mtvscr Decodes Wrong Register

The Move to Vector Status and Control Register (mtvscr) instruction
uses VRB as the source register.  Fix the code generator to correctly
decode the VRB field.  That is, use "rB(ctx->opcode)" instead of
"rD(ctx->opcode)".

Signed-off-by: Tom Musta <address@hidden>
Signed-off-by: Alexander Graf <address@hidden>


  Commit: ff323a6b5468523aab07d376875685ec00385f44
      
https://github.com/qemu/qemu/commit/ff323a6b5468523aab07d376875685ec00385f44
  Author: Peter Maydell <address@hidden>
  Date:   2014-11-20 (Thu, 20 Nov 2014)

  Changed paths:
    M kvm-all.c
    M target-ppc/translate.c
    M target-ppc/translate_init.c

  Log Message:
  -----------
  Merge remote-tracking branch 'remotes/agraf/tags/signed-ppc-for-upstream' 
into staging

Patch queue for ppc - 2014-11-20

Hopefully the last few fixups for 2.2:

  - KVM memory slot fix (should usually only occur on PPC)
  - e300 fix
  - Altivec mtvscr instruction fix

# gpg: Signature made Thu 20 Nov 2014 13:53:34 GMT using RSA key ID 03FEDC60
# gpg: Good signature from "Alexander Graf <address@hidden>"
# gpg:                 aka "Alexander Graf <address@hidden>"

* remotes/agraf/tags/signed-ppc-for-upstream:
  target-ppc: Altivec's mtvscr Decodes Wrong Register
  kvm: Fix memory slot page alignment logic
  target-ppc: Fix breakpoint registers for e300

Signed-off-by: Peter Maydell <address@hidden>


Compare: https://github.com/qemu/qemu/compare/f75ad80f6c8c...ff323a6b5468

reply via email to

[Prev in Thread] Current Thread [Next in Thread]