mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zelin Deng <zelin.deng@linux.alibaba.com>
To: x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Zelin Deng <zelin.deng@linux.alibaba.com>
Subject: [PATCH 1/2] mm/early_ioremap.c: Always build early_memremap_prot() in x86
Date: Thu, 24 Nov 2022 17:12:45 +0800	[thread overview]
Message-ID: <20221124091246.4957-2-zelin.deng@linux.alibaba.com> (raw)
In-Reply-To: <20221124091246.4957-1-zelin.deng@linux.alibaba.com>

In some scenarios, we'd want to specify protection attributes when we
are doing early memory map. As early_memremap_prot() is also defined in
loongarch it's better to select ARCH_USE_MEMREMAP_PROT on X86 config to
avoid redefined error.

Signed-off-by: Zelin Deng <zelin.deng@linux.alibaba.com>
---
 arch/x86/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 48d98a5fe06b..133d7d660b2e 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -97,6 +97,7 @@ config X86
 	select ARCH_HAS_SYNC_CORE_BEFORE_USERMODE
 	select ARCH_HAS_SYSCALL_WRAPPER
 	select ARCH_HAS_UBSAN_SANITIZE_ALL
+	select ARCH_USE_MEMREMAP_PROT
 	select ARCH_HAS_DEBUG_WX
 	select ARCH_HAS_ZONE_DMA_SET if EXPERT
 	select ARCH_HAVE_NMI_SAFE_CMPXCHG
-- 
2.27.0


  reply	other threads:[~2022-11-24  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24  9:12 [PATCH 0/2] Map initrd as encrypted when relocating if SME is enabled Zelin Deng
2022-11-24  9:12 ` Zelin Deng [this message]
2022-11-24  9:12 ` [PATCH 2/2] x86/setup: Preserve _ENC flag when initrd is being relocated Zelin Deng
2022-11-24  9:37   ` Zelin Deng
2022-11-24 14:26 ` [PATCH 0/2] Map initrd as encrypted when relocating if SME is enabled Tom Lendacky
2022-11-24 23:21   ` Zelin Deng

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=20221124091246.4957-2-zelin.deng@linux.alibaba.com \
    --to=zelin.deng@linux.alibaba.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®