From: Paolo Bonzini <pbonzini@redhat.com>
To: "Wu, Feng" <feng.wu@intel.com>,
"Zhang, Yang Z" <yang.z.zhang@intel.com>,
Alex Williamson <alex.williamson@redhat.com>
Cc: "gleb@kernel.org" <gleb@kernel.org>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"joro@8bytes.org" <joro@8bytes.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 05/13] KVM: Update IRTE according to guest interrupt configuration changes
Date: Wed, 12 Nov 2014 10:56:26 +0100 [thread overview]
Message-ID: <54632ECA.4070903@redhat.com> (raw)
In-Reply-To: <E959C4978C3B6342920538CF579893F00227680F@SHSMSX104.ccr.corp.intel.com>
On 12/11/2014 10:19, Wu, Feng wrote:
>> You can certainly backport these patches to distros that do not have
>> VFIO. But upstream we should work on VFIO first. VFIO has feature
>> parity with legacy device assignment, and adding a new feature that is
>> not in VFIO would be a bad idea.
>>
>> By the way, do you have benchmark results for it? We have not been able
>> to see any performance improvement for APICv on e.g. netperf.
>
> Do you mean benchmark results for APICv itself or VT-d Posted-Interrtups?
Especially for VT-d posted interrupts---but it'd be great to know which
workloads see the biggest speedup from APICv.
Paolo
next prev parent reply other threads:[~2014-11-12 9:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 9:20 [PATCH 05/13] KVM: Update IRTE according to guest interrupt configuration changes Wu, Feng
2014-11-11 11:01 ` Paolo Bonzini
2014-11-11 12:28 ` Wu, Feng
2014-11-12 3:42 ` Zhang, Yang Z
2014-11-12 9:14 ` Paolo Bonzini
2014-11-12 9:19 ` Wu, Feng
2014-11-12 9:56 ` Paolo Bonzini [this message]
2014-11-13 1:14 ` Wu, Feng
2014-11-13 1:21 ` Zhang, Yang Z
2014-11-13 1:30 ` Wu, Feng
2014-11-13 1:46 ` Zhang, Yang Z
2014-11-12 17:11 ` Alex Williamson
-- strict thread matches above, loose matches on Subject: below --
2014-11-11 13:02 Wu, Feng
2014-11-11 11:22 Wu, Feng
2014-11-10 6:26 [PATCH 00/13] Add VT-d Posted-Interrupts support for KVM Feng Wu
2014-11-10 6:26 ` [PATCH 05/13] KVM: Update IRTE according to guest interrupt configuration changes Feng Wu
2014-11-10 21:57 ` Alex Williamson
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=54632ECA.4070903@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=dwmw2@infradead.org \
--cc=feng.wu@intel.com \
--cc=gleb@kernel.org \
--cc=hpa@zytor.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yang.z.zhang@intel.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