linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Erhard Furtner <erhard_f@mailbox.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: Juergen Gross <jgross@suse.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	linux-sparc@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/2] Allow nesting of lazy MMU mode
Date: Fri, 13 Oct 2023 15:42:20 +0200	[thread overview]
Message-ID: <20231013154220.02fb2e6d@yea> (raw)
In-Reply-To: <20231012195415.282357-1-willy@infradead.org>

On Thu, 12 Oct 2023 20:54:13 +0100
"Matthew Wilcox (Oracle)" <willy@infradead.org> wrote:

> Dave Woodhouse reported that we now nest calls to
> arch_enter_lazy_mmu_mode().  That was inadvertent, but in principle we
> should allow it.  On further investigation, Juergen already fixed it
> for Xen, but didn't tell anyone.  Fix it for Sparc & PowerPC too.
> This may or may not help fix the problem that Erhard reported.
> 
> Matthew Wilcox (Oracle) (2):
>   powerpc: Allow nesting of lazy MMU mode
>   sparc: Allow nesting of lazy MMU mode
> 
>  arch/powerpc/include/asm/book3s/64/tlbflush-hash.h | 5 ++---
>  arch/sparc/mm/tlb.c                                | 5 ++---
>  2 files changed, 4 insertions(+), 6 deletions(-)
> 
> -- 
> 2.40.1

Applied the patch on top of v6.6-rc5 but unfortunately it did not fix my reported issue.

Regards,
Erhard

  parent reply	other threads:[~2023-10-13 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-12 19:54 [PATCH 0/2] Allow nesting of lazy MMU mode Matthew Wilcox (Oracle)
2023-10-12 19:54 ` [PATCH 1/2] powerpc: " Matthew Wilcox (Oracle)
2023-10-12 19:54 ` [PATCH 2/2] sparc: " Matthew Wilcox (Oracle)
2023-10-13 13:42 ` Erhard Furtner [this message]
2023-10-17  6:04   ` [PATCH 0/2] " Aneesh Kumar K.V
2023-10-17 23:14     ` Erhard Furtner

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=20231013154220.02fb2e6d@yea \
    --to=erhard_f@mailbox.org \
    --cc=dwmw2@infradead.org \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sparc@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=willy@infradead.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).