linux-kernel.vger.kernel.org archive mirror
 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.16
Date: Fri,  5 Nov 2021 12:19:05 -0700	[thread overview]
Message-ID: <20211105191905.7979-1-jcmvbkbc@gmail.com> (raw)

Hi Linus,

please pull the following Xtensa architecture updates for v5.16:

The following changes since commit 519d81956ee277b4419c723adfb154603c2565ba:

  Linux 5.15-rc6 (2021-10-17 20:00:13 -1000)

are available in the Git repository at:

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

for you to fetch changes up to bd47cdb78997f83bd170c389ef59de9eec65976a:

  xtensa: move section symbols to asm/sections.h (2021-10-18 22:19:35 -0700)

----------------------------------------------------------------
Xtensa updates for v5.16

- add support for xtensa cores witout windowed registers option

----------------------------------------------------------------
Max Filippov (10):
      xtensa: move _SimulateUserKernelVectorException out of WindowVectors
      xtensa: use a14 instead of a15 in inline assembly
      xtensa: don't use a12 in strncpy_user
      xtensa: don't use a12 in __xtensa_copy_user in call0 ABI
      xtensa: definitions for call0 ABI
      xtensa: implement call0 ABI support in assembly
      xtensa: use register window specific opcodes only when present
      xtensa: only build windowed register support code when needed
      xtensa: remove unused variable wmask
      xtensa: move section symbols to asm/sections.h

 arch/xtensa/boot/boot-elf/bootstrap.S     |   2 +
 arch/xtensa/boot/boot-redboot/bootstrap.S |  72 +++++-----
 arch/xtensa/include/asm/asmmacro.h        |  65 +++++++++
 arch/xtensa/include/asm/atomic.h          |  26 ++--
 arch/xtensa/include/asm/cmpxchg.h         |  16 +--
 arch/xtensa/include/asm/core.h            |  11 ++
 arch/xtensa/include/asm/processor.h       |  32 ++++-
 arch/xtensa/include/asm/sections.h        |  41 ++++++
 arch/xtensa/include/asm/traps.h           |   2 +
 arch/xtensa/kernel/align.S                |   2 +
 arch/xtensa/kernel/entry.S                | 216 +++++++++++++++++++-----------
 arch/xtensa/kernel/head.S                 |  24 ++--
 arch/xtensa/kernel/mcount.S               |  38 +++++-
 arch/xtensa/kernel/process.c              |  27 +++-
 arch/xtensa/kernel/setup.c                | 102 +++++---------
 arch/xtensa/kernel/signal.c               |  12 +-
 arch/xtensa/kernel/traps.c                |   6 +-
 arch/xtensa/kernel/vectors.S              |  55 +++++---
 arch/xtensa/kernel/vmlinux.lds.S          |  12 +-
 arch/xtensa/lib/strncpy_user.S            |  17 ++-
 arch/xtensa/lib/usercopy.S                |  28 +++-
 21 files changed, 541 insertions(+), 265 deletions(-)
 create mode 100644 arch/xtensa/include/asm/sections.h

-- 
Thanks.
-- Max

             reply	other threads:[~2021-11-05 19:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 19:19 Max Filippov [this message]
2021-11-06 21:56 ` [PULL 00/10] xtensa updates for v5.16 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=20211105191905.7979-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;
as well as URLs for NNTP newsgroup(s).