[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1475224135.5251432.1467976539798.JavaMail.zimbra@redhat.com>
Date: Fri, 8 Jul 2016 07:15:39 -0400 (EDT)
From: Paolo Bonzini <pbonzini@...hat.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Eduardo Habkost <ehabkost@...hat.com>,
linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
stable@...r.kernel.org, Yazen Ghannam <yazen.ghannam@....com>,
Brijesh Singh <brijesh.singh@....com>
Subject: Re: [PATCH] KVM: SVM: fix trashing of MSR_TSC_AUX
> Ok, I'll go through the features and see what kind of state the kernel
> programs in there and add them to a VMStateDescription thing. Hohumm,
> makes sense to me.
It does sometimes happen that there is no state. For example it could be
an MSR that we are already getting in and out of KVM. However, it is way
more common that you have to add support for reading/writing the MSR in
KVM as well, and then teach QEMU's target-i386/kvm.c about it as well.
It's hard to say without knowing exactly what the feature is about...
Is there an architecture manual out there that documents it?
Paolo
Powered by blists - more mailing lists