linux-kernel - Re: [PATCH 0/4] Split hyperv-tlfs.h into generic and arch specific files

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: <20200421112422.j4ihb4se7i5tddih@debian>
Date:   Tue, 21 Apr 2020 12:24:22 +0100
From:   Wei Liu <wei.liu@...nel.org>
To:     Michael Kelley <mikelley@...rosoft.com>
Cc:     kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
        wei.liu@...nel.org, tglx@...utronix.de, mingo@...hat.com,
        bp@...en8.de, x86@...nel.org, hpa@...or.com, pbonzini@...hat.com,
        sean.j.christopherson@...el.com, vkuznets@...hat.com,
        wanpengli@...cent.com, jmattson@...gle.com, joro@...tes.org,
        kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-hyperv@...r.kernel.org
Subject: Re: [PATCH 0/4] Split hyperv-tlfs.h into generic and arch specific
 files

On Mon, Apr 20, 2020 at 10:38:34AM -0700, Michael Kelley wrote:
> Michael Kelley (4):
>   KVM: x86: hyperv: Remove duplicate definitions of Reference TSC Page
>   x86/hyperv: Remove HV_PROCESSOR_POWER_STATE #defines
>   x86/hyperv: Split hyperv-tlfs.h into arch dependent and independent
>     files
>   asm-generic/hyperv: Add definitions for Get/SetVpRegister hypercalls
> 
>  arch/x86/include/asm/hyperv-tlfs.h | 472 +++--------------------------
>  arch/x86/include/asm/kvm_host.h    |   2 +-
>  arch/x86/kvm/hyperv.c              |   4 +-
>  include/asm-generic/hyperv-tlfs.h  | 470 ++++++++++++++++++++++++++++
>  4 files changed, 509 insertions(+), 439 deletions(-)
>  create mode 100644 include/asm-generic/hyperv-tlfs.h

This series looks good to me.

I will wait for a few days before actually queueing it to hyperv-next so
that other people can have a chance to comment.

Wei.