From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@web.de>
Subject: Re: List of unaccessible x86 states
Date: Fri, 23 Oct 2009 21:34:50 +0200
Message-ID: <4AE2055A.3050001@web.de>
References: <4ADDB49B.3010101@siemens.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigD2D862A99DC7DB601C56241E"
Cc: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>,
	Gleb Natapov <gleb@redhat.com>, Alexander Graf <agraf@suse.de>
To: kvm-devel <kvm@vger.kernel.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from fmmailgate02.web.de ([217.72.192.227]:33663 "EHLO
	fmmailgate02.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753078AbZJWTer (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 23 Oct 2009 15:34:47 -0400
In-Reply-To: <4ADDB49B.3010101@siemens.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigD2D862A99DC7DB601C56241E
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Jan Kiszka wrote:
> Hi all,
>=20
> as the list of yet user-unaccessible x86 states is a bit volatile ATM,
> this is an attempt to collect the precise requirements for additional
> state fields. Once everyone feels the list is complete, we can decide
> how to partition it into one ore more substates for the new
> KVM_GET/SET_VCPU_STATE interface.
>=20
> What I read so far (or tried to patch already):
>=20
> - nmi_masked
> - nmi_pending
> - nmi_injected
> - kvm_queued_exception (whole struct content)
> - KVM_REQ_TRIPLE_FAULT (from vcpu.requests)
>=20
> Unclear points (for me) from the last discussion:
>=20
> - sipi_vector
> - MCE (covered via kvm_queued_exception, or does it require more?)
>=20
> Please extend or correct the list as required.
>=20

Here is a wrap-up of what has been reported so far:

 - NMI
    o nmi_masked
    o nmi_pending
    o nmi_injected
 - queued exception
    o kvm_queued_exception
    o triple_fault
 - SVM
    o gif
    (Are we sure that there is really nothing more here?)
 - sipi_vector

So the next question is how to map these on substates. I'm currently
leaning towards this organization:

 - KVM_X86_VCPU_STATE_EVENTS
    o NMI states
    o pending exception
    o sipi_vector
    o pending interrupt?
      (would be redundant to kvm_sregs.interrupt_bitmap, but that struct
      may be obsoleted one day)
 - KVM_X86_VCPU_STATE_SVM
    o gif

Any concerns or better suggestions?

Jan


--------------enigD2D862A99DC7DB601C56241E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkriBVoACgkQitSsb3rl5xRFawCg7fkOIlJZ0Mi5y4N4vtP20raa
7gcAoPA1u6BgY+9k3VcguTGM6FxFhHmC
=b8ae
-----END PGP SIGNATURE-----

--------------enigD2D862A99DC7DB601C56241E--