On 04/25/2011 08:55 AM, brill...@viatech.com.cn wrote:
> On 04/21/2011 01:06 PM, brill...@viatech.com.cn wrote:
> > So,the conclusion is:
> >
> > Only VIA C7 CPUs have dependency on EFLAGS[30], but they do
> not support VT-X technology, so kvm can not run on it and the issue
> about EFLAG
> On 04/21/2011 01:06 PM, brill...@viatech.com.cn wrote:
> > So,the conclusion is:
> >
> > Only VIA C7 CPUs have dependency on EFLAGS[30], but they do
> not support VT-X technology, so kvm can not run on it and the issue
> about EFLAGS[30] will not occur.
> > VIA Nano CPUs support VT-X technology
On 04/21/2011 01:06 PM, brill...@viatech.com.cn wrote:
So,the conclusion is:
Only VIA C7 CPUs have dependency on EFLAGS[30], but they do not support VT-X
technology, so kvm can not run on it and the issue about EFLAGS[30] will not
occur.
VIA Nano CPUs support VT-X technology and can run kvm, b
Hi, Avi
I'm sorry to reply you a little late.
I spent some time on finding information to fix the EFLAGS[30] issue, and I
have got it now.
Here is some comment from Centaur.:
EFLAGS:30 was used on C7 but not by Nano. EFLAGS:30 is undefined for Intel. C7
used it as a way of improving performa
On 04/14/2011 12:54 PM, brill...@viatech.com.cn wrote:
> On 04/14/2011 06:14 AM, brill...@viatech.com.cn wrote:
> >On 04/13/2011 02:05 PM, brill...@viatech.com.cn wrote:
> > > > >>
> > > > >>+ /* cpuid 0xC001.edx */
> > > > >> + const u32 kvm_supported_word5_x86
> On 04/14/2011 06:14 AM, brill...@viatech.com.cn wrote:
> > On 04/13/2011 02:05 PM, brill...@viatech.com.cn wrote:
> > > > >>
> > > > >> +/* cpuid 0xC001.edx */
> > > > >> + const u32 kvm_supported_word5_x86_features =
> > > > >> +F(XSTORE) | F(XSTORE_EN)
On 04/14/2011 06:14 AM, brill...@viatech.com.cn wrote:
On 04/13/2011 02:05 PM, brill...@viatech.com.cn wrote:
> > >>
> > >> +/* cpuid 0xC001.edx */
> > >> + const u32 kvm_supported_word5_x86_features =
> > >> +F(XSTORE) | F(XSTORE_EN) | F(XCRYPT) | F(XCR
On 04/13/2011 02:05 PM, brill...@viatech.com.cn wrote:
> > >>
> > >> + /* cpuid 0xC001.edx */
> > >> +const u32 kvm_supported_word5_x86_features =
> > >> + F(XSTORE) | F(XSTORE_EN) | F(XCRYPT) | F(XCRYPT_EN) |
> > >> + F(ACE2) | F(ACE2_EN) | F(PHE)
On 04/13/2011 02:05 PM, brill...@viatech.com.cn wrote:
>>
>> + /* cpuid 0xC001.edx */
>> + const u32 kvm_supported_word5_x86_features =
>> + F(XSTORE) | F(XSTORE_EN) | F(XCRYPT) | F(XCRYPT_EN) |
>> + F(ACE2) | F(ACE2_EN) | F(PHE) | F(PHE_EN) |
>> +
On 04/13/2011 06:26 AM, brill...@viatech.com.cn wrote:
>> The CPUIDs for Centaur are added, and then the features of PadLock
>> hardware engine on VIA CPU, such as "ace", "ace_en" and so on, can be
>> passed into the kvm guest.
>>
> Nice to see this. Please post a link to the documentation des
On 04/13/2011 06:26 AM, brill...@viatech.com.cn wrote:
The CPUIDs for Centaur are added, and then the features of PadLock
hardware
engine on VIA CPU, such as "ace", "ace_en" and so on, can be passed into
the
kvm guest.
Nice to see this. Please post a link to the documentation describing
the
The CPUIDs for Centaur are added, and then the features of PadLock
hardware
engine on VIA CPU, such as "ace", "ace_en" and so on, can be passed into
the
kvm guest.
Signed-off-by: BrillyWu
Signed-off-by: KaryJin
---
arch/x86/kvm/x86.c | 31 +++
1 file changed, 31 in
12 matches
Mail list logo