From: "Björn Töpel" <bjorn@kernel.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: "Shuah Khan" <shuah@kernel.org>,
linux-kselftest@vger.kernel.org,
"Björn Töpel" <bjorn@rivosinc.com>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-fsdevel@vger.kernel.org,
"Anders Roxell" <anders.roxell@linaro.org>
Subject: Re: [PATCH 2/2] selftests/proc: Do not build x86-64 tests on non-x86-64 builds
Date: Fri, 30 Jun 2023 12:27:44 +0200 [thread overview]
Message-ID: <871qhttfbz.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <fd61fd96-f06f-4a2d-8707-0e1e395c9e51@p183>
Alexey Dobriyan <adobriyan@gmail.com> writes:
> On Thu, Jun 29, 2023 at 06:23:00PM +0200, Björn Töpel wrote:
>> From: Björn Töpel <bjorn@rivosinc.com>
>>
>> The proc-empty-vm test is x86-64 only. Remove that test from
>> non-x86-64 builds.
>>
>> Signed-off-by: Björn Töpel <bjorn@rivosinc.com>
>
> What's the address space size on risc-v?
Different sizes are supported, 39b, 48b, and 57b:
Documentation/riscv/vm-layout.rst
Did you have anything particular in mind?
next prev parent reply other threads:[~2023-06-30 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 16:22 [PATCH 0/2] Two cross-compilation kselftest fixes Björn Töpel
2023-06-29 16:22 ` [PATCH 1/2] selftests/openat2: Run-time check for -fsanitize=undefined Björn Töpel
2023-06-29 16:23 ` [PATCH 2/2] selftests/proc: Do not build x86-64 tests on non-x86-64 builds Björn Töpel
2023-06-29 19:42 ` Alexey Dobriyan
2023-06-30 10:27 ` Björn Töpel [this message]
2023-07-03 6:36 ` [PATCH 0/2] Two cross-compilation kselftest fixes Björn Töpel
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=871qhttfbz.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=adobriyan@gmail.com \
--cc=anders.roxell@linaro.org \
--cc=bjorn@rivosinc.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=shuah@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