public inbox for linux-riscv@lists.infradead.org
 help / color / mirror / Atom feed
From: Eric DeVolder <eric.devolder@oracle.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
	"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"will@kernel.org" <will@kernel.org>,
	"chenhuacai@kernel.org" <chenhuacai@kernel.org>,
	"geert@linux-m68k.org" <geert@linux-m68k.org>,
	"tsbogend@alpha.franken.de" <tsbogend@alpha.franken.de>,
	"James.Bottomley@HansenPartnership.com"
	<James.Bottomley@HansenPartnership.com>,
	"deller@gmx.de" <deller@gmx.de>,
	"ysato@users.sourceforge.jp" <ysato@users.sourceforge.jp>,
	"dalias@libc.org" <dalias@libc.org>,
	"glaubitz@physik.fu-berlin.de" <glaubitz@physik.fu-berlin.de>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"mingo@redhat.com" <mingo@redhat.com>,
	"bp@alien8.de" <bp@alien8.de>,
	"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"loongarch@lists.linux.dev" <loongarch@lists.linux.dev>,
	"linux-m68k@lists.linux-m68k.org"
	<linux-m68k@lists.linux-m68k.org>,
	"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>,
	"linux-parisc@vger.kernel.org" <linux-parisc@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>
Cc: "kernel@xen0n.name" <kernel@xen0n.name>,
	"mpe@ellerman.id.au" <mpe@ellerman.id.au>,
	"npiggin@gmail.com" <npiggin@gmail.com>,
	"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
	"palmer@dabbelt.com" <palmer@dabbelt.com>,
	"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
	"hca@linux.ibm.com" <hca@linux.ibm.com>,
	"gor@linux.ibm.com" <gor@linux.ibm.com>,
	"agordeev@linux.ibm.com" <agordeev@linux.ibm.com>,
	"borntraeger@linux.ibm.com" <borntraeger@linux.ibm.com>,
	"svens@linux.ibm.com" <svens@linux.ibm.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"keescook@chromium.org" <keescook@chromium.org>,
	"paulmck@kernel.org" <paulmck@kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"frederic@kernel.org" <frederic@kernel.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"ardb@kernel.org" <ardb@kernel.org>,
	"samitolvanen@google.com" <samitolvanen@google.com>,
	"juerg.haefliger@canonical.com" <juerg.haefliger@canonical.com>,
	"arnd@arndb.de" <arnd@arndb.de>,
	"rmk+kernel@armlinux.org.uk" <rmk+kernel@armlinux.org.uk>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"sebastian.reichel@collabora.com"
	<sebastian.reichel@collabora.com>,
	"rppt@kernel.org" <rppt@kernel.org>,
	"kirill.shutemov@linux.intel.com"
	<kirill.shutemov@linux.intel.com>,
	"anshuman.khandual@arm.com" <anshuman.khandual@arm.com>,
	"ziy@nvidia.com" <ziy@nvidia.com>,
	"masahiroy@kernel.org" <masahiroy@kernel.org>,
	"ndesaulniers@google.com" <ndesaulniers@google.com>,
	"mhiramat@kernel.org" <mhiramat@kernel.org>,
	"ojeda@kernel.org" <ojeda@kernel.org>,
	"thunder.leizhen@huawei.com" <thunder.leizhen@huawei.com>,
	"xin3.li@intel.com" <xin3.li@intel.com>,
	"tj@kernel.org" <tj@kernel.org>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"tsi@tuyoix.net" <tsi@tuyoix.net>,
	"bhe@redhat.com" <bhe@redhat.com>,
	"hbathini@linux.ibm.com" <hbathini@linux.ibm.com>,
	"sourabhjain@linux.ibm.com" <sourabhjain@linux.ibm.com>,
	"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
	"konrad.wilk@oracle.com" <konrad.wilk@oracle.com>
Subject: Re: [PATCH v5 02/13] x86/kexec: refactor for kernel/Kconfig.kexec
Date: Fri, 7 Jul 2023 07:16:23 -0500	[thread overview]
Message-ID: <c7e2b428-eb61-50c3-dd44-2d3fbe39301d@oracle.com> (raw)
In-Reply-To: <0d1097dd-f0cb-8518-cf88-e6afbd2a6a19@csgroup.eu>



