From: Rebecca Mckeever <remckee0@gmail.com>
To: Mike Rapoport <rppt@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: David Hildenbrand <david@redhat.com>,
Rebecca Mckeever <remckee0@gmail.com>
Subject: [PATCH 3/4] memblock tests: set memblock_debug to enable memblock_dbg() messages
Date: Wed, 22 Jun 2022 01:19:31 -0500 [thread overview]
Message-ID: <fe34452209f54287023ccacd666eade81ecd9a24.1655878337.git.remckee0@gmail.com> (raw)
In-Reply-To: <cover.1655878337.git.remckee0@gmail.com>
If Memblock simulator was compiled with MEMBLOCK_DEBUG=1, set
memblock_debug to 1 so that memblock_dbg() will print debug information
when memblock functions are tested in Memblock simulator.
Signed-off-by: Rebecca Mckeever <remckee0@gmail.com>
---
tools/testing/memblock/internal.h | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/tools/testing/memblock/internal.h b/tools/testing/memblock/internal.h
index 94b52a8718b5..c2a492c05e0c 100644
--- a/tools/testing/memblock/internal.h
+++ b/tools/testing/memblock/internal.h
@@ -2,6 +2,13 @@
#ifndef _MM_INTERNAL_H
#define _MM_INTERNAL_H
+/*
+ * Enable memblock_dbg() messages
+ */
+#ifdef MEMBLOCK_DEBUG
+static int memblock_debug = 1;
+#endif
+
struct page {};
void memblock_free_pages(struct page *page, unsigned long pfn,
--
2.34.1
next prev parent reply other threads:[~2022-06-22 6:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 6:19 [PATCH 0/4] memblock tests: add VERBOSE and MEMBLOCK_DEBUG Makefile options Rebecca Mckeever
2022-06-22 6:19 ` [PATCH 1/4] memblock tests: add user-provided arguments to Makefile Rebecca Mckeever
2022-06-22 8:46 ` David Hildenbrand
2022-06-22 6:19 ` [PATCH 2/4] memblock tests: add verbose output to memblock tests Rebecca Mckeever
2022-06-22 6:19 ` Rebecca Mckeever [this message]
2022-06-22 6:19 ` [PATCH 4/4] memblock tests: remove completed TODO items Rebecca Mckeever
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fe34452209f54287023ccacd666eade81ecd9a24.1655878337.git.remckee0@gmail.com \
--to=remckee0@gmail.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox