From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: Heads up: More user-unaccessible x86 states?
Date: Mon, 05 Oct 2009 08:18:36 +0200 [thread overview]
Message-ID: <4AC98FBC.3030509@redhat.com> (raw)
In-Reply-To: <4AC8F282.3090307@web.de>
On 10/04/2009 09:07 PM, Jan Kiszka wrote:
>> btw, instead of adding a new ioctl, perhaps it makes sense to define a
>> new KVM_VCPU_STATE structure that holds all current and future state
>> (with generous reserved space), instead of separating state over a dozen
>> ioctls.
>>
>>
> OK, makes sense. With our without lapic state?
I'm in two minds. I'm leaning towards including lapic but would welcome
arguments either way.
Note we have to be careful with timers such as the tsc and lapic timer.
Maybe have a bitmask at the front specifying which elements are active.
> How much "future space"?
>
avx will change the sse registers from 16x16 to 16x32, with a hint of
more to come. Nested vmx needs the vmptr and some more bits. MSRs are
potentially endless. Lots of space.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-10-05 6:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AC86404.3090209@web.de>
[not found] ` <4AC87299.4040508@redhat.com>
[not found] ` <4AC87E08.5070908@web.de>
[not found] ` <4AC88BF2.7080200@redhat.com>
2009-10-04 19:07 ` Heads up: More user-unaccessible x86 states? Jan Kiszka
2009-10-05 6:18 ` Avi Kivity [this message]
2009-10-05 7:43 ` Jan Kiszka
2009-10-05 8:55 ` Avi Kivity
2009-10-05 11:18 ` Jan Kiszka
2009-10-05 12:05 ` Avi Kivity
2009-10-05 12:18 ` Jan Kiszka
2009-10-05 12:34 ` Avi Kivity
2009-10-05 12:42 ` Jan Kiszka
2009-10-05 12:55 ` 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=4AC98FBC.3030509@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@web.de \
--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;
as well as URLs for NNTP newsgroup(s).