linux-kernel - Re: [kvm-devel] [RFC] Stable kvm userspace interface

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: <200701110826.28535.arnd@arndb.de>
Date:	Thu, 11 Jan 2007 08:26:28 +0100
From:	Arnd Bergmann <arnd@...db.de>
To:	kvm-devel@...ts.sourceforge.net
Cc:	Avi Kivity <avi@...ranet.com>, Andrew Morton <akpm@...l.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Jeff Garzik <jeff@...zik.org>
Subject: Re: [kvm-devel] [RFC] Stable kvm userspace interface

On Tuesday 09 January 2007 14:37, Avi Kivity wrote:
> struct kvm_vcpu_area {
>     u32 vcpu_area_size;
>     u32 exit_reason;
> 
>     sigset_t sigmask;  // for use during vcpu execution

Since Jeff brought up the point of 32 bit compatibility:
When this structure is shared between 64 bit kernel and
32 bit user space, you sigmask should be a __u64 in order
to guarantee compatibility.

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