All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: fixes for -rc5
Date: Fri, 14 Jun 2019 16:02:59 +0100	[thread overview]
Message-ID: <20190614150259.GC29231@fuggles.cambridge.arm.com> (raw)

Hi Linus,

Here are some arm64 fixes for -rc5. The only non-trivial change (in
terms of the diffstat) is fixing our SVE ptrace API for big-endian
machines, but the majority of this is actually the addition of
much-needed comments and updates to the documentation to try to avoid
this mess biting us again in future.

There are still a couple of small things on the horizon, but nothing
major at this point.

Please pull. Thanks,

Will

--->8

The following changes since commit ebcc5928c5d925b1c8d968d9c89cdb0d0186db17:

  arm64: Silence gcc warnings about arch ABI drift (2019-06-06 13:28:45 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to 41040cf7c5f0f26c368bc5d3016fed3a9ca6dba4:

  arm64/sve: Fix missing SVE/FPSIMD endianness conversions (2019-06-13 10:07:19 +0100)

----------------------------------------------------------------
arm64 fixes for -rc5

- Fix broken SVE ptrace API when running in a big-endian configuration

- Fix performance regression due to off-by-one in TLBI range checking

- Fix build regression when using Clang

----------------------------------------------------------------
Dave Martin (1):
      arm64/sve: Fix missing SVE/FPSIMD endianness conversions

Nathan Chancellor (1):
      arm64: Don't unconditionally add -Wno-psabi to KBUILD_CFLAGS

Will Deacon (1):
      arm64: tlbflush: Ensure start/end of address range are aligned to stride

 Documentation/arm64/sve.txt              | 16 ++++++++++++
 arch/arm64/Makefile                      |  2 +-
 arch/arm64/include/asm/tlbflush.h        |  3 +++
 arch/arm64/include/uapi/asm/kvm.h        |  7 ++++++
 arch/arm64/include/uapi/asm/ptrace.h     |  4 +++
 arch/arm64/include/uapi/asm/sigcontext.h | 14 +++++++++++
 arch/arm64/kernel/fpsimd.c               | 42 +++++++++++++++++++++++++-------
 7 files changed, 78 insertions(+), 10 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com
Subject: [GIT PULL] arm64: fixes for -rc5
Date: Fri, 14 Jun 2019 16:02:59 +0100	[thread overview]
Message-ID: <20190614150259.GC29231@fuggles.cambridge.arm.com> (raw)

Hi Linus,

Here are some arm64 fixes for -rc5. The only non-trivial change (in
terms of the diffstat) is fixing our SVE ptrace API for big-endian
machines, but the majority of this is actually the addition of
much-needed comments and updates to the documentation to try to avoid
this mess biting us again in future.

There are still a couple of small things on the horizon, but nothing
major at this point.

Please pull. Thanks,

Will

--->8

The following changes since commit ebcc5928c5d925b1c8d968d9c89cdb0d0186db17:

  arm64: Silence gcc warnings about arch ABI drift (2019-06-06 13:28:45 +0100)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to 41040cf7c5f0f26c368bc5d3016fed3a9ca6dba4:

  arm64/sve: Fix missing SVE/FPSIMD endianness conversions (2019-06-13 10:07:19 +0100)

----------------------------------------------------------------
arm64 fixes for -rc5

- Fix broken SVE ptrace API when running in a big-endian configuration

- Fix performance regression due to off-by-one in TLBI range checking

- Fix build regression when using Clang

----------------------------------------------------------------
Dave Martin (1):
      arm64/sve: Fix missing SVE/FPSIMD endianness conversions

Nathan Chancellor (1):
      arm64: Don't unconditionally add -Wno-psabi to KBUILD_CFLAGS

Will Deacon (1):
      arm64: tlbflush: Ensure start/end of address range are aligned to stride

 Documentation/arm64/sve.txt              | 16 ++++++++++++
 arch/arm64/Makefile                      |  2 +-
 arch/arm64/include/asm/tlbflush.h        |  3 +++
 arch/arm64/include/uapi/asm/kvm.h        |  7 ++++++
 arch/arm64/include/uapi/asm/ptrace.h     |  4 +++
 arch/arm64/include/uapi/asm/sigcontext.h | 14 +++++++++++
 arch/arm64/kernel/fpsimd.c               | 42 +++++++++++++++++++++++++-------
 7 files changed, 78 insertions(+), 10 deletions(-)

             reply	other threads:[~2019-06-14 15:03 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 15:02 Will Deacon [this message]
2019-06-14 15:02 ` [GIT PULL] arm64: fixes for -rc5 Will Deacon
2019-06-14 16:20 ` pr-tracker-bot
2019-06-14 16:20   ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2026-03-20 13:06 [GIT PULL] arm64 " Will Deacon
2026-03-20 16:25 ` pr-tracker-bot
2025-03-01 21:21 Will Deacon
2025-03-01 21:48 ` pr-tracker-bot
2024-02-16 11:58 Will Deacon
2024-02-16 11:58 ` Will Deacon
2024-02-16 18:52 ` pr-tracker-bot
2024-02-16 18:52   ` pr-tracker-bot
2023-10-06  7:56 Will Deacon
2023-10-06  7:56 ` Will Deacon
2023-10-06 15:15 ` pr-tracker-bot
2023-10-06 15:15   ` pr-tracker-bot
2023-07-21 11:44 Will Deacon
2023-07-21 11:44 ` Will Deacon
2023-07-21 11:45 ` Will Deacon
2023-07-21 11:45   ` Will Deacon
2023-07-21 17:28 ` pr-tracker-bot
2023-07-21 17:28   ` pr-tracker-bot
2022-09-11 11:37 Will Deacon
2022-09-11 11:37 ` Will Deacon
2022-09-11 19:36 ` pr-tracker-bot
2022-09-11 19:36   ` pr-tracker-bot
2021-08-06 13:53 Will Deacon
2021-08-06 13:53 ` Will Deacon
2021-08-06 18:40 ` Linus Torvalds
2021-08-06 18:40   ` Linus Torvalds
2021-08-09 10:52   ` Will Deacon
2021-08-09 10:52     ` Will Deacon
2021-08-06 18:48 ` pr-tracker-bot
2021-08-06 18:48   ` pr-tracker-bot
2021-03-25 14:54 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-25 14:54 ` Will Deacon
2021-03-25 19:13 ` pr-tracker-bot
2021-03-25 19:13   ` pr-tracker-bot
2020-07-10 14:39 [GIT PULL] arm64 fixes " Will Deacon
2020-07-10 14:39 ` Will Deacon
2020-07-10 16:55 ` pr-tracker-bot
2020-07-10 16:55   ` pr-tracker-bot
2020-03-06 15:12 Will Deacon
2020-03-06 15:12 ` Will Deacon
2020-03-06 20:55 ` pr-tracker-bot
2020-03-06 20:55   ` pr-tracker-bot
2019-04-12 16:05 Will Deacon
2019-04-12 16:05 ` Will Deacon
2019-04-13 17:40 ` pr-tracker-bot
2019-04-13 17:40   ` pr-tracker-bot
2019-02-01 17:51 [GIT PULL] arm64: " Will Deacon
2019-02-01 17:51 ` Will Deacon
2019-02-02  1:00 ` pr-tracker-bot
2019-02-02  1:00   ` pr-tracker-bot
2018-05-11 17:30 Will Deacon
2018-05-11 17:30 ` Will Deacon
2017-03-31 17:15 Will Deacon
2017-03-31 17:15 ` Will Deacon
2016-06-24 11:41 Will Deacon
2016-06-24 11:41 ` Will Deacon
2016-02-19 16:29 Will Deacon
2016-02-19 16:29 ` Will Deacon
2015-10-07 14:20 Will Deacon
2015-10-07 14:20 ` Will Deacon
2015-01-16 17:16 Will Deacon
2015-01-16 17:16 ` Will Deacon

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=20190614150259.GC29231@fuggles.cambridge.arm.com \
    --to=will.deacon@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.