Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1347074 > unrolled thread

Re: [2/4] powerpc/mm: Handle removing maybe-present bolted HPTEs

Started byMichael Ellerman <mpe@ellerman.id.au>
First post2016-03-01 23:30 +0100
Last post2016-03-01 23:30 +0100
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [2/4] powerpc/mm: Handle removing maybe-present bolted HPTEs Michael Ellerman <mpe@ellerman.id.au> - 2016-03-01 23:30 +0100

#1347074 — Re: [2/4] powerpc/mm: Handle removing maybe-present bolted HPTEs

FromMichael Ellerman <mpe@ellerman.id.au>
Date2016-03-01 23:30 +0100
SubjectRe: [2/4] powerpc/mm: Handle removing maybe-present bolted HPTEs
Message-ID<r80XP-6Zi-81@gated-at.bofh.it>
On Tue, 2016-09-02 at 03:32:41 UTC, David Gibson wrote:
> At the moment the hpte_removebolted callback in ppc_md returns void and
> will BUG_ON() if the hpte it's asked to remove doesn't exist in the first
> place.  This is awkward for the case of cleaning up a mapping which was
> partially made before failing.
> 
> So, we add a return value to hpte_removebolted, and have it return ENOENT
> in the case that the HPTE to remove didn't exist in the first place.
> 
> In the (sole) caller, we propagate errors in hpte_removebolted to its
> caller to handle.  However, we handle ENOENT specially, continuing to
> complete the unmapping over the specified range before returning the error
> to the caller.
> 
> This means that htab_remove_mapping() will work sanely on a partially
> present mapping, removing any HPTEs which are present, while also returning
> ENOENT to its caller in case it's important there.
> 
> There are two callers of htab_remove_mapping():
>    - In remove_section_mapping() we already WARN_ON() any error return,
>      which is reasonable - in this case the mapping should be fully
>      present
>    - In vmemmap_remove_mapping() we BUG_ON() any error.  We change that to
>      just a WARN_ON() in the case of ENOENT, since failing to remove a
>      mapping that wasn't there in the first place probably shouldn't be
>      fatal.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> Reviewed-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>

Applied to powerpc next, thanks.

https://git.kernel.org/powerpc/c/27828f98a0522ad4a745a80407

cheers

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web