linux-kernel - Re: [kvm-devel] [PATCH 0/15] KVM userspace interface updates

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 for Android: free password hash cracker in your pocket

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

Message-ID: <45FD152E.6020207@qumranet.com>
Date:	Sun, 18 Mar 2007 12:32:14 +0200
From:	Avi Kivity <avi@...ranet.com>
To:	Heiko Carstens <heiko.carstens@...ibm.com>
CC:	kvm-devel@...ts.sourceforge.net, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [kvm-devel] [PATCH 0/15] KVM userspace interface updates

Heiko Carstens wrote:
> On Sun, Mar 18, 2007 at 07:20:57AM +0200, Avi Kivity wrote:
>   
>> Heiko Carstens wrote:
>>     
>>> On Sun, Mar 11, 2007 at 03:53:12PM +0200, Avi Kivity wrote:
>>>  
>>>       
>>>> This patchset updates the kvm userspace interface to what I hope will
>>>> be the long-term stable interface.  Provisions are included for extending
>>>> the interface later.  The patches address performance and cleanliness
>>>> concerns.
>>>>         
>>> [...]
>>> But the general question is: do you still plan to switch to a syscall
>>> interface?
>>>       
>> I don't have any present plans for that.  Maybe when the interface starts
>> to evolve at a slower pace, or if it is shown to be significantly faster.
>>
>> Not that interface stabilization here doesn't mean a freeze; it means that
>> backwards compatibility starts when this gets merged.
>>     
>
> If the interface is considered to be stable you can get rid of the
> KVM_GET_API_VERSION ioctl, since the version can't change anymore, right?
>   

It's needed in case pre-stabilization userspace tries to use the 
stabilized interface.  It's true the version won't change.

But maybe we can get rid of it, and the old userspace will just fail on 
the ioctl (we need to keep it reserved for that).

-- 
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/