On 7/7/23 00:58, Christophe Leroy wrote:
> 
> 
> Le 07/07/2023 à 00:20, Eric DeVolder a écrit :
>> The kexec and crash kernel options are provided in the common
>> kernel/Kconfig.kexec. Utilize the common options and provide
>> the ARCH_SUPPORTS_ and ARCH_SELECTS_ entries to recreate the
>> equivalent set of KEXEC and CRASH options.
> 
> 
> Why do you need to duplicate the ARCH_SELECTS_ entries in each
> architecture ?
> 
> Why not define them in arch/Kconfig then select if from each architecture ?
> 
> For instance here for x86 for ARCH_SELECTS_KEXEC_FILE all you'll have to
> do is:
> 	select ARCH_SELECTS_KEXEC_FILE if KEXEC_FILE
> 	select HAVE_IMA_KEXEC if IMA && KEXEC_FILE
> 
> 
> Christophe

Hi Christophe, thanks for looking at this!
The ARCH_SELECTS_ is where the "customization" is performed for that option. The customization is 
putting in place the differences that the arch had from the common option.

For example, with ARCH_SELECTS_KEXEC_FILE, here are all the uses:

x86:
     select HAVE_IMA_KEXEC if IMA

arm64:
     select HAVE_IMA_KEXEC if IMA

powerpc:
     select KEXEC_ELF
     select HAVE_IMA_KEXEC if IMA

riscv:
     select HAVE_IMA_KEXEC if IMA
     select KEXEC_ELF

And there are archs (parisc, riscv, s390) that support KEXEC_FILE that do not need 
ARCH_SELECTS_KEXEC_FILE.

So there isn't a clear path for optimizing the IMA statement, in this example, that I'm aware of.

But perhaps I don't quite understand the technique you are suggesting, either...

eric



