From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <mpe@ellerman.id.au>,
Suraj Jitindar Singh <sjitindarsingh@gmail.com>,
linuxppc-dev@lists.ozlabs.org
Cc: paulus@samba.org, aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [PATCH] powerpc/mm: Invalidate partition table cache on host proc tbl base update
Date: Thu, 03 Aug 2017 17:35:20 +1000 [thread overview]
Message-ID: <1501745720.2664.38.camel@kernel.crashing.org> (raw)
In-Reply-To: <87h8xpqi28.fsf@concordia.ellerman.id.au>
On Thu, 2017-08-03 at 16:30 +1000, Michael Ellerman wrote:
> Suraj Jitindar Singh <sjitindarsingh@gmail.com> writes:
>
> > The host process table base is stored in the partition table by calling
> > the function native_register_process_table(). Currently this just sets
> > the entry in memory and is missing a proceeding cache invalidation
> > instruction. Any update to the partition table should be followed by a
> > cache invalidation instruction specifying invalidation of the caching of
> > any partition table entries (RIC = 2, PRS = 0).
> >
> > We already have a function to update the partition table with the
> > required cache invalidation instructions - mmu_partition_table_set_entry().
> > Update the native_register_process_table() function to call
> > mmu_partition_table_set_entry(), this ensures all appropriate
> > invalidation will be performed.
>
> Without this patch the kernel will:
> [ ] work normally
> [ ] randomly crash
> [ ] catch fire
I think we get lucky because OPAL added a "flush the whole world" to
opal_reinit_cpus() but this patch seems to improve general code
"correctness".
Cheers,
Ben.
next prev parent reply other threads:[~2017-08-03 7:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 4:15 [PATCH] powerpc/mm: Invalidate partition table cache on host proc tbl base update Suraj Jitindar Singh
2017-08-03 6:30 ` Michael Ellerman
2017-08-03 7:35 ` Benjamin Herrenschmidt [this message]
2017-08-04 1:02 ` Suraj Jitindar Singh
2017-08-04 1:31 ` Benjamin Herrenschmidt
2017-08-04 1:53 ` Suraj Jitindar Singh
2017-08-04 3:33 ` Michael Ellerman
2017-08-04 3:49 ` Aneesh Kumar K.V
2017-08-09 10:30 ` Michael Ellerman
2017-08-14 7:24 ` Suraj Jitindar Singh
2017-08-11 12:19 ` Michael Ellerman
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=1501745720.2664.38.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sjitindarsingh@gmail.com \
/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).