From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoffer Dall Subject: [PATCH kvm-unit-tests] scripts: Speedup MAX_SMP check Date: Mon, 3 Sep 2018 12:58:45 +0200 Message-ID: <20180903105845.13942-1-christoffer.dall@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: marc.zyngier@arm.com, kvmarm@lists.cs.columbia.edu To: kvm@vger.kernel.org Return-path: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu List-Id: kvm.vger.kernel.org The current MAX_SMP check launches QEMU for every value of the SMP parameter to check if the SMP parameter based on the native is higher than the QEMU maximum supported configuration. On something like a TX2, which has 224 threads, this takes a very long time where the test script just sits there with no output. Reduce the wait time by taking the log2 of MAX_SMP in each iteration of the loop instead. Signed-off-by: Christoffer Dall --- scripts/runtime.bash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/runtime.bash b/scripts/runtime.bash index a31ae91..1e2c288 100644 --- a/scripts/runtime.bash +++ b/scripts/runtime.bash @@ -140,5 +140,5 @@ function run() # just remove it... while $RUNTIME_arch_run _NO_FILE_4Uhere_ -smp $MAX_SMP \ |& grep -qi 'exceeds max CPUs'; do - ((--MAX_SMP)) + MAX_SMP=$((MAX_SMP >> 1)) done -- 2.7.4