All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: KVM guest interrupts, traps, and, exceptions
Date: Sat, 27 Mar 2010 17:43:55 +0200	[thread overview]
Message-ID: <4BAE27BB.8040000@cs.helsinki.fi> (raw)

Hi Avi,

I'm continuing my journey through the KVM API documentation and I'm now 
scratching my head on how interrupts, traps, and exceptions are 
supported by the API. I see KVM_CREATE_IRQCHIP and KVM_IRQ_LINE but I'm 
unable to work out how the host is notified of such events. For example, 
if the guest does

   int $0x10

is there some KVM_EXIT "exit reason" like we have for IO? Is there some 
other mechanism for that? As I haven't yet set up anything related to 
IRQs I can see the host just deadlock on user interrupts.

			Pekka

             reply	other threads:[~2010-03-27 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-27 15:43 Pekka Enberg [this message]
2010-03-27 16:15 ` KVM guest interrupts, traps, and, exceptions Alexander Graf
2010-03-27 16:42   ` Pekka Enberg
2010-03-27 16:45     ` Alexander Graf

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=4BAE27BB.8040000@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=avi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.