mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	maddy@linux.vnet.ibm.com, npiggin@gmail.com
Subject: [GIT PULL] Please pull powerpc/linux.git powerpc-4.13-3 tag
Date: Fri, 21 Jul 2017 21:14:20 +1000	[thread overview]
Message-ID: <87h8y6dotv.fsf@concordia.ellerman.id.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 2454 bytes --]

Hi Linus,

Please pull some more powerpc fixes for 4.13:

The following changes since commit 01e6a61aceb82e13bec29502a8eb70d9574f97ad:

  powerpc/64: Fix atomic64_inc_not_zero() to return an int (2017-07-12 21:49:55 +1000)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git tags/powerpc-4.13-3

for you to fetch changes up to 029d9252b116fa52a95150819e62af1f6e420fe5:

  powerpc/mm: Mark __init memory no-execute when STRICT_KERNEL_RWX=y (2017-07-18 19:54:24 +1000)

----------------------------------------------------------------
powerpc fixes for 4.13 #3

A handful of fixes, mostly for new code.

Some reworking of the new STRICT_KERNEL_RWX support to make sure we also remove
executable permission from __init memory before it's freed.

A fix to some recent optimisations to the hypercall entry where we were
clobbering r12, this was breaking nested guests (PR KVM).

A fix for the recent patch to opal_configure_cores(). This could break booting
on bare metal Power8 boxes if the kernel was built without
CONFIG_JUMP_LABEL_FEATURE_CHECK_DEBUG.

And finally a workaround for spurious PMU interrupts on Power9 DD2.

Thanks to:
  Nicholas Piggin, Anton Blanchard, Balbir Singh.

----------------------------------------------------------------
Michael Ellerman (4):
      powerpc/powernv: Fix boot on Power8 bare metal due to opal_configure_cores()
      powerpc/mm/radix: Refactor radix__mark_rodata_ro()
      powerpc/mm/hash: Refactor hash__mark_rodata_ro()
      powerpc/mm: Mark __init memory no-execute when STRICT_KERNEL_RWX=y

Nicholas Piggin (2):
      powerpc/perf: Avoid spurious PMU interrupts after idle
      powerpc/64s: Fix hypercall entry clobbering r12 input

 arch/powerpc/include/asm/book3s/64/hash.h    |  1 +
 arch/powerpc/include/asm/book3s/64/pgtable.h |  1 +
 arch/powerpc/include/asm/book3s/64/radix.h   |  1 +
 arch/powerpc/include/asm/pgtable.h           |  7 +++++
 arch/powerpc/kernel/exceptions-64s.S         | 28 +++++++++---------
 arch/powerpc/kernel/idle_book3s.S            | 15 +++++++++-
 arch/powerpc/mm/mem.c                        |  1 +
 arch/powerpc/mm/pgtable-hash64.c             | 44 ++++++++++++++++++++--------
 arch/powerpc/mm/pgtable-radix.c              | 28 ++++++++++++++----
 arch/powerpc/mm/pgtable_64.c                 |  8 +++++
 arch/powerpc/platforms/powernv/opal.c        |  2 +-
 11 files changed, 102 insertions(+), 34 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

                 reply	other threads:[~2017-07-21 11:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87h8y6dotv.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®