mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: mlevitsk@redhat.com, seanjc@google.com, joro@8bytes.org,
	jon.grimm@amd.com, wei.huang2@amd.com, terry.bowman@amd.com
Subject: Re: [PATCH V2 0/2] KVM: SVM: Optimize AVIC incomplete IPI #vmexit handling
Date: Wed, 20 Apr 2022 18:42:04 +0200	[thread overview]
Message-ID: <36ffc0e3-ac2d-be99-002b-916c1e0797b8@redhat.com> (raw)
In-Reply-To: <20220420154954.19305-1-suravee.suthikulpanit@amd.com>

On 4/20/22 17:49, Suravee Suthikulpanit wrote:
> This series introduce a fast-path when handling AVIC incomplete IPI #vmexit
> for AVIC, and introduce a new tracepoint for the slow-path processing.
> 
> Regards,
> Suravee
> 
> Change from v1: (https://lore.kernel.org/lkml/20220414051151.77710-1-suravee.suthikulpanit@amd.com/T/)
>   * Rebased on top of Linux 5.18-rc3
>   * Patch 1/2:
>      - Update commit shortlog to be more meaningful
>      - Refactor to remove x2AVIC related logic for now, which will be included
>        in the x2AVIC patch series.
> 
> Suravee Suthikulpanit (2):
>    KVM: SVM: Use target APIC ID to complete AVIC IRQs when possible
>    KVM: SVM: Introduce trace point for the slow-path of
>      avic_kic_target_vcpus
> 
>   arch/x86/kvm/svm/avic.c | 74 ++++++++++++++++++++++++++++++++++++++---
>   arch/x86/kvm/trace.h    | 20 +++++++++++
>   arch/x86/kvm/x86.c      |  1 +
>   3 files changed, 91 insertions(+), 4 deletions(-)
> 

Queued, thanks.

Paolo

      parent reply	other threads:[~2022-04-20 16:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-20 15:49 Suravee Suthikulpanit
2022-04-20 15:49 ` [PATCH 1/2] KVM: SVM: Use target APIC ID to complete AVIC IRQs when possible Suravee Suthikulpanit
2022-04-20 15:49 ` [PATCH 2/2] KVM: SVM: Introduce trace point for the slow-path of avic_kic_target_vcpus Suravee Suthikulpanit
2022-04-20 16:42 ` Paolo Bonzini [this message]

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=36ffc0e3-ac2d-be99-002b-916c1e0797b8@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jon.grimm@amd.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlevitsk@redhat.com \
    --cc=seanjc@google.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=terry.bowman@amd.com \
    --cc=wei.huang2@amd.com \
    /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

all inboxes | Powered by JetHome®