From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
benh@kernel.crashing.org, paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [v3,1/3] powerpc/mm: Rename find_linux_pte_or_hugepte
Date: Mon, 21 Aug 2017 23:39:08 +1000 (AEST) [thread overview]
Message-ID: <3xbZXr2tPHz9sRW@ozlabs.org> (raw)
In-Reply-To: <20170727062455.15404-1-aneesh.kumar@linux.vnet.ibm.com>
On Thu, 2017-07-27 at 06:24:53 UTC, "Aneesh Kumar K.V" wrote:
> Add newer helpers to make the function usage simpler. It is always recommended
> to use find_current_mm_pte() for walking the page table. If we cannot use
> find_current_mm_pte(), it should be documented why the said usage of
> __find_linux_pte() is safe against a parallel THP split.
>
> For now we have KVM code using __find_linux_pte(). This is because kvm code ends
> up calling __find_linux_pte() in real mode with MSR_EE=0 but with PACA soft_enabled =
> 1. We may want to fix that later and make sure we keep the MSR_EE and PACA
> soft_enabled in sync. When we do that we can switch kvm to use find_linux_pte().
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Applied to powerpc next and topic/ppc-kvm, thanks.
https://git.kernel.org/powerpc/c/94171b19c3f1f4d9d4c0e3aaa1aa16
cheers
prev parent reply other threads:[~2017-08-21 13:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 6:24 [PATCH v3 1/3] powerpc/mm: Rename find_linux_pte_or_hugepte Aneesh Kumar K.V
2017-07-27 6:24 ` [PATCH v3 2/3] powerpc/mm: Don't send IPI to all cpus on THP updates Aneesh Kumar K.V
2017-08-21 13:39 ` [v3,2/3] " Michael Ellerman
2017-07-27 6:24 ` [PATCH v3 3/3] powerpc/mm/cxl: Add the fault handling cpu to mm cpumask Aneesh Kumar K.V
2017-08-21 13:39 ` [v3, " Michael Ellerman
2017-08-21 16:49 ` [v3,3/3] " Benjamin Herrenschmidt
2017-08-21 13:39 ` Michael Ellerman [this message]
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=3xbZXr2tPHz9sRW@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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.