mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: pbonzini@redhat.com, mlevitsk@redhat.com, seanjc@google.com,
	joro@8bytes.org, jon.grimm@amd.com, wei.huang2@amd.com,
	terry.bowman@amd.com
Subject: Re: [PATCH 0/2] KVM: SVM: Optimize AVIC incomplete IPI #vmexit handling
Date: Mon, 18 Apr 2022 21:39:29 +0700	[thread overview]
Message-ID: <81bb5fd1-2241-3ea4-dd52-a1eaa2101997@amd.com> (raw)
In-Reply-To: <20220414051151.77710-1-suravee.suthikulpanit@amd.com>



On 4/14/22 12:11 PM, Suravee Suthikulpanit wrote:
> This series introduce a fast-path when handling AVIC incomplete IPI #vmexit
> for AVIC and x2AVIC, and introduce a new tracepoint for the slow-path
> processing.
> 
> Please note that the prereq of this series is:
>    [PATCH v2 00/12] Introducing AMD x2APIC Virtualization (x2AVIC) support
>    (https://lore.kernel.org/lkml/20220412115822.14351-2-suravee.suthikulpanit@amd.com/T/)
> 

Since x2AVIC stuff is still under development, and likely will need v3,
I will extract the logic for x2AVIC, and send out V2 of this series.
The support for x2AVIC will be send separately.

Regards,
Suravee

      parent reply	other threads:[~2022-04-18 15:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14  5:11 Suravee Suthikulpanit
2022-04-14  5:11 ` [PATCH 1/2] KVM: SVM: Introduce avic_kick_target_vcpus_fast() Suravee Suthikulpanit
2022-04-14 19:21   ` Sean Christopherson
2022-04-18 11:02   ` Maxim Levitsky
2022-04-14  5:11 ` [PATCH 2/2] KVM: SVM: Introduce trace point for the slow-path of avic_kic_target_vcpus Suravee Suthikulpanit
2022-04-18 11:03   ` Maxim Levitsky
2022-04-18 14:39 ` Suravee Suthikulpanit [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=81bb5fd1-2241-3ea4-dd52-a1eaa2101997@amd.com \
    --to=suravee.suthikulpanit@amd.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=pbonzini@redhat.com \
    --cc=seanjc@google.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®