From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Rework the pte handling for hardware AF/DBM
Date: Fri, 18 Aug 2017 18:29:36 +0100 [thread overview]
Message-ID: <20170818172936.GA10043@arm.com> (raw)
In-Reply-To: <20170818172602.7624-1-catalin.marinas@arm.com>
On Fri, Aug 18, 2017 at 06:25:57PM +0100, Catalin Marinas wrote:
> That's the second version of the pte accessors reworking series (first
> version at [1]).
>
> Changes since v1:
>
> - READ_ONCE moved out of the cmpxchg loops since cmpxchg already returns
> the old value (probably more efficient with LSE atomics)
>
> - The first patch from the first series has been merged upstream (cc
> stable)
>
> - Kconfig entry kept just to disable the hardware feature but the code
> paths all assume hardware AF/DBM
>
> - PAGE_COPY(_EXEC) removed as they just duplicate PAGE_READONLY(_EXEC)
>
> I kept the review-by tags in place as the logic is unchanged but feel
> free to look at the patches again.
Thanks, this looks good to me now:
Reviewed-by: Will Deacon <will.deacon@arm.com>
Will
next prev parent reply other threads:[~2017-08-18 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 17:25 [PATCH v2 0/5] Rework the pte handling for hardware AF/DBM Catalin Marinas
2017-08-18 17:25 ` [PATCH v2 1/5] arm64: Convert pte handling from inline asm to using (cmp)xchg Catalin Marinas
2017-08-18 17:25 ` [PATCH v2 2/5] kvm: arm64: Convert kvm_set_s2pte_readonly() from inline asm to cmpxchg() Catalin Marinas
2017-08-18 17:26 ` [PATCH v2 3/5] arm64: Move PTE_RDONLY bit handling out of set_pte_at() Catalin Marinas
2017-08-18 17:26 ` [PATCH v2 4/5] arm64: Ignore hardware dirty bit updates in ptep_set_wrprotect() Catalin Marinas
2017-08-18 17:26 ` [PATCH v2 5/5] arm64: Remove the !CONFIG_ARM64_HW_AFDBM alternative code paths Catalin Marinas
2017-08-18 17:29 ` Will Deacon [this message]
2017-08-21 10:41 ` [PATCH v2 0/5] Rework the pte handling for hardware AF/DBM Catalin Marinas
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=20170818172936.GA10043@arm.com \
--to=will.deacon@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).