From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Laurent Dufour <ldufour@linux.ibm.com>,
benh@kernel.crashing.org, paulus@samba.org,
aneesh.kumar@linux.ibm.com, npiggin@gmail.com,
linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] powperc/mm: read TLB Block Invalidate Characteristics
Date: Wed, 25 Sep 2019 21:05:25 +1000 (AEST) [thread overview]
Message-ID: <46dZwP4hpLz9sPl@ozlabs.org> (raw)
In-Reply-To: <20190920130523.20441-2-ldufour@linux.ibm.com>
On Fri, 2019-09-20 at 13:05:22 UTC, Laurent Dufour wrote:
> The PAPR document specifies the TLB Block Invalidate Characteristics which
> tells for each pair of segment base page size, actual page size, the size
> of the block the hcall H_BLOCK_REMOVE supports.
>
> These characteristics are loaded at boot time in a new table hblkr_size.
> The table is separate from the mmu_psize_def because this is specific to
> the pseries platform.
>
> A new init function, pseries_lpar_read_hblkrm_characteristics() is added to
> read the characteristics. It is called from pSeries_setup_arch().
>
> Fixes: ba2dd8a26baa ("powerpc/pseries/mm: call H_BLOCK_REMOVE")
> Signed-off-by: Laurent Dufour <ldufour@linux.ibm.com>
Series applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c/1211ee61b4a8e60d6dc77211cdcf01906915bfba
cheers
next prev parent reply other threads:[~2019-09-25 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 13:05 [PATCH v3 0/2] powerpc/mm: Conditionally call H_BLOCK_REMOVE Laurent Dufour
2019-09-20 13:05 ` [PATCH v3 1/2] powperc/mm: read TLB Block Invalidate Characteristics Laurent Dufour
2019-09-25 11:05 ` Michael Ellerman [this message]
2019-09-20 13:05 ` [PATCH v3 2/2] powerpc/mm: call H_BLOCK_REMOVE when supported Laurent Dufour
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=46dZwP4hpLz9sPl@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=aneesh.kumar@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox