All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Fernandez <martin.fernandez@eclypsium.com>
To: linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
	platform-driver-x86@vger.kernel.org, linux-mm@kvack.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
	dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
	ardb@kernel.org, dvhart@infradead.org, andy@infradead.org,
	gregkh@linuxfoundation.org, rafael@kernel.org, rppt@kernel.org,
	akpm@linux-foundation.org, daniel.gutson@eclypsium.com,
	hughsient@gmail.com, alex.bazhaniuk@eclypsium.com,
	alison.schofield@intel.com, keescook@chromium.org,
	Martin Fernandez <martin.fernandez@eclypsium.com>
Subject: [PATCH v7 2/8] mm/mmzone: Tag pg_data_t with crypto capabilities
Date: Mon, 25 Apr 2022 14:15:20 -0300	[thread overview]
Message-ID: <20220425171526.44925-3-martin.fernandez@eclypsium.com> (raw)
In-Reply-To: <20220425171526.44925-1-martin.fernandez@eclypsium.com>

Add a new member in the pg_data_t struct to tell whether the node
corresponding to that pg_data_t is able to do hardware memory
encryption.

This will be read from sysfs.

Signed-off-by: Martin Fernandez <martin.fernandez@eclypsium.com>
---
 include/linux/mmzone.h | 3 +++
 mm/page_alloc.c        | 1 +
 2 files changed, 4 insertions(+)

diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
index 46ffab808f03..89054af9e599 100644
--- a/include/linux/mmzone.h
+++ b/include/linux/mmzone.h
@@ -886,6 +886,9 @@ typedef struct pglist_data {
 	struct task_struct *kcompactd;
 	bool proactive_compact_trigger;
 #endif
+
+	bool crypto_capable;
+
 	/*
 	 * This is a per-node reserve of pages that are not available
 	 * to userspace allocations.
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 0e42038382c1..a244151045b4 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -7699,6 +7699,7 @@ static void __init free_area_init_node(int nid)
 	pgdat->node_id = nid;
 	pgdat->node_start_pfn = start_pfn;
 	pgdat->per_cpu_nodestats = NULL;
+	pgdat->crypto_capable = memblock_node_is_crypto_capable(nid);
 
 	if (start_pfn != end_pfn) {
 		pr_info("Initmem setup node %d [mem %#018Lx-%#018Lx]\n", nid,
-- 
2.30.2


  parent reply	other threads:[~2022-04-25 17:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 17:15 [PATCH v7 0/8] x86: Show in sysfs if a memory node is able to do encryption Martin Fernandez
2022-04-25 17:15 ` [PATCH v7 1/8] mm/memblock: Tag memblocks with crypto capabilities Martin Fernandez
2022-04-26  6:10   ` Mike Rapoport
2022-04-26 12:59     ` Martin Fernandez
2022-04-26 13:20       ` Mike Rapoport
2022-04-26 13:25         ` Daniel Gutson
2022-04-25 17:15 ` Martin Fernandez [this message]
2022-04-26  6:16   ` [PATCH v7 2/8] mm/mmzone: Tag pg_data_t " Mike Rapoport
2022-04-25 17:15 ` [PATCH v7 3/8] x86/e820: Add infrastructure to refactor e820__range_{update,remove} Martin Fernandez
2022-04-25 17:15 ` [PATCH v7 4/8] x86/e820: Refactor __e820__range_update Martin Fernandez
2022-04-25 17:15 ` [PATCH v7 5/8] x86/e820: Refactor e820__range_remove Martin Fernandez
2022-04-26 15:10   ` Dave Hansen
2022-04-26 17:37     ` Martin Fernandez
2022-04-26 17:55       ` Dave Hansen
2022-04-25 17:15 ` [PATCH v7 6/8] x86/e820: Tag e820_entry with crypto capabilities Martin Fernandez
2022-04-25 17:15 ` [PATCH v7 7/8] x86/efi: Mark e820_entries as crypto capable from EFI memmap Martin Fernandez
2022-04-25 17:15 ` [PATCH v7 8/8] drivers/node: Show in sysfs node's crypto capabilities Martin Fernandez
2022-04-26  6:16   ` Mike Rapoport
2022-04-26 13:01     ` Martin Fernandez
2022-04-25 17:23 ` [PATCH v7 0/8] x86: Show in sysfs if a memory node is able to do encryption Andrew Morton

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=20220425171526.44925-3-martin.fernandez@eclypsium.com \
    --to=martin.fernandez@eclypsium.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.bazhaniuk@eclypsium.com \
    --cc=alison.schofield@intel.com \
    --cc=andy@infradead.org \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=daniel.gutson@eclypsium.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dvhart@infradead.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=hughsient@gmail.com \
    --cc=keescook@chromium.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rppt@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.