kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yang Zhang <yang.zhang.wz@gmail.com>
To: "Wu, Feng" <feng.wu@intel.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"rkrcmar@redhat.com" <rkrcmar@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] KVM: x86: Use vector-hashing to deliver lowest-priority interrupts
Date: Mon, 21 Dec 2015 10:06:18 +0800	[thread overview]
Message-ID: <56775E9A.5030108@gmail.com> (raw)
In-Reply-To: <E959C4978C3B6342920538CF579893F00AF027DF@SHSMSX104.ccr.corp.intel.com>

On 2015/12/21 9:50, Wu, Feng wrote:
>
>
>> -----Original Message-----
>> From: Yang Zhang [mailto:yang.zhang.wz@gmail.com]
>> Sent: Monday, December 21, 2015 9:46 AM
>> To: Wu, Feng <feng.wu@intel.com>; pbonzini@redhat.com;
>> rkrcmar@redhat.com
>> Cc: kvm@vger.kernel.org; linux-kernel@vger.kernel.org
>> Subject: Re: [PATCH v2 1/2] KVM: x86: Use vector-hashing to deliver lowest-
>> priority interrupts
>>
>> On 2015/12/16 9:37, Feng Wu wrote:
>>> Use vector-hashing to deliver lowest-priority interrupts, As an
>>> example, modern Intel CPUs in server platform use this method to
>>> handle lowest-priority interrupts.
>>>
>>> Signed-off-by: Feng Wu <feng.wu@intel.com>
>>> ---
>>>    arch/x86/kvm/irq_comm.c | 27 ++++++++++++++++++-----
>>>    arch/x86/kvm/lapic.c    | 57
>> ++++++++++++++++++++++++++++++++++++++++---------
>>>    arch/x86/kvm/lapic.h    |  2 ++
>>>    arch/x86/kvm/x86.c      |  9 ++++++++
>>>    arch/x86/kvm/x86.h      |  1 +
>>>    5 files changed, 81 insertions(+), 15 deletions(-)
>>>
>>> diff --git a/arch/x86/kvm/irq_comm.c b/arch/x86/kvm/irq_comm.c
>>> index 84b96d3..c8c5f61 100644
>>> --- a/arch/x86/kvm/irq_comm.c
>>> +++ b/arch/x86/kvm/irq_comm.c
>>> @@ -32,6 +32,7 @@
>>>    #include "ioapic.h"
>>>
>>>    #include "lapic.h"
>>> +#include "x86.h"
>>>
>>>    static int kvm_set_pic_irq(struct kvm_kernel_irq_routing_entry *e,
>>>    			   struct kvm *kvm, int irq_source_id, int level,
>>> @@ -53,8 +54,10 @@ static int kvm_set_ioapic_irq(struct
>> kvm_kernel_irq_routing_entry *e,
>>>    int kvm_irq_delivery_to_apic(struct kvm *kvm, struct kvm_lapic *src,
>>>    		struct kvm_lapic_irq *irq, unsigned long *dest_map)
>>>    {
>>> -	int i, r = -1;
>>> +	int i, r = -1, idx = 0;
>>>    	struct kvm_vcpu *vcpu, *lowest = NULL;
>>> +	unsigned long dest_vcpu_bitmap[BITS_TO_LONGS(KVM_MAX_VCPUS)];
>>> +	unsigned int dest_vcpus = 0;
>>>
>>>    	if (irq->dest_mode == 0 && irq->dest_id == 0xff &&
>>>    			kvm_lowest_prio_delivery(irq)) {
>>> @@ -65,6 +68,8 @@ int kvm_irq_delivery_to_apic(struct kvm *kvm, struct
>> kvm_lapic *src,
>>>    	if (kvm_irq_delivery_to_apic_fast(kvm, src, irq, &r, dest_map))
>>>    		return r;
>>>
>>> +	memset(dest_vcpu_bitmap, 0, sizeof(dest_vcpu_bitmap));
>>> +
>>>    	kvm_for_each_vcpu(i, vcpu, kvm) {
>>>    		if (!kvm_apic_present(vcpu))
>>>    			continue;
>>> @@ -78,13 +83,25 @@ int kvm_irq_delivery_to_apic(struct kvm *kvm, struct
>> kvm_lapic *src,
>>>    				r = 0;
>>>    			r += kvm_apic_set_irq(vcpu, irq, dest_map);
>>>    		} else if (kvm_lapic_enabled(vcpu)) {
>>> -			if (!lowest)
>>> -				lowest = vcpu;
>>> -			else if (kvm_apic_compare_prio(vcpu, lowest) < 0)
>>> -				lowest = vcpu;
>>> +			if (!kvm_vector_hashing_enabled()) {
>>> +				if (!lowest)
>>> +					lowest = vcpu;
>>> +				else if (kvm_apic_compare_prio(vcpu, lowest) <
>> 0)
>>> +					lowest = vcpu;
>>> +			} else {
>>> +				__set_bit(vcpu->vcpu_id, dest_vcpu_bitmap);
>>> +				dest_vcpus++;
>>> +			}
>>>    		}
>>>    	}
>>>
>>> +	if (dest_vcpus != 0) {
>>> +		idx = kvm_vector_2_index(irq->vector, dest_vcpus,
>>> +					 dest_vcpu_bitmap, KVM_MAX_VCPUS);
>>> +
>>> +		lowest = kvm_get_vcpu(kvm, idx - 1);
>>> +	}
>>> +
>>>    	if (lowest)
>>>    		r = kvm_apic_set_irq(lowest, irq, dest_map);
>>>
>>> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
>>> index ecd4ea1..e29001f 100644
>>> --- a/arch/x86/kvm/lapic.c
>>> +++ b/arch/x86/kvm/lapic.c
>>> @@ -678,6 +678,22 @@ bool kvm_apic_match_dest(struct kvm_vcpu *vcpu,
>> struct kvm_lapic *source,
>>>    	}
>>>    }
>>>
>>> +int kvm_vector_2_index(u32 vector, u32 dest_vcpus,
>>> +		       const unsigned long *bitmap, u32 bitmap_size)
>>> +{
>>> +	u32 mod;
>>> +	int i, idx = 0;
>>> +
>>> +	mod = vector % dest_vcpus;
>>> +
>>> +	for (i = 0; i <= mod; i++) {
>>> +		idx = find_next_bit(bitmap, bitmap_size, idx) + 1;
>>> +		BUG_ON(idx > bitmap_size);
>>> +	}
>>> +
>>> +	return idx;
>>> +}
>>> +
>>>    bool kvm_irq_delivery_to_apic_fast(struct kvm *kvm, struct kvm_lapic *src,
>>>    		struct kvm_lapic_irq *irq, int *r, unsigned long *dest_map)
>>>    {
>>> @@ -731,17 +747,38 @@ bool kvm_irq_delivery_to_apic_fast(struct kvm
>> *kvm, struct kvm_lapic *src,
>>>    		dst = map->logical_map[cid];
>>>
>>>    		if (kvm_lowest_prio_delivery(irq)) {
>>> -			int l = -1;
>>> -			for_each_set_bit(i, &bitmap, 16) {
>>> -				if (!dst[i])
>>> -					continue;
>>> -				if (l < 0)
>>> -					l = i;
>>> -				else if (kvm_apic_compare_prio(dst[i]->vcpu,
>> dst[l]->vcpu) < 0)
>>> -					l = i;
>>> +			if (!kvm_vector_hashing_enabled()) {
>>> +				int l = -1;
>>> +				for_each_set_bit(i, &bitmap, 16) {
>>> +					if (!dst[i])
>>> +						continue;
>>> +					if (l < 0)
>>> +						l = i;
>>> +					else if (kvm_apic_compare_prio(dst[i]-
>>> vcpu, dst[l]->vcpu) < 0)
>>> +						l = i;
>>> +				}
>>> +				bitmap = (l >= 0) ? 1 << l : 0;
>>> +			} else {
>>> +				int idx = 0;
>>> +				unsigned int dest_vcpus = 0;
>>> +
>>> +				for_each_set_bit(i, &bitmap, 16) {
>>> +					if (!dst[i]
>> && !kvm_lapic_enabled(dst[i]->vcpu)) {
>>
>> It should be or(||) not and (&&).
>
> Oh, you are right! My negligence! Thanks for pointing this out, Yang!

btw, i think the kvm_lapic_enabled check is wrong here? Why need it here?

>
> Thanks,
> Feng
>


-- 
best regards
yang

  reply	other threads:[~2015-12-21  2:06 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-16  1:37 [PATCH v2 0/2] Add vector-hashing support for lowest-priority interrupts delivery Feng Wu
2015-12-16  1:37 ` [PATCH v2 1/2] KVM: x86: Use vector-hashing to deliver lowest-priority interrupts Feng Wu
2015-12-21  1:46   ` Yang Zhang
2015-12-21  1:50     ` Wu, Feng
2015-12-21  2:06       ` Yang Zhang [this message]
2015-12-22  4:37         ` Wu, Feng
2015-12-22  6:49           ` Yang Zhang
2015-12-22  6:59             ` Wu, Feng
2015-12-22  7:13               ` Yang Zhang
2015-12-22  7:19                 ` Wu, Feng
2015-12-22 19:52                   ` rkrcmar
2015-12-23  2:12                     ` Wu, Feng
2015-12-23 16:42                       ` rkrcmar
2015-12-23  3:17                     ` Yang Zhang
2015-12-23 17:19   ` Radim Krčmář
2016-01-18  5:19     ` Wu, Feng
2016-01-18 10:41       ` Paolo Bonzini
2016-01-19  4:44         ` Wu, Feng
2016-01-19 13:42           ` Paolo Bonzini
2016-01-19 13:49             ` Wu, Feng
2016-01-18 14:00       ` Radim Krcmár
2015-12-16  1:37 ` [PATCH v2 2/2] KVM: x86: Add lowest-priority support for vt-d posted-interrupts Feng Wu
2015-12-21  1:50   ` Yang Zhang
2015-12-21  1:55     ` Wu, Feng
2015-12-21  2:01       ` Yang Zhang
2015-12-22  4:36         ` Wu, Feng
2015-12-22  6:42           ` Yang Zhang
2015-12-23 16:50             ` rkrcmar
2015-12-23 17:21   ` Radim Krčmář
2016-01-04  1:57     ` Wu, Feng

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=56775E9A.5030108@gmail.com \
    --to=yang.zhang.wz@gmail.com \
    --cc=feng.wu@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.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;
as well as URLs for NNTP newsgroup(s).