> 
>>
>> Signed-off-by: Eric DeVolder <eric.devolder@oracle.com>
>> ---
>>    arch/x86/Kconfig | 92 ++++++++++--------------------------------------
>>    1 file changed, 19 insertions(+), 73 deletions(-)
>>
>> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
>> index 7422db409770..9767a343f7c2 100644
>> --- a/arch/x86/Kconfig
>> +++ b/arch/x86/Kconfig
>> @@ -2040,88 +2040,34 @@ config EFI_RUNTIME_MAP
>>    
>>    source "kernel/Kconfig.hz"
>>    
>> -config KEXEC
>> -	bool "kexec system call"
>> -	select KEXEC_CORE
>> -	help
>> -	  kexec is a system call that implements the ability to shutdown your
>> -	  current kernel, and to start another kernel.  It is like a reboot
>> -	  but it is independent of the system firmware.   And like a reboot
>> -	  you can start any kernel with it, not just Linux.
>> -
>> -	  The name comes from the similarity to the exec system call.
>> -
>> -	  It is an ongoing process to be certain the hardware in a machine
>> -	  is properly shutdown, so do not be surprised if this code does not
>> -	  initially work for you.  As of this writing the exact hardware
>> -	  interface is strongly in flux, so no good recommendation can be
>> -	  made.
>> -
>> -config KEXEC_FILE
>> -	bool "kexec file based system call"
>> -	select KEXEC_CORE
>> -	select HAVE_IMA_KEXEC if IMA
>> -	depends on X86_64
>> -	depends on CRYPTO=y
>> -	depends on CRYPTO_SHA256=y
>> -	help
>> -	  This is new version of kexec system call. This system call is
>> -	  file based and takes file descriptors as system call argument
>> -	  for kernel and initramfs as opposed to list of segments as
>> -	  accepted by previous system call.
>> +config ARCH_SUPPORTS_KEXEC
>> +	def_bool y
>>    
>> -config ARCH_HAS_KEXEC_PURGATORY
>> -	def_bool KEXEC_FILE
>> +config ARCH_SUPPORTS_KEXEC_FILE
>> +	def_bool X86_64 && CRYPTO && CRYPTO_SHA256
>>    
>> -config KEXEC_SIG
>> -	bool "Verify kernel signature during kexec_file_load() syscall"
>> +config ARCH_SELECTS_KEXEC_FILE
>> +	def_bool y
>>    	depends on KEXEC_FILE
>> -	help
>> +	select HAVE_IMA_KEXEC if IMA
>>    
>> -	  This option makes the kexec_file_load() syscall check for a valid
>> -	  signature of the kernel image.  The image can still be loaded without
>> -	  a valid signature unless you also enable KEXEC_SIG_FORCE, though if
>> -	  there's a signature that we can check, then it must be valid.
>> +config ARCH_HAS_KEXEC_PURGATORY
>> +	def_bool KEXEC_FILE
>>    
>> -	  In addition to this option, you need to enable signature
>> -	  verification for the corresponding kernel image type being
>> -	  loaded in order for this to work.
>> +config ARCH_SUPPORTS_KEXEC_SIG
>> +	def_bool y
>>    
>> -config KEXEC_SIG_FORCE
>> -	bool "Require a valid signature in kexec_file_load() syscall"
>> -	depends on KEXEC_SIG
>> -	help
>> -	  This option makes kernel signature verification mandatory for
>> -	  the kexec_file_load() syscall.
>> +config ARCH_SUPPORTS_KEXEC_SIG_FORCE
>> +	def_bool y
>>    
>> -config KEXEC_BZIMAGE_VERIFY_SIG
>> -	bool "Enable bzImage signature verification support"
>> -	depends on KEXEC_SIG
>> -	depends on SIGNED_PE_FILE_VERIFICATION
>> -	select SYSTEM_TRUSTED_KEYRING
>> -	help
>> -	  Enable bzImage signature verification support.
>> +config ARCH_SUPPORTS_KEXEC_BZIMAGE_VERIFY_SIG
>> +	def_bool y
>>    
>> -config CRASH_DUMP
>> -	bool "kernel crash dumps"
>> -	depends on X86_64 || (X86_32 && HIGHMEM)
>> -	help
>> -	  Generate crash dump after being started by kexec.
>> -	  This should be normally only set in special crash dump kernels
>> -	  which are loaded in the main kernel with kexec-tools into
>> -	  a specially reserved region and then later executed after
>> -	  a crash by kdump/kexec. The crash dump kernel must be compiled
>> -	  to a memory address not used by the main kernel or BIOS using
>> -	  PHYSICAL_START, or it must be built as a relocatable image
>> -	  (CONFIG_RELOCATABLE=y).
>> -	  For more details see Documentation/admin-guide/kdump/kdump.rst
>> +config ARCH_SUPPORTS_KEXEC_JUMP
>> +	def_bool y
>>    
>> -config KEXEC_JUMP
>> -	bool "kexec jump"
>> -	depends on KEXEC && HIBERNATION
>> -	help
>> -	  Jump between original kernel and kexeced kernel and invoke
>> -	  code in physical address mode via KEXEC
>> +config ARCH_SUPPORTS_CRASH_DUMP
>> +	def_bool X86_64 || (X86_32 && HIGHMEM)
>>    
>>    config PHYSICAL_START
>>    	hex "Physical address where the kernel is loaded" if (EXPERT || CRASH_DUMP)

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-07-07 12:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06 22:20 [PATCH v5 00/13] refactor Kconfig to consolidate KEXEC and CRASH options Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 01/13] kexec: consolidate kexec and crash options into kernel/Kconfig.kexec Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 02/13] x86/kexec: refactor for kernel/Kconfig.kexec Eric DeVolder
2023-07-07  5:58   ` Christophe Leroy
2023-07-07 12:16     ` Eric DeVolder [this message]
2023-07-06 22:20 ` [PATCH v5 03/13] arm/kexec: " Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 04/13] ia64/kexec: " Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 05/13] arm64/kexec: " Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 06/13] loongarch/kexec: " Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 07/13] m68k/kexec: " Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 08/13] mips/kexec: " Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 09/13] parisc/kexec: " Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 10/13] powerpc/kexec: " Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 11/13] riscv/kexec: " Eric DeVolder
2023-07-06 22:32   ` Palmer Dabbelt
2023-07-07 13:03     ` Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 12/13] s390/kexec: " Eric DeVolder
2023-07-06 22:20 ` [PATCH v5 13/13] sh/kexec: " Eric DeVolder

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=c7e2b428-eb61-50c3-dd44-2d3fbe39301d@oracle.com \
    --to=eric.devolder@oracle.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bhe@redhat.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=chenhuacai@kernel.org \
    --cc=christophe.leroy@csgroup.eu \
    --cc=dalias@libc.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=deller@gmx.de \
    --cc=frederic@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=gor@linux.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hbathini@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hpa@zytor.com \
    --cc=juerg.haefliger@canonical.com \
    --cc=keescook@chromium.org \
    --cc=kernel@xen0n.name \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=loongarch@lists.linux.dev \
    --cc=masahiroy@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=ndesaulniers@google.com \
    --cc=npiggin@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=rppt@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=sebastian.reichel@collabora.com \
    --cc=sourabhjain@linux.ibm.com \
    --cc=svens@linux.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=thunder.leizhen@huawei.com \
    --cc=tj@kernel.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=tsi@tuyoix.net \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=xin3.li@intel.com \
    --cc=ysato@users.sourceforge.jp \
    --cc=ziy@nvidia.com \
    /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