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


Groups > linux.kernel > #1195188 > unrolled thread

[PATCH 0/2] KVM: x86: limit interactions between IOAPIC and LAPIC

Started byPaolo Bonzini <pbonzini@redhat.com>
First post2015-07-29 15:40 +0200
Last post2015-07-29 22:10 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH 0/2] KVM: x86: limit interactions between IOAPIC and LAPIC Paolo Bonzini <pbonzini@redhat.com> - 2015-07-29 15:40 +0200
    Re: [PATCH 0/2] KVM: x86: limit interactions between IOAPIC and  LAPIC Alex Williamson <alex.williamson@redhat.com> - 2015-07-29 22:10 +0200

#1195188 — [PATCH 0/2] KVM: x86: limit interactions between IOAPIC and LAPIC

FromPaolo Bonzini <pbonzini@redhat.com>
Date2015-07-29 15:40 +0200
Subject[PATCH 0/2] KVM: x86: limit interactions between IOAPIC and LAPIC
Message-ID<pRzKq-15P-21@gated-at.bofh.it>
Inspired by the split irqchip patches, this series limits the
IOAPIC<->LAPIC to the EOI exit bitmap that is inferred from the
redirection table.

TMR is entirely handled within the local APIC, and no global copy
of the IOAPIC-handled vectors is necessary anymore.  This makes
it simpler to introduce a userspace IOAPIC.

Tested with ioapic.flat for now, planning to do more complete tests
tomorrow.  The most interesting test to do here is an assigned device
that uses INTX, so I am CCing Alex Williamson for a heads up.

Paolo

Paolo Bonzini (2):
  KVM: x86: set TMR when the interrupt is accepted
  KVM: x86: store IOAPIC-handled vectors in each VCPU

 arch/x86/include/asm/kvm_host.h |  3 ++-
 arch/x86/kvm/ioapic.c           | 27 ++++-----------------------
 arch/x86/kvm/ioapic.h           | 11 +----------
 arch/x86/kvm/lapic.c            | 29 ++++++++++++++++++-----------
 arch/x86/kvm/lapic.h            |  1 -
 arch/x86/kvm/svm.c              |  2 +-
 arch/x86/kvm/vmx.c              |  3 ++-
 arch/x86/kvm/x86.c              | 11 +++--------
 8 files changed, 31 insertions(+), 56 deletions(-)

-- 
1.8.3.1

--
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]


#1195471 — Re: [PATCH 0/2] KVM: x86: limit interactions between IOAPIC and LAPIC

FromAlex Williamson <alex.williamson@redhat.com>
Date2015-07-29 22:10 +0200
SubjectRe: [PATCH 0/2] KVM: x86: limit interactions between IOAPIC and LAPIC
Message-ID<pRFPQ-1zd-9@gated-at.bofh.it>
In reply to#1195188
On Wed, 2015-07-29 at 15:37 +0200, Paolo Bonzini wrote:
> Inspired by the split irqchip patches, this series limits the
> IOAPIC<->LAPIC to the EOI exit bitmap that is inferred from the
> redirection table.
> 
> TMR is entirely handled within the local APIC, and no global copy
> of the IOAPIC-handled vectors is necessary anymore.  This makes
> it simpler to introduce a userspace IOAPIC.
> 
> Tested with ioapic.flat for now, planning to do more complete tests
> tomorrow.  The most interesting test to do here is an assigned device
> that uses INTX, so I am CCing Alex Williamson for a heads up.

Tested Windows and Linux guests with assigned devices restricted to INTx
mode, no obvious regression.  Thanks,

Alex

> Paolo Bonzini (2):
>   KVM: x86: set TMR when the interrupt is accepted
>   KVM: x86: store IOAPIC-handled vectors in each VCPU
> 
>  arch/x86/include/asm/kvm_host.h |  3 ++-
>  arch/x86/kvm/ioapic.c           | 27 ++++-----------------------
>  arch/x86/kvm/ioapic.h           | 11 +----------
>  arch/x86/kvm/lapic.c            | 29 ++++++++++++++++++-----------
>  arch/x86/kvm/lapic.h            |  1 -
>  arch/x86/kvm/svm.c              |  2 +-
>  arch/x86/kvm/vmx.c              |  3 ++-
>  arch/x86/kvm/x86.c              | 11 +++--------
>  8 files changed, 31 insertions(+), 56 deletions(-)
> 



--
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