linux-kernel - Re: [PATCH 0/3] stop_machine enhancements and simplifications

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: <200807081821.09722.borntraeger@de.ibm.com>
Date:	Tue, 8 Jul 2008 18:21:09 +0200
From:	Christian Borntraeger <borntraeger@...ibm.com>
To:	Rusty Russell <rusty@...tcorp.com.au>
Cc:	linux-kernel@...r.kernel.org, Jason Baron <jbaron@...hat.com>,
	Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
	Max Krasnyansky <maxk@...lcomm.com>
Subject: Re: [PATCH 0/3] stop_machine enhancements and simplifications

Am Dienstag, 8. Juli 2008 schrieb Rusty Russell:
> Hi all,
> 
>    Here are the three stop_machine patches I've queued for the next merge
> window.  The first two are pretty well tested via linux-next, the last is
> recent but fairly straightforward.

Hmm, these patches dont fit on kvm.git so I tested the version from 
linux-next.

When using linux-next in a kvm guest on a linux-next host this patch set 
really improves the situation. On a guest with 64 cpus on a 1 cpu host 
stop_machine_run seems to finish immediately. 

I still have some strange problems with 25 guests * 64 cpus on one host cpu, 
but this requires further analysis.

IMHO this patch set is really an improvement to the earlier version:

Acked-by: Christian Borntraeger <borntraeger@...ibm.com>

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