linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 7/7] arm64: hugetlb: Add break-before-make logic for contiguous entries
Date: Wed, 22 Mar 2017 14:38:10 +0000	[thread overview]
Message-ID: <20170322143810.GH2977@leverpostej> (raw)
In-Reply-To: <20170321180421.18332-8-punit.agrawal@arm.com>

On Tue, Mar 21, 2017 at 06:04:21PM +0000, Punit Agrawal wrote:
> From: Steve Capper <steve.capper@arm.com>
> 
> It has become apparent that one has to take special care when modifying
> attributes of memory mappings that employ the contiguous bit.
> 
> Both the requirement and the architecturally correct "Break-Before-Make"
> technique of updating contiguous entries can be found described in:
> ARM DDI 0487A.k_iss10775, "Misprogramming of the Contiguous bit",
> page D4-1762.
> 
> The huge pte accessors currently replace the attributes of contiguous
> pte entries in place thus can, on certain platforms, lead to TLB
> conflict aborts or even erroneous results returned from TLB lookups.
> 
> This patch adds a helper function get_clear_flush(.) that clears a
> contiguous entry and returns the head pte (whilst taking care to
> retain dirty bit information that could have been modified by DBM).
> A tlb invalidate is performed to then ensure that there is no
> possibility of multiple tlb entries being present for the same
> region.

Since its evidently easy to miss, can we please add a comment above
get_clear_flush() regarding the BBM requirement, e.g.

/*
 * Changing some bits of contiguous entries requires us to follow a
 * Break-Before-Make approach, breaking the whole contiguous set before
 * we can change any entries. See ARM DDI 0487A.k_iss10775,
 * "Misprogramming of the Contiguous bit", page D4-1762.
 *
 * This helper performs the break step.
 */

Otherwise, this looks good to me, and to the best of my knowledge avoids
the issue described above.

FWIW:

Reviewed-by: Mark Rutland <mark.rutland@arm.com>

Mark.

  reply	other threads:[~2017-03-22 14:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 18:04 [PATCH 0/7] arm64: hugetlb cleanup + break-before-make fixes Punit Agrawal
2017-03-21 18:04 ` [PATCH 1/7] arm64: hugetlb: set_huge_pte_at Add WARN_ON on !pte_present Punit Agrawal
2017-03-21 18:04 ` [PATCH 2/7] arm64: hugetlb: Cleanup setup_hugepagesz Punit Agrawal
2017-03-22 14:01   ` Mark Rutland
2017-03-21 18:04 ` [PATCH 3/7] arm64: hugetlb: Refactor find_num_contig Punit Agrawal
2017-03-22 14:14   ` Mark Rutland
2017-03-21 18:04 ` [PATCH 4/7] arm64: hugetlb: Introduce pte_pgprot helper Punit Agrawal
2017-03-22 14:16   ` Mark Rutland
2017-03-21 18:04 ` [PATCH 5/7] arm64: hugetlb: Remove spurious calls to huge_ptep_offset Punit Agrawal
2017-03-22 14:18   ` Mark Rutland
2017-03-21 18:04 ` [PATCH 6/7] arm64: hugetlb: Spring clean huge pte accessors Punit Agrawal
2017-03-22 14:24   ` Mark Rutland
2017-03-21 18:04 ` [PATCH 7/7] arm64: hugetlb: Add break-before-make logic for contiguous entries Punit Agrawal
2017-03-22 14:38   ` Mark Rutland [this message]
2017-03-22 18:14     ` Punit Agrawal

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=20170322143810.GH2977@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=linux-arm-kernel@lists.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).