From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Max Filippov <jcmvbkbc@gmail.com>, linux-xtensa@linux-xtensa.org
Cc: Chris Zankel <chris@zankel.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xtensa: enable ARCH_HAS_DEBUG_VM_PGTABLE
Date: Tue, 26 Apr 2022 11:38:19 +0530 [thread overview]
Message-ID: <63deb092-4002-d798-410e-1db2081f0ef8@arm.com> (raw)
In-Reply-To: <20220425180540.880632-1-jcmvbkbc@gmail.com>
Hi Max,
Thanks for the patch. Just wondering if you ran with different config
options (which might impact test case selection) on/off during testing ?
- Anshuman
On 4/25/22 23:35, Max Filippov wrote:
> xtensa kernels successfully build and run with
> CONFIG_DEBUG_VM_PGTABLE=y, enable arch support for it.
>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> Documentation/features/debug/debug-vm-pgtable/arch-support.txt | 2 +-
> arch/xtensa/Kconfig | 1 +
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/features/debug/debug-vm-pgtable/arch-support.txt b/Documentation/features/debug/debug-vm-pgtable/arch-support.txt
> index 83eafe1a7f68..ff21a83abe62 100644
> --- a/Documentation/features/debug/debug-vm-pgtable/arch-support.txt
> +++ b/Documentation/features/debug/debug-vm-pgtable/arch-support.txt
> @@ -27,5 +27,5 @@
> | sparc: | TODO |
> | um: | TODO |
> | x86: | ok |
> - | xtensa: | TODO |
> + | xtensa: | ok |
> -----------------------
> diff --git a/arch/xtensa/Kconfig b/arch/xtensa/Kconfig
> index 2ed897299f19..903b910ebc10 100644
> --- a/arch/xtensa/Kconfig
> +++ b/arch/xtensa/Kconfig
> @@ -4,6 +4,7 @@ config XTENSA
> select ARCH_32BIT_OFF_T
> select ARCH_HAS_BINFMT_FLAT if !MMU
> select ARCH_HAS_CURRENT_STACK_POINTER
> + select ARCH_HAS_DEBUG_VM_PGTABLE
> select ARCH_HAS_DMA_PREP_COHERENT if MMU
> select ARCH_HAS_SYNC_DMA_FOR_CPU if MMU
> select ARCH_HAS_SYNC_DMA_FOR_DEVICE if MMU
next prev parent reply other threads:[~2022-04-26 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 18:05 Max Filippov
2022-04-26 6:08 ` Anshuman Khandual [this message]
2022-04-26 12:42 ` Max Filippov
2022-04-29 3:33 ` Anshuman Khandual
2022-04-29 4:21 ` Anshuman Khandual
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=63deb092-4002-d798-410e-1db2081f0ef8@arm.com \
--to=anshuman.khandual@arm.com \
--cc=chris@zankel.net \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.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®