Re: [PATCH v2 2/3] x86/mm: Make flush_tlb_mm_range() more predictable

2017-04-21 Thread Dave Hansen
On 04/21/2017 11:15 AM, Andy Lutomirski wrote: > I'm about to rewrite the function almost completely, but first I > want to get a functional change out of the way. Currently, if > flush_tlb_mm_range() does not flush the local TLB at all, it will > never do individual page flushes on remote CPUs.

Re: [PATCH v2 2/3] x86/mm: Make flush_tlb_mm_range() more predictable

2017-04-21 Thread Dave Hansen
On 04/21/2017 11:15 AM, Andy Lutomirski wrote: > I'm about to rewrite the function almost completely, but first I > want to get a functional change out of the way. Currently, if > flush_tlb_mm_range() does not flush the local TLB at all, it will > never do individual page flushes on remote CPUs.

[PATCH v2 2/3] x86/mm: Make flush_tlb_mm_range() more predictable

2017-04-21 Thread Andy Lutomirski
I'm about to rewrite the function almost completely, but first I want to get a functional change out of the way. Currently, if flush_tlb_mm_range() does not flush the local TLB at all, it will never do individual page flushes on remote CPUs. This seems to be an accident, and preserving it will

[PATCH v2 2/3] x86/mm: Make flush_tlb_mm_range() more predictable

2017-04-21 Thread Andy Lutomirski
I'm about to rewrite the function almost completely, but first I want to get a functional change out of the way. Currently, if flush_tlb_mm_range() does not flush the local TLB at all, it will never do individual page flushes on remote CPUs. This seems to be an accident, and preserving it will