From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>, konrad.wilk@oracle.com
Cc: xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
jbeulich@suse.com
Subject: Re: [Xen-devel] [PATCH] xen/x86/pvh: Use HVM's flush_tlb_others op
Date: Mon, 14 Dec 2015 09:05:34 -0500 [thread overview]
Message-ID: <566ECCAE.7080702@oracle.com> (raw)
In-Reply-To: <566ECB19.70106@citrix.com>
On 12/14/2015 08:58 AM, David Vrabel wrote:
> On 13/12/15 00:25, 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.
>>
>> 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).
>>
>> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> Suggested-by: Jan Beulich <jbeulich@suse.com>
>> Cc: stable@vger.kernel.org # 3.14+
> Applied to for-linus-4.4, thanks. But given that PVH is experimental
> I've dropped the stable Cc.
The reason I want this to go to stable is that I will be removing access
to MMUEXT_TLB_FLUSH_MULTI and MMUEXT_INVLPG_MULTI to PVH guests in the
hypervisor (as part of merging HVM and PVH hypercall tables) and that
will result in essentially unbootable PVH guests due to warnings flood.
-boris
next prev parent reply other threads:[~2015-12-14 14:05 UTC|newest]
Thread overview: 22+ 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 [this message]
2015-12-14 13:58 ` David Vrabel
2015-12-14 15:27 ` Konrad Rzeszutek Wilk
2015-12-14 15:35 ` Roger Pau Monné
2015-12-14 15:35 ` [Xen-devel] " Roger Pau Monné
2015-12-14 15:58 ` Boris Ostrovsky
2015-12-14 15:58 ` [Xen-devel] " Boris Ostrovsky
2015-12-14 15:58 ` 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
2015-12-15 14:36 ` 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=566ECCAE.7080702@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jbeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@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.