From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Avi Kivity <avi@redhat.com>
Cc: KVM General <kvm@vger.kernel.org>
Subject: Re: KVM_SET_MP_STATE is undocumented
Date: Mon, 26 Apr 2010 10:48:40 +0300 [thread overview]
Message-ID: <4BD54558.4000704@cs.helsinki.fi> (raw)
In-Reply-To: <4BD43AF6.4020901@redhat.com>
Hi Avi,
Avi Kivity kirjoitti:
>> I noticed that QEMU uses KVM_SET_MP_STATE but the ioctl() is
>> completely undocumented. I assume it has something to do with
>> multiprocessor but I am unable to work out the details unless I take a
>> peek at arch/x86/kvm.
>
> Patch sent.
Two more interesting but undocumented ioctls:
- KVM_SET_IDENTITY_MAP_ADDR
- KVM_SET_BOOT_CPU_ID
Little background: we're debugging a KVM_EXIT_UNKNOWN problem for the
"largest bug-free kernel" on Core i5 machine. I've been looking at
plain QEMU sources but it seems "qemu-kvm" that the person is using does
much more during initialization. Do we have a known good list of
mandatory steps required to properly initialize KVM on all CPUs?
Pekka
next prev parent reply other threads:[~2010-04-26 7:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 17:18 KVM_SET_MP_STATE is undocumented Pekka Enberg
2010-04-25 12:52 ` Avi Kivity
2010-04-26 7:48 ` Pekka Enberg [this message]
2010-04-26 13:21 ` 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=4BD54558.4000704@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox