arm64: mm: use ARCH_HAS_DEBUG_WX instead of arch defined

	select ACPI_MCFG if (ACPI && PCI)

	select ACPI_SPCR_TABLE if ACPI

	select ACPI_PPTT if ACPI

	select ARCH_HAS_DEBUG_WX

	select ARCH_BINFMT_ELF_STATE

	select ARCH_HAS_DEBUG_VIRTUAL

	select ARCH_HAS_DEVMEM_IS_ALLOWED

	  of TEXT_OFFSET and platforms must not require a specific

	  value.

config DEBUG_WX

	bool "Warn on W+X mappings at boot"

	select PTDUMP_CORE

	---help---

	  Generate a warning if any W+X mappings are found at boot.

	  This is useful for discovering cases where the kernel is leaving

	  W+X mappings after applying NX, as such mappings are a security risk.

	  This check also includes UXN, which should be set on all kernel

	  mappings.

	  Look for a message in dmesg output like this:

	    arm64/mm: Checked W+X mappings: passed, no W+X pages found.

	  or like this, if the check failed:

	    arm64/mm: Checked W+X mappings: FAILED, <N> W+X pages found.

	  Note that even if the check fails, your kernel is possibly

	  still fine, as W+X mappings are not a security hole in

	  themselves, what they do is that they make the exploitation

	  of other unfixed kernel bugs easier.

	  There is no runtime or memory usage effect of this option

	  once the kernel has booted up - it's a one time check.

	  If in doubt, say "Y".

config DEBUG_EFI

	depends on EFI && DEBUG_INFO

	bool "UEFI debugging"