Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1242680 > unrolled thread

Re: [PATCH] KVM: x86: don't notify userspace IOAPIC on edge EOI

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH] KVM: x86: don't notify userspace IOAPIC on edge EOI Radim Krčmář <rkrcmar@redhat.com> - 2015-10-08 20:40 +0200
    Re: [PATCH] KVM: x86: don't notify userspace IOAPIC on edge EOI Paolo Bonzini <pbonzini@redhat.com> - 2015-10-09 13:10 +0200

#1242680 — Re: [PATCH] KVM: x86: don't notify userspace IOAPIC on edge EOI

2015-10-08 20:30+0200, Radim Krčmář:
> On real hardware, edge-triggered interrupts don't set a bit in TMR,
> which means that IOAPIC isn't notified on EOI.  Do the same here.
> 
> Staying in guest/kernel mode after edge EOI is what we want for most
> devices.  If some bugs could be nicely worked around with edge EOI
> notifications, we should invest in a better interface.
> 
> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
> ---
>  Completely untested.
>  
> diff --git a/arch/x86/kvm/irq_comm.c b/arch/x86/kvm/irq_comm.c
> @@ -389,13 +389,15 @@ void kvm_scan_ioapic_routes(struct kvm_vcpu *vcpu, u64 *eoi_exit_bitmap)
>  	for (i = 0; i < nr_ioapic_pins; ++i) {
>  		hlist_for_each_entry(entry, &table->map[i], link) {
>  			u32 dest_id, dest_mode;
> +			bool level;
>  
>  			if (entry->type != KVM_IRQ_ROUTING_MSI)
>  				continue;
>  			dest_id = (entry->msi.address_lo >> 12) & 0xff;
>  			dest_mode = (entry->msi.address_lo >> 2) & 0x1;
> -			if (kvm_apic_match_dest(vcpu, NULL, 0, dest_id,
> -						dest_mode)) {
> +			level = entry->msi.data & MSI_DATA_TRIGGER_LEVEL;
> +			if (level && kvm_apic_match_dest(vcpu, NULL, 0,

Describing that result is an overkill -- I'll send v2 if the idea is
accepted.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]

#1243247

On 08/10/2015 20:34, Radim Krčmář wrote:
> 2015-10-08 20:30+0200, Radim Krčmář:
>> On real hardware, edge-triggered interrupts don't set a bit in TMR,
>> which means that IOAPIC isn't notified on EOI.  Do the same here.
>>
>> Staying in guest/kernel mode after edge EOI is what we want for most
>> devices.  If some bugs could be nicely worked around with edge EOI
>> notifications, we should invest in a better interface.
>>
>> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
>> ---
>>  Completely untested.
>>  
>> diff --git a/arch/x86/kvm/irq_comm.c b/arch/x86/kvm/irq_comm.c
>> @@ -389,13 +389,15 @@ void kvm_scan_ioapic_routes(struct kvm_vcpu *vcpu, u64 *eoi_exit_bitmap)
>>  	for (i = 0; i < nr_ioapic_pins; ++i) {
>>  		hlist_for_each_entry(entry, &table->map[i], link) {
>>  			u32 dest_id, dest_mode;
>> +			bool level;
>>  
>>  			if (entry->type != KVM_IRQ_ROUTING_MSI)
>>  				continue;
>>  			dest_id = (entry->msi.address_lo >> 12) & 0xff;
>>  			dest_mode = (entry->msi.address_lo >> 2) & 0x1;
>> -			if (kvm_apic_match_dest(vcpu, NULL, 0, dest_id,
>> -						dest_mode)) {
>> +			level = entry->msi.data & MSI_DATA_TRIGGER_LEVEL;
>> +			if (level && kvm_apic_match_dest(vcpu, NULL, 0,
> 
> Describing that result is an overkill -- I'll send v2 if the idea is
> accepted.

It's okay and it matches the other lines before.  I'm applying this too,
but I would appreciate Steve's Tested-by before moving it to kvm/next.


Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web