mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-xtensa@linux-xtensa.org,
	Chris Zankel <chris@zankel.net>,
	Max Filippov <jcmvbkbc@gmail.com>
Subject: [PULL 00/10] xtensa updates for v5.9
Date: Wed,  5 Aug 2020 09:17:13 -0700	[thread overview]
Message-ID: <20200805161713.7476-1-jcmvbkbc@gmail.com> (raw)

Hi Linus,

please pull the following Xtensa architecture updates for v5.9.
There are trivial conflicts in the seccomp selftests with the csky
and sh trees.

The following changes since commit 92ed301919932f777713b9172e525674157e983d:

  Linux 5.8-rc7 (2020-07-26 14:14:06 -0700)

are available in the Git repository at:

  git://github.com/jcmvbkbc/linux-xtensa.git tags/xtensa-20200805

for you to fetch changes up to a0fc1436f1f4f84e93144480bf30e0c958d135b6:

  xtensa: add missing exclusive access state management (2020-07-31 14:15:57 -0700)

----------------------------------------------------------------
Xtensa updates for v5.9:

- add syscall audit support
- add seccomp filter support
- clean up make rules under arch/xtensa/boot
- fix state management for exclusive access opcodes
- fix build with PMU enabled

----------------------------------------------------------------
Masahiro Yamada (1):
      xtensa: add boot subdirectories build artifacts to 'targets'

Max Filippov (8):
      xtensa: add audit support
      xtensa: expose syscall through user_pt_regs
      xtensa: add seccomp support
      selftests/seccomp: add xtensa support
      xtensa: move vmlinux.bin[.gz] to boot subdirectory
      xtensa: add uImage and xipImage to targets
      xtensa: fix xtensa_pmu_setup prototype
      xtensa: add missing exclusive access state management

Randy Dunlap (1):
      xtensa: initialize_mmu.h: fix a duplicated word

 .../features/seccomp/seccomp-filter/arch-support.txt     |  2 +-
 arch/xtensa/Kconfig                                      | 16 ++++++++++++++++
 arch/xtensa/boot/Makefile                                | 12 +++++++-----
 arch/xtensa/boot/boot-elf/Makefile                       |  5 +++--
 arch/xtensa/boot/boot-redboot/Makefile                   |  5 +++--
 arch/xtensa/include/asm/Kbuild                           |  1 +
 arch/xtensa/include/asm/initialize_mmu.h                 |  2 +-
 arch/xtensa/include/asm/thread_info.h                    | 11 ++++++++++-
 arch/xtensa/include/uapi/asm/ptrace.h                    |  3 ++-
 arch/xtensa/kernel/asm-offsets.c                         |  3 +++
 arch/xtensa/kernel/entry.S                               | 11 +++++++++++
 arch/xtensa/kernel/perf_event.c                          |  2 +-
 arch/xtensa/kernel/ptrace.c                              | 14 +++++++++++++-
 tools/testing/selftests/seccomp/seccomp_bpf.c            | 16 +++++++++++++++-
 14 files changed, 87 insertions(+), 16 deletions(-)

-- 
Thanks.
-- Max

             reply	other threads:[~2020-08-05 16:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 16:17 Max Filippov [this message]
2020-08-06 17:19 ` pr-tracker-bot

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=20200805161713.7476-1-jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=chris@zankel.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.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 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®