Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
Date: Fri, 11 Aug 2017 14:54:42 +0200
Cc: Vitaly Kuznetsov <vkuznets@xxxxxxxxxx>, Jork Loeser <Jork.Loeser@xxxxxxxxxxxxx>, KY Srinivasan <kys@xxxxxxxxxxxxx>, Simon Xiao <sixiao@xxxxxxxxxxxxx>, Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>, Stephen Hemminger <sthemmin@xxxxxxxxxxxxx>, "torvalds@xxxxxxxxxxxxxxxxxxxx" <torvalds@xxxxxxxxxxxxxxxxxxxx>, "luto@xxxxxxxxxx" <luto@xxxxxxxxxx>, "hpa@xxxxxxxxx" <hpa@xxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "rostedt@xxxxxxxxxxx" <rostedt@xxxxxxxxxxx>, "andy.shevchenko@xxxxxxxxx" <andy.shevchenko@xxxxxxxxx>, "tglx@xxxxxxxxxxxxx" <tglx@xxxxxxxxxxxxx>, "mingo@xxxxxxxxxx" <mingo@xxxxxxxxxx>, "linux-tip-commits@xxxxxxxxxxxxxxx" <linux-tip-commits@xxxxxxxxxxxxxxx>, boris.ostrovsky@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx
In-reply-to: <8d758a18-3db4-41c3-9748-41a649b7950b@suse.com>
References: <tip-2ffd9e33ce4af4e8cfa3e17bf493defe8474e2eb@git.kernel.org> <20170810185646.GI6524@worktop.programming.kicks-ass.net> <DM5PR21MB0476915D204F850F7F7C1475A0880@DM5PR21MB0476.namprd21.prod.outlook.com> <CY4PR21MB06313B9D59F8846CDDE443F0F1880@CY4PR21MB0631.namprd21.prod.outlook.com> <20170810192742.GJ6524@worktop.programming.kicks-ass.net> <87lgmqqwzl.fsf@vitty.brq.redhat.com> <20170811105625.hmdfnp3yh72zut33@hirez.programming.kicks-ass.net> <b369bcb0-49e6-2f50-574e-4a66ced9e05d@suse.com> <20170811123534.quyckfyspl5fqdrg@hirez.programming.kicks-ass.net> <8d758a18-3db4-41c3-9748-41a649b7950b@suse.com>
User-agent: NeoMutt/20170609 (1.8.3)

On Fri, Aug 11, 2017 at 02:46:41PM +0200, Juergen Gross wrote:
> Aah, okay. Now I understand the problem. The TLB isn't the issue but the
> IPI is serving two purposes here: TLB flushing (which is allowed to
> happen at any time) and serialization regarding access to critical pages
> (which seems to be broken in the Xen case as you suggest).

Indeed, and now hyper-v as well.
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Follow-Ups:
- Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: Juergen Gross

References:
- [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: tip-bot for Vitaly Kuznetsov
- Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: Peter Zijlstra
- RE: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: KY Srinivasan
- RE: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: Jork Loeser
- Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: Peter Zijlstra
- Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: Vitaly Kuznetsov
- Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: Peter Zijlstra
- Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: Juergen Gross
- Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: Peter Zijlstra
- Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
  - From: Juergen Gross

Prev by Date: [tip:locking/core] mm, locking: Fix up flush_tlb_pending() related merge in do_huge_pmd_numa_page()
Next by Date: Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
Previous by thread: Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
Next by thread: Re: [tip:x86/platform] x86/hyper-v: Use hypercall for remote TLB flush
Index(es):
- Date
- Thread

[Index of Archives] [Linux Stable Commits] [Linux Stable Kernel] [Linux Kernel] [Linux USB Devel] [Linux Video &Media] [Linux Audio Users] [Yosemite News] [Linux SCSI]