Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp2023018rwb; Sun, 18 Sep 2022 20:23:41 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4ruA8TIge2ra1K+j1p7kDUAInMitRju/Qw/RNxglAs3I/Xl6pHqrmwAMYPP/DSUW+14Kvp X-Received: by 2002:a17:907:7b95:b0:72f:9c64:4061 with SMTP id ne21-20020a1709077b9500b0072f9c644061mr11383967ejc.351.1663557821155; Sun, 18 Sep 2022 20:23:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1663557821; cv=none; d=google.com; s=arc-20160816; b=ypFcWFaJdG9R2lrpjN7jU2iKWg6WRdsntTpVJ6K2iAAybB7qKTyWxlbMzBO5aIyBMW o6EW+TMacBteeo+/gSkUWuOSR5Knm9i8JwTfA0U2tXHJ0KTakbsmn+3gobA/uUX6qptV /NI1H7cSWK2ntnxLfZ0iFNFRMjKStTFI/5wlMSQG3pnMKLA4hr7JS3XDxRG3dcp4y5wy u3Bq2JKwzxf25207yMPLjFqwft8zZL9GKhsa2WcyO3bYpXfFuaCiXhdzQZsJ04QDE2mt G6S/84kDRh/PlU586SgtBsKjsE9Gw4ToxriEu30xiGjqih455pEZmcrwmxUQP3urM+rp LHdg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=dUt3tJb2OYIfAxz7jv8jQWHh7b94TyYbQK8fuSEm1q8=; b=YJG2lspFO1rl5Vl0cVAeLazwsEbFareW8WtVT1NtJubGbokWH4gARuE2/2t62sevM1 raXUVSnx/6GZFAYds1KgQMrAon2L6EfB+8cd6Bc7nmPgzNx5SUZ4Pb4/i+t/kfA2amwY px5FDWirCzgZnWEDYPKWkp5hOIkTOKQTxasFPgKgDDJVflcAwca2x2zaunY5WdY9+QCT EnJgTkk+amu4oV6swF71Xq/pCE8VqSjbzmjHUfYQQM3T01u3+R+fqNL+DnWCaiASLOIc Lkpvx86zpwu8otxrekXOYQO05vsQuXBIhgXbqHOlDINlmPe581LDOeiHVNWPi0zzjVUu LOyA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=D6g8+W5w; 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=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bb4-20020a1709070a0400b007317274bb0dsi19790371ejc.979.2022.09.18.20.23.15; Sun, 18 Sep 2022 20:23:41 -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=@intel.com header.s=Intel header.b=D6g8+W5w; 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229803AbiISCtd (ORCPT + 99 others); Sun, 18 Sep 2022 22:49:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39628 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229772AbiISCtT (ORCPT ); Sun, 18 Sep 2022 22:49:19 -0400 Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 24F49193D0 for ; Sun, 18 Sep 2022 19:49:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1663555758; x=1695091758; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=OlGIODpv04YEUz28eV6/esNGVmMut18UL3VgBHg/Gxc=; b=D6g8+W5wd1wVbcS9mToArszsReSzjWUoan7IohO3KU/1Le7YOWi2FZJy 6C0ZIoN947nWWWsMReVxduRlZlkl7gR8MWGNiA6JTVRiqZIbC+a8vnin3 2biBjly6MGoC1IrxDzqXMauYJ6lnqrmbP7HaHcbR4ezYqKFAE17Km0Eyp 0eNsKkFNQP/HnBXv9N7sVJIi1CuBMBZGqGntuP+y/9n3wA62HxDjxp3hV 7/0THMKgd6CSPK4m8Tqlysn7V5A/W/2RaJX8cnGiryVpBvKGd3gbmYnzD LaQFk0GKG92FeUcdxNJ7Cs57kGxCXDmHYevlBm5PlllwNcpVAQLU3vjP0 g==; X-IronPort-AV: E=McAfee;i="6500,9779,10474"; a="298019467" X-IronPort-AV: E=Sophos;i="5.93,325,1654585200"; d="scan'208";a="298019467" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Sep 2022 19:49:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.93,325,1654585200"; d="scan'208";a="947035190" Received: from q.bj.intel.com ([10.238.154.102]) by fmsmga005.fm.intel.com with ESMTP; 18 Sep 2022 19:49:15 -0700 From: shaoqin.huang@intel.com To: rppt@kernel.org Cc: Shaoqin Huang , Rebecca Mckeever , Karolina Drobnik , David Hildenbrand , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: [PATCH v4 2/3] memblock test: Add test to memblock_reserve() 129th region Date: Mon, 19 Sep 2022 10:47:38 +0800 Message-Id: <20220919024745.153395-3-shaoqin.huang@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20220919024745.153395-1-shaoqin.huang@intel.com> References: <20220919024745.153395-1-shaoqin.huang@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE autolearn=ham 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 From: Shaoqin Huang Reserve 129th region in the memblock, and this will trigger the memblock_double_array() function, this needs valid memory regions. So using dummy_physical_memory_init() to allocate a valid memory region. At the same time, reserve 128 faked memory region, and make sure these reserved region not intersect with the valid memory region. So memblock_double_array() will choose the valid memory region, and it will success. Also need to restore the reserved.regions after memblock_double_array(), to make sure the subsequent tests can run as normal. Signed-off-by: Shaoqin Huang --- tools/testing/memblock/tests/basic_api.c | 91 ++++++++++++++++++++++++ 1 file changed, 91 insertions(+) diff --git a/tools/testing/memblock/tests/basic_api.c b/tools/testing/memblock/tests/basic_api.c index 4d61a4b474be..c07a1ab0f19b 100644 --- a/tools/testing/memblock/tests/basic_api.c +++ b/tools/testing/memblock/tests/basic_api.c @@ -892,6 +892,96 @@ static int memblock_reserve_near_max_check(void) return 0; } +/* + * A test that trying to reserve the 129th memory block. + * Expect to trigger memblock_double_array() to double the + * memblock.memory.max, find a new valid memory as + * reserved.regions. + */ +static int memblock_reserve_many_check(void) +{ + int i; + void *orig_region; + struct region r = { + .base = SZ_16K, + .size = SZ_16K, + }; + phys_addr_t memory_base = SZ_128K; + phys_addr_t new_reserved_regions_size; + + PREFIX_PUSH(); + + reset_memblock_regions(); + memblock_allow_resize(); + + /* Add a valid memory region used by double_array(). */ + dummy_physical_memory_init(); + memblock_add(dummy_physical_memory_base(), MEM_SIZE); + + for (i = 0; i < INIT_MEMBLOCK_REGIONS; i++) { + /* Reserve some fakes memory region to fulfill the memblock. */ + memblock_reserve(memory_base, MEM_SIZE); + + ASSERT_EQ(memblock.reserved.cnt, i + 1); + ASSERT_EQ(memblock.reserved.total_size, (i + 1) * MEM_SIZE); + + /* Keep the gap so these memory region will not be merged. */ + memory_base += MEM_SIZE * 2; + } + + orig_region = memblock.reserved.regions; + + /* This reserve the 129 memory_region, and makes it double array. */ + memblock_reserve(memory_base, MEM_SIZE); + + /* + * This is the memory region size used by the doubled reserved.regions, + * and it has been reserved due to it has been used. The size is used to + * calculate the total_size that the memblock.reserved have now. + */ + new_reserved_regions_size = PAGE_ALIGN((INIT_MEMBLOCK_REGIONS * 2) * + sizeof(struct memblock_region)); + /* + * The double_array() will find a free memory region as the new + * reserved.regions, and the used memory region will be reserved, so + * there will be one more region exist in the reserved memblock. And the + * one more reserved region's size is new_reserved_regions_size. + */ + ASSERT_EQ(memblock.reserved.cnt, INIT_MEMBLOCK_REGIONS + 2); + ASSERT_EQ(memblock.reserved.total_size, (INIT_MEMBLOCK_REGIONS + 1) * MEM_SIZE + + new_reserved_regions_size); + ASSERT_EQ(memblock.reserved.max, INIT_MEMBLOCK_REGIONS * 2); + + /* + * Now memblock_double_array() works fine. Let's check after the + * double_array(), the memblock_reserve() still works as normal. + */ + memblock_reserve(r.base, r.size); + ASSERT_EQ(memblock.reserved.regions[0].base, r.base); + ASSERT_EQ(memblock.reserved.regions[0].size, r.size); + + ASSERT_EQ(memblock.reserved.cnt, INIT_MEMBLOCK_REGIONS + 3); + ASSERT_EQ(memblock.reserved.total_size, (INIT_MEMBLOCK_REGIONS + 1) * MEM_SIZE + + new_reserved_regions_size + + r.size); + ASSERT_EQ(memblock.reserved.max, INIT_MEMBLOCK_REGIONS * 2); + + dummy_physical_memory_cleanup(); + + /* + * The current reserved.regions is occupying a range of memory that + * allocated from dummy_physical_memory_init(). After free the memory, + * we must not use it. So restore the origin memory region to make sure + * the tests can run as normal and not affected by the double array. + */ + memblock.reserved.regions = orig_region; + memblock.reserved.cnt = INIT_MEMBLOCK_REGIONS; + + test_pass_pop(); + + return 0; +} + static int memblock_reserve_checks(void) { prefix_reset(); @@ -906,6 +996,7 @@ static int memblock_reserve_checks(void) memblock_reserve_twice_check(); memblock_reserve_between_check(); memblock_reserve_near_max_check(); + memblock_reserve_many_check(); prefix_pop(); -- 2.34.1