From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: KVM_SET_MP_STATE is undocumented
Date: Mon, 26 Apr 2010 10:48:40 +0300
Message-ID: <4BD54558.4000704@cs.helsinki.fi>
References: <4BD084E7.3020609@cs.helsinki.fi> <4BD43AF6.4020901@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: KVM General <kvm@vger.kernel.org>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from courier.cs.helsinki.fi ([128.214.9.1]:37953 "EHLO
	mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1754675Ab0DZHsm (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 26 Apr 2010 03:48:42 -0400
In-Reply-To: <4BD43AF6.4020901@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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