linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Palmer Dabbelt <palmer@dabbelt.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] RISC-V Fixes for 5.8-rc6
Date: Sat, 18 Jul 2020 10:35:48 -0700 (PDT)	[thread overview]
Message-ID: <mhng-8419056a-6b67-4a07-b5a2-6ca837bb9b9d@palmerdabbelt-glaptop1> (raw)

The following changes since commit 11ba468877bb23f28956a35e896356252d63c983:

  Linux 5.8-rc5 (2020-07-12 16:34:50 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.8-rc6

for you to fetch changes up to 38b7c2a3ffb1fce8358ddc6006cfe5c038ff9963:

  RISC-V: Upgrade smp_mb__after_spinlock() to iorw,iorw (2020-07-17 09:28:35 -0700)

----------------------------------------------------------------
RISC-V Fixes for 5.8-rc6

I have two fixes:

* 16KiB kernel stacks on rv64, which fixes a lot of crashes.
* Rolling an mmiowb() into the scheduled, which when combined with Will's fix
  to the mmiowb()-on-spinlock should fix the PREEMPT issues we've been seeing.

----------------------------------------------------------------
Andreas Schwab (1):
      riscv: use 16KB kernel stack on 64-bit

Palmer Dabbelt (1):
      RISC-V: Upgrade smp_mb__after_spinlock() to iorw,iorw

 arch/riscv/include/asm/barrier.h     | 10 +++++++++-
 arch/riscv/include/asm/thread_info.h |  4 ++++
 2 files changed, 13 insertions(+), 1 deletion(-)

             reply	other threads:[~2020-07-18 17:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-18 17:35 Palmer Dabbelt [this message]
2020-07-18 18:15 ` [GIT PULL] RISC-V Fixes for 5.8-rc6 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=mhng-8419056a-6b67-4a07-b5a2-6ca837bb9b9d@palmerdabbelt-glaptop1 \
    --to=palmer@dabbelt.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.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).