linux-kernel - Re: [kvm-devel] [PATCH 3/3] KVM

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] [day] [month] [year] [list]

Date:	Wed, 18 Jul 2007 14:25:17 -0500
From:	Anthony Liguori <anthony@...emonkey.ws>
To:	Jeff Dike <jdike@...toit.com>
CC:	Avi Kivity <avi@...ranet.com>,
	KVM devel <kvm-devel@...ts.sourceforge.net>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [kvm-devel] [PATCH 3/3] KVM - add hypercall nr to kvm_run

Jeff Dike wrote:
> On Wed, Jul 18, 2007 at 11:28:18AM -0500, Anthony Liguori wrote:
>   
>> Within the kernel right (VMCALL is only usable in ring 1).  
>>     
>
> Yup.
>
>   
>> Is it 
>> terribly important to be able to pass through the syscall arguments in 
>> registers verses packing them in a data structure and passing a pointer 
>> to that structure?
>>     
>
> An arg block would be fine, too.
>   

Okay, then you should be pretty well insulated against the changing 
hypercall stuff since you only need one hypercall NR and can use a one 
argument hypercall.

Regards,

Anthony Liguori

> 				Jeff
>
>   

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