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] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 7 Jan 2016 15:23:00 +0100
From:	Christian Borntraeger <borntraeger@...ibm.com>
To:	Paolo Bonzini <pbonzini@...hat.com>, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org
Cc:	Takuya Yoshikawa <yoshikawa_takuya_b1@....ntt.co.jp>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: [PATCH 0/4] Reorganize request bits

On 01/07/2016 03:17 PM, Paolo Bonzini wrote:
> There is no need for request bits to differ across architectures.  Only
> a handful of them are architecture-independent, the others can all share
> bits 8-31 with overlap.
> 
> Leaving room for more architecture-independent bits means that actually
> no bits are freed, but the cleanup is useful anyway IMO.
> 
> Paolo Bonzini (4):
>   KVM: Remove unused KVM_REQ_KICK to save a bit in
>   KVM: document which architecture uses each request bit
>   KVM: renumber architecture-dependent requests
>   KVM: move architecture-dependent requests to arch/
> 
>  arch/powerpc/include/asm/kvm_host.h |  4 ++++
>  arch/s390/include/asm/kvm_host.h    |  4 ++++
>  arch/x86/include/asm/kvm_host.h     | 28 ++++++++++++++++++++++++++
>  arch/x86/kvm/x86.c                  | 10 ++++++++++
>  include/linux/kvm_host.h            | 39 +++++--------------------------------
>  virt/kvm/kvm_main.c                 | 10 ----------
>  6 files changed, 51 insertions(+), 44 deletions(-)
> 

For the idea:

Acked-by: Christian Borntraeger <borntraeger@...ibm.com>
but no deep review so far.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