linux-kernel - Re: [PATCH v4 00/14] KVM: Dirty ring 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 for Android: free password hash cracker in your pocket

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

Message-ID: <20200303173334.GE464129@xz-x1>
Date:   Tue, 3 Mar 2020 12:33:34 -0500
From:   Peter Xu <peterx@...hat.com>
To:     kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     Christophe de Dinechin <dinechin@...hat.com>,
        Sean Christopherson <sean.j.christopherson@...el.com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Jason Wang <jasowang@...hat.com>,
        Yan Zhao <yan.y.zhao@...el.com>,
        "Michael S . Tsirkin" <mst@...hat.com>,
        Kevin Tian <kevin.tian@...el.com>,
        Alex Williamson <alex.williamson@...hat.com>,
        "Dr . David Alan Gilbert" <dgilbert@...hat.com>,
        Vitaly Kuznetsov <vkuznets@...hat.com>
Subject: Re: [PATCH v4 00/14] KVM: Dirty ring interface

On Tue, Feb 04, 2020 at 09:50:51PM -0500, Peter Xu wrote:
> KVM branch:
>   https://github.com/xzpeter/linux/tree/kvm-dirty-ring
> 
> QEMU branch for testing:
>   https://github.com/xzpeter/qemu/tree/kvm-dirty-ring
> 
> v4 changelog:
> 
> - refactor ring layout: remove indices, use bit 0/1 in the gfn.flags
>   field to encode GFN status (invalid, dirtied, collected) [Michael,
>   Paolo]
> - patch memslot_valid_for_gpte() too to check against memslot flags
>   rather than dirty_bitmap pointer
> - fix build on non-x86 arch [syzbot]
> - fix comment for kvm_dirty_gfn [Michael]
> - check against VM_EXEC, VM_SHARED for mmaps [Michael]
> - fix "KVM: X86: Don't track dirty for
>   KVM_SET_[TSS_ADDR|IDENTITY_MAP_ADDR]" to unbreak
>   unrestricted_guest=N [Sean]
> - some rework in the test code, e.g., more comments

Any comments before I repost another version?  Thanks,

-- 
Peter Xu