All of lore.kernel.org
 help / color / mirror / Atom feed
From: Itaru Kitayama <itaru.kitayama@linux.dev>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Shuah Khan <shuah@kernel.org>,
	kvm@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Itaru Kitayama <itaru.kitayama@fujitsu.com>
Subject: Re: [PATCH] Build guest_memfd_test also on arm64.
Date: Mon, 13 May 2024 10:46:54 +0900	[thread overview]
Message-ID: <9804CC2E-9F3B-4A39-B91F-9C91155CC50F@linux.dev> (raw)
In-Reply-To: <E7E9D65D-1DAC-4CA5-BDA5-D515D15E50F8@linux.dev>



> On May 8, 2024, at 15:41, Itaru Kitayama <itaru.kitayama@linux.dev> wrote:
> 
> Hi Paolo,
> 
>> On Feb 23, 2024, at 17:57, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> 
>> On Thu, Feb 22, 2024 at 12:44 AM Itaru Kitayama
>> <itaru.kitayama@linux.dev> wrote:
>>> on arm64 KVM_CAP_GUEST_MEMDF capability is not enabled, but
>>> guest_memfd_test can build on arm64, let's build it on arm64 as well.
>> 
>> The test will be skipped, so there's no point in compiling it.
> 
> It’s not merged yet, but the Arm CCA support series V2 is out there, would you consider building it for arm64
> as well?

Unless KVM_CAP_GUEST_MEMFD is supported in arm64, you think it should not be built at all?
Then, I will build them locally for now.

Thanks,
Itaru.

> 
> Thanks,
> Itaru.
> 
>> 
>> Paolo
>> 
>>> Signed-off-by: Itaru Kitayama <itaru.kitayama@fujitsu.com>
>>> ---
>>> tools/testing/selftests/kvm/Makefile | 1 +
>>> 1 file changed, 1 insertion(+)
>>> 
>>> diff --git a/tools/testing/selftests/kvm/Makefile b/tools/testing/selftests/kvm/Makefile
>>> index 492e937fab00..8a4f8afb81ca 100644
>>> --- a/tools/testing/selftests/kvm/Makefile
>>> +++ b/tools/testing/selftests/kvm/Makefile
>>> @@ -158,6 +158,7 @@ TEST_GEN_PROGS_aarch64 += access_tracking_perf_test
>>> TEST_GEN_PROGS_aarch64 += demand_paging_test
>>> TEST_GEN_PROGS_aarch64 += dirty_log_test
>>> TEST_GEN_PROGS_aarch64 += dirty_log_perf_test
>>> +TEST_GEN_PROGS_aarch64 += guest_memfd_test
>>> TEST_GEN_PROGS_aarch64 += guest_print_test
>>> TEST_GEN_PROGS_aarch64 += get-reg-list
>>> TEST_GEN_PROGS_aarch64 += kvm_create_max_vcpus
>>> 
>>> ---
>>> base-commit: 39133352cbed6626956d38ed72012f49b0421e7b
>>> change-id: 20240222-memfd-7285f9564c1e
>>> 
>>> Best regards,
>>> --
>>> Itaru Kitayama <itaru.kitayama@linux.dev>
>>> 
>> 
> 


      reply	other threads:[~2024-05-13  1:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 23:38 [PATCH] Build guest_memfd_test also on arm64 Itaru Kitayama
2024-02-23  8:57 ` Paolo Bonzini
2024-05-08  6:41   ` Itaru Kitayama
2024-05-13  1:46     ` Itaru Kitayama [this message]

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=9804CC2E-9F3B-4A39-B91F-9C91155CC50F@linux.dev \
    --to=itaru.kitayama@linux.dev \
    --cc=itaru.kitayama@fujitsu.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.