From: "Li,Rongqing" <lirongqing@baidu.com>
To: "Yuan,Zhaoxiong" <yuanzhaoxiong@baidu.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"seanjc@google.com" <seanjc@google.com>,
"wanpengli@tencent.com" <wanpengli@tencent.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"jmattson@google.com" <jmattson@google.com>,
"joro@8bytes.org" <joro@8bytes.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"bp@alien8.de" <bp@alien8.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 答复: [PATCH v2] KVM: X86: Introduce vfio_intr_stat per-vm debugfs file
Date: Fri, 25 Feb 2022 02:27:39 +0000 [thread overview]
Message-ID: <dd872a587e874576900bec770d244ad7@baidu.com> (raw)
In-Reply-To: <1644324020-17639-1-git-send-email-yuanzhaoxiong@baidu.com>
> 主题: [PATCH v2] KVM: X86: Introduce vfio_intr_stat per-vm debugfs file
>
> Use this file to export correspondence between guest_irq, host_irq, vector and
> vcpu belonging to VFIO passthrough devices.
>
> An example output of this looks like (a vm with VFIO passthrough
> devices):
> guest_irq host_irq vector vcpu
> 24 201 37 8
> 25 202 35 25
> 26 203 35 20
> ......
>
> When a VM has VFIO passthrough devices, the correspondence between
> guest_irq, host_irq, vector and vcpu may need to be known especially in AMD
> platform with avic disabled. The AMD avic is disabled, and the passthrough
> devices may cause vcpu vm exit twice for a interrupt.
> One extrernal interrupt caused by vfio host irq, other ipi to inject a interrupt to
> vm.
>
> If the system administrator known these information, set vfio host irq affinity to
> Pcpu which the correspondece guest irq affinited vcpu, to avoid extra vm exit.
>
> Co-developed-by: Li RongQing <lirongqing@baidu.com>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
> Signed-off-by: Yuan ZhaoXiong <yuanzhaoxiong@baidu.com>
> ---
Ping
Thanks
-Li
prev parent reply other threads:[~2022-02-25 3:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 12:40 Yuan ZhaoXiong
2022-02-25 2:27 ` Li,Rongqing [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=dd872a587e874576900bec770d244ad7@baidu.com \
--to=lirongqing@baidu.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=x86@kernel.org \
--cc=yuanzhaoxiong@baidu.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®