From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Pekka Enberg <penberg@kernel.org>,
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 11:50:20 +0300 [thread overview]
Message-ID: <4DB7D8CC.7020902@redhat.com> (raw)
In-Reply-To: <20110427082652.GK2265@redhat.com>
On 04/27/2011 11:26 AM, Gleb Natapov wrote:
> On Wed, Apr 27, 2011 at 11:20:29AM +0300, Avi Kivity wrote:
> > On 04/27/2011 10:53 AM, Pekka Enberg wrote:
> > >On Wed, Apr 27, 2011 at 10:37 AM, Avi Kivity<avi@redhat.com> wrote:
> > >> KVM_SET_GSI_ROUTING - manipulate the routes between irq lines and the IOAPIC
> > >> and PIC; also maintain virtual routes for message signalled interrupts (MSI)
> > >
> > >Is this mandatory to set up manually for lapic to work or does KVM set
> > >these up automatically (like it does for most ioctls) to something
> > >sane?
> >
> > The defaults are all sane (including the APIC ID).
> >
> But IIRC the only way to reset BSP lapic to its initial state is to call
> KVM_SET_LAPIC with buffer filled with initial values. The same is true
> for non-BSP lapics too if they are reset by machine reset (as opposite
> to by INIT message).
Right, we do need a reset system in kvm.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-04-27 8:50 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
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 [this message]
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=4DB7D8CC.7020902@redhat.com \
--to=avi@redhat.com \
--cc=gleb@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