public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: KVM General <kvm@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Cyrill Gorcunov <gorcunov@gmail.com>
Subject: Re: Undocumented KVM_SET_LAPIC ioctl()
Date: Wed, 27 Apr 2011 10:37:58 +0300	[thread overview]
Message-ID: <4DB7C7D6.7000502@redhat.com> (raw)
In-Reply-To: <BANLkTinBhazJ3J_QcNsKh6pXaU+BuVpeAw@mail.gmail.com>

On 04/27/2011 10:23 AM, Pekka Enberg wrote:
> Hi!
>
> We're currently having issues while trying to make the KVM in-kernel
> lapic to work. There seems to be a KVM_SET_LAPIC ioctl() for this but
> it's not documented in Documentation/kvm/api.txt. Are there other
> ioctls we should know about? We're using KVM_CREATE_IRQCHIP obviously.

Plenty, yes.

KVM_IRQ_LINE - raise or lower an irq line.
KVM_GET_IRQCHIP/KVM_SET_IRQCHIP - save/restore PIC/IOAPIC states.
KVM_CREATE_PIT2/KVM_GET_PIT2/KVM_SET_PIT2 - PIT support (optional)
KVM_IRQ_LINE_STATUS - like KVM_IRQ_LINE, but provide information about 
whether the interrupt was coalesced or not.  Useful for compensating for 
time drift.
KVM_SET_GSI_ROUTING - manipulate the routes between irq lines and the 
IOAPIC and PIC; also maintain virtual routes for message signalled 
interrupts (MSI)
KVM_IRQFD - raise an edge-triggered interrupt via an eventfd; useful for 
talking to a guest from outside its host process
KVM_GET_LAPIC/KVM_SET_LAPIC - save/restore local APIC register state


I'll post documentation patches.  To get started, KVM_SET_LAPIC is 
simple - it simply accepts a 1K buffer that maps 1:1 to local APIC 
registers as documented in the Intel SDM, volume 3.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-04-27  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  7:23 Undocumented KVM_SET_LAPIC ioctl() Pekka Enberg
2011-04-27  7:37 ` Avi Kivity [this message]
2011-04-27  7:53   ` Pekka Enberg
2011-04-27  8:20     ` Avi Kivity
2011-04-27  8:26       ` Gleb Natapov
2011-04-27  8:50         ` Avi Kivity

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=4DB7C7D6.7000502@redhat.com \
    --to=avi@redhat.com \
    --cc=gorcunov@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=penberg@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