From: Sean Christopherson <seanjc@google.com>
To: Bibo Mao <maobibo@loongson.cn>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Tianrui Zhao <zhaotianrui@loongson.cn>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 4/4] KVM: selftests: Add test cases for LoongArch
Date: Fri, 26 Jan 2024 12:28:31 -0800 [thread overview]
Message-ID: <ZbQV75Q-N_cJLhj6@google.com> (raw)
In-Reply-To: <20240125015420.1960090-5-maobibo@loongson.cn>
On Thu, Jan 25, 2024, Bibo Mao wrote:
> diff --git a/tools/testing/selftests/kvm/set_memory_region_test.c b/tools/testing/selftests/kvm/set_memory_region_test.c
> index 075b80dbe237..7b09e59296be 100644
> --- a/tools/testing/selftests/kvm/set_memory_region_test.c
> +++ b/tools/testing/selftests/kvm/set_memory_region_test.c
> @@ -333,7 +333,7 @@ static void test_invalid_memory_region_flags(void)
> struct kvm_vm *vm;
> int r, i;
>
> -#if defined __aarch64__ || defined __x86_64__
> +#if defined __aarch64__ || defined __x86_64__ || __loongarch__
I assume that last one wants to be "defined __loongarch__"
> supported_flags |= KVM_MEM_READONLY;
> #endif
>
> --
> 2.39.3
>
next prev parent reply other threads:[~2024-01-26 20:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 1:54 [PATCH v6 0/4] VM: selftests: Add LoongArch support Bibo Mao
2024-01-25 1:54 ` [PATCH v6 1/4] KVM: selftests: Add KVM selftests header files for LoongArch Bibo Mao
2024-01-25 1:54 ` [PATCH v6 2/4] KVM: selftests: Add core KVM selftests support " Bibo Mao
2024-01-25 1:54 ` [PATCH v6 3/4] KVM: selftests: Add ucall test " Bibo Mao
2024-01-25 1:54 ` [PATCH v6 4/4] KVM: selftests: Add test cases " Bibo Mao
2024-01-26 20:28 ` Sean Christopherson [this message]
2024-01-29 1:28 ` maobibo
2024-01-26 20:32 ` [PATCH v6 0/4] VM: selftests: Add LoongArch support Sean Christopherson
2024-01-29 2:41 ` maobibo
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=ZbQV75Q-N_cJLhj6@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maobibo@loongson.cn \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.org \
--cc=zhaotianrui@loongson.cn \
/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