Re: [PATCH 1/6] arm64: pgtable: Fix pte_accessible()

2020-11-24 Thread Anshuman Khandual
On 11/20/20 8:05 PM, Will Deacon wrote: > pte_accessible() is used by ptep_clear_flush() to figure out whether TLB > invalidation is necessary when unmapping pages for reclaim. Although our > implementation is correct according to the architecture, returning true > only for valid, young ptes in

Re: [PATCH 1/6] arm64: pgtable: Fix pte_accessible()

2020-11-23 Thread Catalin Marinas
On Fri, Nov 20, 2020 at 02:35:52PM +, Will Deacon wrote: > pte_accessible() is used by ptep_clear_flush() to figure out whether TLB > invalidation is necessary when unmapping pages for reclaim. Although our > implementation is correct according to the architecture, returning true > only for

Re: [PATCH 1/6] arm64: pgtable: Fix pte_accessible()

2020-11-20 Thread Yu Zhao
On Fri, Nov 20, 2020 at 02:35:52PM +, Will Deacon wrote: > pte_accessible() is used by ptep_clear_flush() to figure out whether TLB > invalidation is necessary when unmapping pages for reclaim. Although our > implementation is correct according to the architecture, returning true > only for

Re: [PATCH 1/6] arm64: pgtable: Fix pte_accessible()

2020-11-20 Thread Minchan Kim
On Fri, Nov 20, 2020 at 02:35:52PM +, Will Deacon wrote: > pte_accessible() is used by ptep_clear_flush() to figure out whether TLB > invalidation is necessary when unmapping pages for reclaim. Although our > implementation is correct according to the architecture, returning true > only for

[PATCH 1/6] arm64: pgtable: Fix pte_accessible()

2020-11-20 Thread Will Deacon
pte_accessible() is used by ptep_clear_flush() to figure out whether TLB invalidation is necessary when unmapping pages for reclaim. Although our implementation is correct according to the architecture, returning true only for valid, young ptes in the absence of racing page-table modifications,