linux-kernel - Re: [PATCH] expose async pf through our standard mechanism

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]

Message-ID: <4D8B1FC2.8050305@redhat.com>
Date:	Thu, 24 Mar 2011 12:41:06 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Glauber Costa <glommer@...hat.com>
CC:	kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
	Gleb Natapov <gleb@...hat.com>
Subject: Re: [PATCH] expose async pf through our standard mechanism

On 03/23/2011 06:40 PM, Glauber Costa wrote:
> As Avi recently mentioned, the new standard mechanism for exposing features
> is KVM_GET_SUPPORTED_CPUID, not spanning CAPs. For some reason async pf missed that.
>
> So expose async_pf here.
>

Applied, thanks.

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