kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Metin Kaya <metikaya@amazon.co.uk>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, x86@kernel.org,
	bp@alien8.de, dwmw@amazon.co.uk, paul@xen.org,
	tglx@linutronix.de, mingo@redhat.com,
	dave.hansen@linux.intel.com, joao.m.martins@oracle.com
Subject: Re: [PATCH v3] KVM: x86/xen: Implement hvm_op/HVMOP_flush_tlbs hypercall
Date: Fri, 26 May 2023 13:32:31 -0700	[thread overview]
Message-ID: <ZHEXX/OG6suNGWPN@google.com> (raw)
In-Reply-To: <20230418101306.98263-1-metikaya@amazon.co.uk>

On Tue, Apr 18, 2023, Metin Kaya wrote:
> Implement in-KVM support for Xen's HVMOP_flush_tlbs hypercall, which
> allows the guest to flush all vCPU's TLBs. KVM doesn't provide an
> ioctl() to precisely flush guest TLBs, and punting to userspace would
> likely negate the performance benefits of avoiding a TLB shootdown in
> the guest.
> 
> Signed-off-by: Metin Kaya <metikaya@amazon.co.uk>
> 
> ---
> v3:
>   - Addressed comments for v2.
>   - Verified with XTF/invlpg test case.
> 
> v2:
>   - Removed an irrelevant URL from commit message.
> ---
>  arch/x86/kvm/xen.c                 | 15 +++++++++++++++
>  include/xen/interface/hvm/hvm_op.h |  3 +++
>  2 files changed, 18 insertions(+)

I still don't see a testcase.

  : This doesn't even compile.  I'll give you one guess as to how much confidence I
  : have that this was properly tested.
  : 
  : Aha!  And QEMU appears to have Xen emulation support.  That means KVM-Unit-Tests
  : is an option.  Specifically, extend the "access" test to use this hypercall instead
  : of INVLPG.  That'll verify that the flush is actually being performed as expteced.

Let me be more explicit this time: I am not applying this without a test.  I don't
care how trivial a patch may seem, I'm done taking patches without test coverage
unless there's a *really* good reason for me to do so.

  parent reply	other threads:[~2023-05-26 20:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230417122206.34647-1-metikaya@amazon.co.uk>
2023-04-17 12:22 ` [PATCH v2] KVM: x86/xen: Implement hvm_op/HVMOP_flush_tlbs hypercall Metin Kaya
2023-04-17 16:31   ` Sean Christopherson
2023-04-18  9:14     ` [EXTERNAL][PATCH " David Woodhouse
2023-04-18 10:13       ` [PATCH v3] " Metin Kaya
2023-04-18 10:48         ` Paul Durrant
2023-04-18 11:04           ` Kaya, Metin
2023-04-18 11:13             ` Paul Durrant
2023-04-18 11:05           ` [EXTERNAL][PATCH " David Woodhouse
2023-05-26 20:32         ` Sean Christopherson [this message]
2023-07-25 12:56           ` [PATCH " David Woodhouse
2023-07-26 20:07             ` Sean Christopherson
2023-07-27 12:04               ` David Woodhouse
2023-07-28  7:31                 ` Kaya, Metin
2023-08-04  0:22         ` Sean Christopherson
2023-04-18 14:44       ` [EXTERNAL][PATCH v2] " Sean Christopherson
2023-04-18 15:47         ` David Woodhouse
2023-04-18 16:08           ` David Woodhouse

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=ZHEXX/OG6suNGWPN@google.com \
    --to=seanjc@google.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=dwmw@amazon.co.uk \
    --cc=joao.m.martins@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=metikaya@amazon.co.uk \
    --cc=mingo@redhat.com \
    --cc=paul@xen.org \
    --cc=pbonzini@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).