linux-kernel - Re: [PATCH 16/22] KVM: MMU: Track page fault data in struct vcpu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BDFE6C2.2040601@redhat.com>
Date:	Tue, 04 May 2010 12:20:02 +0300
From:	Avi Kivity <avi@...hat.com>
To:	"Roedel, Joerg" <Joerg.Roedel@....com>
CC:	Marcelo Tosatti <mtosatti@...hat.com>,
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 16/22] KVM: MMU: Track page fault data in struct vcpu

On 05/04/2010 12:11 PM, Roedel, Joerg wrote:
> On Tue, May 04, 2010 at 03:53:57AM -0400, Avi Kivity wrote:
>    
>> On 05/03/2010 07:32 PM, Joerg Roedel wrote:
>>      
>>> On Tue, Apr 27, 2010 at 03:58:36PM +0300, Avi Kivity wrote:
>>>
>>>        
>>>> So we probably need to upgrade gva_t to a u64.  Please send this as
>>>> a separate patch, and test on i386 hosts.
>>>>
>>>>          
>>> Are there _any_ regular tests of KVM on i386 hosts? For me this is
>>> terribly broken (also after I fixed the issue which gave me a
>>> VMEXIT_INVALID at the first vmrun).
>>>
>>>
>>>        
>> No, apart from the poor users.  I'll try to set something up using nsvm.
>>      
> Ok. I will post an initial fix for the VMEXIT_INVALID bug soon. Apart
> from that I get a lockdep warning when I try to start a guest. The guest
> actually boots if it is single-vcpu. SMP guests don't even boot through
> the BIOS for me.
>
>    

Strange.  i386 vs x86_64 shouldn't have that much effect!

-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/