public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH v2 00/16] interrupt injection rework
Date: Wed, 29 Apr 2009 12:46:18 +0200	[thread overview]
Message-ID: <49F82FFA.9000800@siemens.com> (raw)
In-Reply-To: <20090429103510.GB19927@redhat.com>

Gleb Natapov wrote:
> On Wed, Apr 29, 2009 at 12:33:09PM +0200, Jan Kiszka wrote:
>> Gleb Natapov wrote:
>>> On Wed, Apr 29, 2009 at 11:30:46AM +0200, Jan Kiszka wrote:
>>>> Avi Kivity wrote:
>>>>> Gleb Natapov wrote:
>>>>>> Hi,
>>>>>>
>>>>>> This patch series aims to consolidate IRQ injection code for in kernel
>>>>>> IRQ chip and userspace one. Also to move IRQ injection logic from
>>>>>> SVM/VMX specific code to x86.c.
>>>>>>   
>>>>> Applied all, thanks for this excellent patchset.
>>>>>
>>>> Hmm, to which branch? Or did you just forget to also push it...
>>>>
>>>> Gleb, what is your current schedule regarding single-step on NMI iret?
>>>>
>>> I was going to look at it shortly. BTW there are other cases when single
>>> stepping is required. For instance if exception is injected and there is
>>> NMI pending NMI should be injected immediately after exception handler
>>> is started, but currently it happens only after a next exit.
>> So we basically need an NMI windows notification that not only triggers
>> on iret completion. Sounds OK.
>>
> But we don't have one on SVM :(

Yeah - and I was so optimistic that AMD managed to deliver an easily
implementable interface right from the beginning. Intel required two
steps, and the result has still some traps. Now it turns out also AMD
complicated NMI virtualization, IMHO needlessly. Well, but as we all
constantly seek for challenges... ;)

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-04-29 10:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21 14:44 [PATCH v2 00/16] interrupt injection rework Gleb Natapov
2009-04-21 14:44 ` [PATCH v2 01/16] Make kvm_cpu_(has|get)_interrupt() work for userspace irqchip too Gleb Natapov
2009-04-21 14:44 ` [PATCH v2 02/16] Consolidate userspace and kernel interrupt injection for VMX Gleb Natapov
2009-04-21 14:44 ` [PATCH v2 03/16] Cleanup vmx_intr_assist() Gleb Natapov
2009-04-21 14:44 ` [PATCH v2 04/16] Use kvm_arch_interrupt_allowed() instead of checking interrupt_window_open directly Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 05/16] Coalesce userspace/kernel irqchip interrupt injection logic Gleb Natapov
2009-04-23 14:14   ` Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 06/16] Use EVENTINJ to inject interrupts Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 07/16] Remove exception_injected() callback Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 08/16] Remove inject_pending_vectors() callback Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 09/16] kvm_push_irq() no longer used Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 10/16] sync_lapic_to_cr8() should always sync cr8 to V_TPR Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 11/16] Do not report TPR write to userspace if new value bigger or equal to a previous one Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 12/16] Get rid of arch.interrupt_window_open & arch.nmi_window_open Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 13/16] Add NMI injection support to SVM Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 14/16] Move interrupt injection logic to x86.c Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 15/16] Fix userspace IRQ chip migration Gleb Natapov
2009-04-21 14:45 ` [PATCH v2 16/16] Get rid of get_irq() callback Gleb Natapov
2009-04-27 11:19 ` [PATCH v2 00/16] interrupt injection rework Avi Kivity
2009-04-29  9:30   ` Jan Kiszka
2009-04-29 10:22     ` Gleb Natapov
2009-04-29 10:33       ` Jan Kiszka
2009-04-29 10:35         ` Gleb Natapov
2009-04-29 10:46           ` Jan Kiszka [this message]
2009-04-29 10:40     ` Avi Kivity
2009-04-29 10:47       ` Jan Kiszka

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=49F82FFA.9000800@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    /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