From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm-devel <kvm@vger.kernel.org>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>
Subject: List of unaccessible x86 states
Date: Tue, 20 Oct 2009 15:01:15 +0200 [thread overview]
Message-ID: <4ADDB49B.3010101@siemens.com> (raw)
Hi all,
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.
What I read so far (or tried to patch already):
- nmi_masked
- nmi_pending
- nmi_injected
- kvm_queued_exception (whole struct content)
- KVM_REQ_TRIPLE_FAULT (from vcpu.requests)
Unclear points (for me) from the last discussion:
- sipi_vector
- MCE (covered via kvm_queued_exception, or does it require more?)
Please extend or correct the list as required.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next reply other threads:[~2009-10-20 13:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-20 13:01 Jan Kiszka [this message]
2009-10-20 13:10 ` List of unaccessible x86 states Alexander Graf
2009-10-20 13:19 ` Jan Kiszka
2009-10-20 13:27 ` Gleb Natapov
2009-10-20 13:29 ` Jan Kiszka
2009-10-20 13:32 ` Gleb Natapov
2009-10-20 13:27 ` Alexander Graf
2009-10-20 13:37 ` Jan Kiszka
2009-10-20 13:41 ` Alexander Graf
2009-10-20 13:48 ` Gleb Natapov
2009-10-20 13:51 ` Alexander Graf
2009-10-20 18:55 ` Gleb Natapov
2009-10-20 18:59 ` Alexander Graf
2009-10-20 19:09 ` Gleb Natapov
2009-10-20 19:23 ` Alexander Graf
2009-10-20 19:31 ` Gleb Natapov
2009-10-25 9:46 ` Avi Kivity
2009-10-25 13:53 ` Alexander Graf
2009-10-25 14:08 ` Avi Kivity
2009-10-25 16:45 ` Alexander Graf
2009-10-26 8:33 ` Avi Kivity
2009-10-26 9:11 ` Alexander Graf
2009-10-26 9:19 ` Avi Kivity
2009-10-20 13:35 ` Gleb Natapov
2009-10-20 18:45 ` Marcelo Tosatti
2009-10-23 13:08 ` Jan Kiszka
2009-10-23 17:00 ` Marcelo Tosatti
2009-10-23 19:26 ` Jan Kiszka
2009-10-23 19:34 ` Jan Kiszka
2009-10-24 10:35 ` Alexander Graf
2009-10-25 9:49 ` Avi Kivity
2009-10-26 9:17 ` Joerg Roedel
2009-10-26 9:21 ` Avi Kivity
2009-10-26 9:30 ` Joerg Roedel
2009-10-26 9:39 ` Avi Kivity
2009-10-26 9:56 ` Joerg Roedel
2009-10-26 10:09 ` Avi Kivity
2009-10-26 10:45 ` Joerg Roedel
2009-10-26 10:56 ` Avi Kivity
2009-10-26 11:10 ` Joerg Roedel
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=4ADDB49B.3010101@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).