lkml.org 
[lkml]   [2008]   [Oct]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [RFC] CPUID usage for interaction between Hypervisors and Linux.
Alok Kataria wrote:
> Your explanation below answers the question you raised, the problem
> being we need to have support for each of these different hypercall
> mechanisms in the kernel.
> I understand that this was the correct thing to do at that moment.
> But do we want to go the same way again for CPUID when we can make it
> generic (flat enough) for anybody to use it in the same manner and
> expose a generic interface to the kernel.
>

But what sort of information can be stored in cpuid that's actually
useful? Right now we just it in KVM for feature bits. Most of the
stuff that's interesting is stored in shared memory because a guest can
read that without taking a vmexit or via a hypercall.

We can all agree upon a common mechanism for doing something but if no
one is using that mechanism to do anything significant, what purpose
does it serve?

Regards,

Anthony Liguori



\
 
 \ /
  Last update: 2008-10-01 23:33    [W:0.093 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site