From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CF50BC433DB for ; Sat, 16 Jan 2021 00:11:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9397E23A5E for ; Sat, 16 Jan 2021 00:11:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729046AbhAPALY (ORCPT ); Fri, 15 Jan 2021 19:11:24 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48602 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726367AbhAPALX (ORCPT ); Fri, 15 Jan 2021 19:11:23 -0500 Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2E403C061757 for ; Fri, 15 Jan 2021 16:10:43 -0800 (PST) Received: by mail-pl1-x62e.google.com with SMTP id x18so5530560pln.6 for ; Fri, 15 Jan 2021 16:10:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=Bie5cw6IgM1/wPZEPjLzAx0dXtWLAo5L5+QElnLZ0lw=; b=JfcClhi8ThEbUx1xc/HweHvfS3oYjLxZglAOXkbN7XcScAUlZuDr2zU2+kD+vAp3/P 3smdJHqUkHCBuuwZ7pHK20OTvgE40/xcI+Ti4kpzD8Wzb2ozimVi06xdFbU3erOGivDF MhuhsGC/a0f17cfDoXYVX3knC12e/7ZQylY/b4/tC5o9NdcA6FlMZwtdSxCi+u8n7xO5 cXP6ium5H5iHbmssgy46DfEZKNubp6qlIV+O32p2jbZL4hCN6XBQbt0YtJl+uCrdlu7U UT6qGc8JOZuuYr0IBIs2+6dAcJa8ZA+cKaWnq8CWfErWLJLNMqwpN3ivxtEs7lO8LmZl N/9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=Bie5cw6IgM1/wPZEPjLzAx0dXtWLAo5L5+QElnLZ0lw=; b=cdGgghc+NkbyVoSLcjGKM4Oy7OW5as05UBhHASmXJGznEu4AMuZqg+H35Xdlpeh167 H3AeNmYLCo332aNn06yPrEPs/Ug7hg3YpPEaIQMLqKY8i93hoPqggSDK26unEVAw0yNx ULAcTMpWBf1umiky+FcWQLyZoGsrujWZB00PyMmclRF+s/nEM1tYXjjZc8cTY6V/3ld9 YZfgL6f10l5KIsQ8NvpDUAUt36o5JH3vpnrY3hTcXpkyql5jD29ZoJoCUFDN7KnGQ3aq 9KVFwT8sYf5hyGJkKTSnoO1+sJjUo+C9yzC3VzLCjPbuQKcgzAjoYW7MwMbSjpVnMDOe wW5Q== X-Gm-Message-State: AOAM533/ZOgQWVph5usrm7ZWFtextdBe7jpfVQNl+TMA/mK4YWonP8eY qvFOqJ5Yp3lEApjZ8eqVi3A8kw== X-Google-Smtp-Source: ABdhPJzCO7p96Akm/DHojJzNSqrjomr1S9QiWXoQxgHDqKHRdHhi0EUQ8a3kodg1g7reFX41E2Lkhg== X-Received: by 2002:a17:90a:c8d:: with SMTP id v13mr13334657pja.75.1610755842662; Fri, 15 Jan 2021 16:10:42 -0800 (PST) Received: from google.com ([2620:15c:f:10:1ea0:b8ff:fe73:50f5]) by smtp.gmail.com with ESMTPSA id l11sm9465799pgt.79.2021.01.15.16.10.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 15 Jan 2021 16:10:41 -0800 (PST) Date: Fri, 15 Jan 2021 16:10:35 -0800 From: Sean Christopherson To: Ben Gardon Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, linux-kselftest@vger.kernel.org, Paolo Bonzini , Peter Xu , Andrew Jones , Peter Shier , Sean Christopherson , Thomas Huth , Jacob Xu , Makarand Sonare Subject: Re: [PATCH 6/6] KVM: selftests: Add memslot modification stress test Message-ID: References: <20210112214253.463999-1-bgardon@google.com> <20210112214253.463999-7-bgardon@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210112214253.463999-7-bgardon@google.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 12, 2021, Ben Gardon wrote: > Add a memslot modification stress test in which a memslot is repeatedly > created and removed while vCPUs access memory in another memslot. Most > userspaces do not create or remove memslots on running VMs which makes > it hard to test races in adding and removing memslots without a > dedicated test. Adding and removing a memslot also has the effect of > tearing down the entire paging structure, which leads to more page > faults and pressure on the page fault handling path than a one-and-done > memory population test. Would it make sense to integrate this with set_memory_region_test? At a high level, they are doing very similar things. Not sure how much code can be shared, but I assume there's some amount of overlap.