Received: by 2002:a05:6358:16cd:b0:dc:6189:e246 with SMTP id r13csp1652376rwl; Fri, 4 Nov 2022 17:20:34 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6AIXmNLf/sLuWmuCv7pFpdycNsCOmkyMjACeL6qLbZAVmU6+aol1iQVPIe3uSfGkKLx7c5 X-Received: by 2002:a17:907:94ce:b0:79c:d3c5:e9f6 with SMTP id dn14-20020a17090794ce00b0079cd3c5e9f6mr36526423ejc.219.1667607633945; Fri, 04 Nov 2022 17:20:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1667607633; cv=none; d=google.com; s=arc-20160816; b=EnkJmghMSjiwfgNUFg5N2v/y7Mat+g9acR0hm6AU50maz9QVskanpx857bFoUw2pMB YJOfAHAbofhuh5UDxvPNVHzBcGlp7necRcC+rZRLqc35rI09vofgOkgUm549tOOXHDg4 95K5v6pzdHesFWOdBEDAN7d3db5MmdMo1DLcENEb4H+RVhZ9zC7S11khBR5GtPReE2if 20B78WctLsSi92wJCJB4ZaxsxBGJsR0K/YhskO7lHZZnRCpXhPRBQ7UeiWW2a87j1Ph5 rk+HXrGxjjyJV4kowUqYBdjUZID9fd2JiBvU53/4Km1hmpgSX4+pprfLYLfE2S4i23JO ATPQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:reply-to:dkim-signature; bh=ZnzJmimE900iiRy7VTWPGN9EpNmm/Y1LD4I/QC6tB0Q=; b=zKSshxZAwXtfWU9N4R/HI9mZZ7VpOFyqMc0gLRQzJj3QCRuYE8li9QS8UXQGOxV1rJ JET6Z1JqO4Eqe9GFml5M9cnpmxLKQpQJ3RE8BpYGx43CYDGNOYbqlUqp6AgXZlvg+Tsp 0KxxqK/qVzfygwGbjE8s5SS5LFYQ6i/cDY8WhFcPgEDCT8bSpn1PBM0YSl6DJI1Yui22 1/EvkJiqJDIFaQaELuO7pDQ7YJHTyhsLIASmmROs4O8kgbTXiVSY5G+IMaG/kgbh/CFI 1h0XjYK06WDyUL2tYW8McfubpmeR/5lZe91EKtHxlIkFMH4cQvKtLq4yvrEw7nJQEmEB 4u8Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=SAaScsy5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m17-20020a056402511100b00461b8e2c7f4si1168515edd.548.2022.11.04.17.20.10; Fri, 04 Nov 2022 17:20:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=SAaScsy5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229609AbiKDX64 (ORCPT + 97 others); Fri, 4 Nov 2022 19:58:56 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37998 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229459AbiKDX6z (ORCPT ); Fri, 4 Nov 2022 19:58:55 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3A185419B1 for ; Fri, 4 Nov 2022 16:58:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1667606282; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ZnzJmimE900iiRy7VTWPGN9EpNmm/Y1LD4I/QC6tB0Q=; b=SAaScsy5VY4LkU/F29nQbQkVTdRnZ2Uug7YnY4hJq2aPUYT9avq/N/8zcbi5BuJxdoINE+ zTySlv0elts214yRAh2OsPXZSVHutrTsc3KpBUiIZrmsmztdlcQC8yNvCMXbeklvnvMOXw ps3avhtBNlxNGI9jnwpY37JfuU7+8sg= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-196-T678CyveNP-D_kNb-7hxrA-1; Fri, 04 Nov 2022 19:57:57 -0400 X-MC-Unique: T678CyveNP-D_kNb-7hxrA-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 20CF785A583; Fri, 4 Nov 2022 23:57:46 +0000 (UTC) Received: from [10.64.54.78] (vpn2-54-78.bne.redhat.com [10.64.54.78]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 343EFC16932; Fri, 4 Nov 2022 23:57:26 +0000 (UTC) Reply-To: Gavin Shan Subject: Re: [PATCH v3 0/6] KVM: selftests: memslot_perf_test: aarch64 cleanup/fixes To: "Maciej S. Szmigiero" Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, maz@kernel.org, pbonzini@redhat.com, ajones@ventanamicro.com, kvmarm@lists.linux.dev, shuah@kernel.org, peterx@redhat.com, oliver.upton@linux.dev, seanjc@google.com, ricarkol@google.com, zhenyzha@redhat.com, shan.gavin@gmail.com References: <20221020071209.559062-1-gshan@redhat.com> <91d563b6-5f1c-5ecc-0a40-7d8838770b22@maciej.szmigiero.name> From: Gavin Shan Message-ID: Date: Sat, 5 Nov 2022 07:57:24 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0 MIME-Version: 1.0 In-Reply-To: <91d563b6-5f1c-5ecc-0a40-7d8838770b22@maciej.szmigiero.name> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Spam-Status: No, score=-3.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/25/22 7:18 AM, Maciej S. Szmigiero wrote: > On 20.10.2022 09:12, Gavin Shan wrote: >> kvm/selftests/memslots_perf_test doesn't work with 64KB-page-size-host >> and 4KB-page-size-guest on aarch64. In the implementation, the host and >> guest page size have been hardcoded to 4KB. It's ovbiously not working >> on aarch64 which supports 4KB, 16KB, 64KB individually on host and guest. >> >> This series tries to fix it. After the series is applied, the test runs >> successfully with 64KB-page-size-host and 4KB-page-size-guest. >> >>     # ./memslots_perf_tests -v -s 512 >> >> Since we're here, the code is cleaned up a bit as PATCH[1-3] do. The >> other patches are fixes to handle the mismatched host/guest page >> sized. >> >> v1: https://lore.kernel.org/kvmarm/20221014071914.227134-1-gshan@redhat.com/T/#t >> v2: https://lore.kernel.org/kvmarm/20221018040454.405719-1-gshan@redhat.com/T/#t >> >> Changelog >> ========= >> v3: >>    * Improved comments about MEM_TEST_MOVE_SIZE, which is set >>      to 64KB in PATCH[v3 4/6] and finally fixed to 192KB in >>      PATCH[v3 5/6].                                              (Maciej) >>    * Use size instead of pages to do the comparison in >>      test_memslot_move_prepare()                                 (Maciej) >>    * Use tools/include/linux/sizes.h instead of inventing >>      our own macros.                                             (Oliver) >> v2: >>    * Pick the smaller value between the ones specified by >>      user or probed from KVM_CAP_NR_MEMSLOTS in PATCH[v2 3/6]    (Maciej) >>    * Improved comments about MEM_TEST_MOVE_SIZE in >>      PATCH[v2 4/6]                                               (Maciej) >>    * Avoid mismatched guest page size after VM is started in >>      prepare_vm() in PATCH[v2 4/6]                               (Maciej) >>    * Fix condition to check MEM_TEST_{UNMAP, UNMAP_CHUNK}_SIZE >>      in check_memory_size() in PATCH[v2 4/6]                     (Maciej) >>    * Define base and huge page size in kvm_util_base.h in >>      PATCH[v2 5/6]                                               (Sean) >>    * Add checks on host/guest page size in check_memory_size() >>      and fail early if any of them exceeds 64KB in PATCH[v2 5/6] (Maciej) >> >> >> Gavin Shan (6): >>    KVM: selftests: memslot_perf_test: Use data->nslots in prepare_vm() >>    KVM: selftests: memslot_perf_test: Consolidate loop conditions in >>      prepare_vm() >>    KVM: selftests: memslot_perf_test: Probe memory slots for once >>    KVM: selftests: memslot_perf_test: Support variable guest page size >>    KVM: selftests: memslot_perf_test: Consolidate memory >>    KVM: selftests: memslot_perf_test: Report optimal memory slots >> > > This patch set now looks good to me, so for the whole series: > Reviewed-by: Maciej S. Szmigiero > Thanks for your time on reviews, Maciej. The broken test case was reported in our downstream Linux, which means our downstream linux needs the improvements and fixes to make the test case working. Thanks, Gavin