From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: 3.14+@char.us.oracle.com, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, david.vrabel@citrix.com,
jbeulich@suse.com, xen-devel@lists.xenproject.org,
#@char.us.oracle.com
Subject: Re: [PATCH] xen/x86/pvh: Use HVM's flush_tlb_others op
Date: Mon, 14 Dec 2015 10:27:13 -0500 [thread overview]
Message-ID: <20151214152713.GC23203@char.us.oracle.com> (raw)
In-Reply-To: <1449966355-10611-1-git-send-email-boris.ostrovsky@oracle.com>
On Sat, Dec 12, 2015 at 07:25:55PM -0500, Boris Ostrovsky wrote:
> Using MMUEXT_TLB_FLUSH_MULTI doesn't buy us much since the hypervisor
> will likely perform same IPIs as would have the guest.
>
But if the VCPU is asleep, doing it via the hypervisor will save us waking
up the guest VCPU, sending an IPI - just to do an TLB flush
of that CPU. Which is pointless as the CPU hadn't been running the
guest in the first place.
>
>More importantly, using MMUEXT_INVLPG_MULTI may not to invalidate the
>guest's address on remote CPU (when, for example, VCPU from another
>guest
>is running there).
Right, so the hypervisor won't even send an IPI there.
But if you do it via the normal guest IPI mechanism (which are opaque
to the hypervisor) you and up scheduling the guest VCPU to do
send an hypervisor callback. And the callback will go the IPI routine
which will do an TLB flush. Not necessary.
This is all in case of oversubscription of course. In the case where
we are fine on vCPU resources it does not matter.
Perhaps if we have PV aware TLB flush it could do this differently?
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> Suggested-by: Jan Beulich <jbeulich@suse.com>
> Cc: stable@vger.kernel.org # 3.14+
> ---
> arch/x86/xen/mmu.c | 9 ++-------
> 1 files changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/arch/x86/xen/mmu.c b/arch/x86/xen/mmu.c
> index 9c479fe..9ed7eed 100644
> --- a/arch/x86/xen/mmu.c
> +++ b/arch/x86/xen/mmu.c
> @@ -2495,14 +2495,9 @@ void __init xen_init_mmu_ops(void)
> {
> x86_init.paging.pagetable_init = xen_pagetable_init;
>
> - /* Optimization - we can use the HVM one but it has no idea which
> - * VCPUs are descheduled - which means that it will needlessly IPI
> - * them. Xen knows so let it do the job.
> - */
> - if (xen_feature(XENFEAT_auto_translated_physmap)) {
> - pv_mmu_ops.flush_tlb_others = xen_flush_tlb_others;
> + if (xen_feature(XENFEAT_auto_translated_physmap))
> return;
> - }
> +
> pv_mmu_ops = xen_mmu_ops;
>
> memset(dummy_mapping, 0xff, PAGE_SIZE);
> --
> 1.7.1
>
next prev parent reply other threads:[~2015-12-14 15:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 0:25 [PATCH] xen/x86/pvh: Use HVM's flush_tlb_others op Boris Ostrovsky
2015-12-14 13:58 ` [Xen-devel] " David Vrabel
2015-12-14 14:05 ` Boris Ostrovsky
2015-12-14 14:05 ` Boris Ostrovsky
2015-12-14 13:58 ` David Vrabel
2015-12-14 15:27 ` Konrad Rzeszutek Wilk [this message]
2015-12-14 15:35 ` [Xen-devel] " Roger Pau Monné
2015-12-14 15:58 ` Boris Ostrovsky
2015-12-14 15:58 ` Boris Ostrovsky
2015-12-14 15:58 ` Boris Ostrovsky
2015-12-14 15:35 ` Roger Pau Monné
2015-12-15 14:36 ` Boris Ostrovsky
2015-12-15 14:36 ` Boris Ostrovsky
2015-12-15 15:03 ` Jan Beulich
2015-12-15 15:03 ` Jan Beulich
2015-12-15 15:14 ` Boris Ostrovsky
2015-12-15 15:24 ` Jan Beulich
2015-12-15 15:24 ` Jan Beulich
2015-12-15 15:37 ` Boris Ostrovsky
2015-12-15 15:37 ` Boris Ostrovsky
2015-12-15 16:07 ` Jan Beulich
2015-12-15 15:14 ` Boris Ostrovsky
-- strict thread matches above, loose matches on Subject: below --
2015-12-13 0:25 Boris Ostrovsky
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=20151214152713.GC23203@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=#@char.us.oracle.com \
--cc=3.14+@char.us.oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jbeulich@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.