From: Gavin Shan <gshan@redhat.com>
To: Nico Boehr <nrb@linux.ibm.com>, kvmarm@lists.linux.dev
Cc: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org,
linux-s390@vger.kernel.org, andrew.jones@linux.dev,
lvivier@redhat.com, thuth@redhat.com, frankja@linux.ibm.com,
imbrenda@linux.ibm.com, david@redhat.com, pbonzini@redhat.com,
shan.gavin@gmail.com
Subject: Re: [kvm-unit-tests PATCH v3] runtime: Allow to specify properties for accelerator
Date: Fri, 16 Jun 2023 10:41:29 +1000 [thread overview]
Message-ID: <2a1b0e2b-a412-143a-9a57-5f2c12e8944c@redhat.com> (raw)
In-Reply-To: <168683636810.207611.6242722390379085462@t14-nrb>
Hi Nico,
On 6/15/23 23:39, Nico Boehr wrote:
> Quoting Gavin Shan (2023-06-15 08:21:48)
>> There are extra properties for accelerators to enable the specific
>> features. For example, the dirty ring for KVM accelerator can be
>> enabled by "-accel kvm,dirty-ring-size=65536". Unfortuntely, the
>> extra properties for the accelerators aren't supported. It makes
>> it's impossible to test the combination of KVM and dirty ring
>> as the following error message indicates.
>>
>> # cd /home/gavin/sandbox/kvm-unit-tests/tests
>> # QEMU=/home/gavin/sandbox/qemu.main/build/qemu-system-aarch64 \
>> ACCEL=kvm,dirty-ring-size=65536 ./its-migration
>> :
>> BUILD_HEAD=2fffb37e
>> timeout -k 1s --foreground 90s /home/gavin/sandbox/qemu.main/build/qemu-system-aarch64 \
>> -nodefaults -machine virt -accel kvm,dirty-ring-size=65536 -cpu cortex-a57 \
>> -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd \
>> -device pci-testdev -display none -serial stdio -kernel _NO_FILE_4Uhere_ -smp 160 \
>> -machine gic-version=3 -append its-pending-migration # -initrd /tmp/tmp.gfDLa1EtWk
>> qemu-system-aarch64: kvm_init_vcpu: kvm_arch_init_vcpu failed (0): Invalid argument
>>
>> Allow to specify extra properties for accelerators. With this, the
>> "its-migration" can be tested for the combination of KVM and dirty
>> ring.
>>
>> Signed-off-by: Gavin Shan <gshan@redhat.com>
>
> Maybe get_qemu_accelerator could be renamed now, since it doesn't actually "get"
> anything, so maybe check_qemu_accelerator?
>
> In any case, I gave it a quick run on s390x with kvm and tcg and nothing seems
> to break, hence for the changes in s390x:
>
> Tested-by: Nico Boehr <nrb@linux.ibm.com>
> Acked-by: Nico Boehr <nrb@linux.ibm.com>
>
Thanks for a quick try and comment for this. I guess it's fine to keep
the function name as get_qemu_accelator() because $ACCEL is split into
$ACCEL and $ACCEL_PROPS inside it, even it don't print the accelerator
name at return. However, I'm also fine with check_qemu_accelerator().
Lets see what's Drew's comment on this and I can post v4 to have the
modified function name, or an followup patch to modify the function name.
Thanks,
Gavin
next prev parent reply other threads:[~2023-06-16 0:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 6:21 [kvm-unit-tests PATCH v3] runtime: Allow to specify properties for accelerator Gavin Shan
2023-06-15 13:39 ` Nico Boehr
2023-06-16 0:41 ` Gavin Shan [this message]
2023-06-19 8:44 ` Andrew Jones
2023-06-20 4:14 ` Gavin Shan
2023-06-19 8:45 ` Andrew Jones
2023-06-20 4:13 ` Gavin Shan
2023-06-20 9:06 ` Andrew Jones
2023-06-23 4:22 ` Gavin Shan
2023-06-23 7:36 ` Andrew Jones
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=2a1b0e2b-a412-143a-9a57-5f2c12e8944c@redhat.com \
--to=gshan@redhat.com \
--cc=andrew.jones@linux.dev \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-s390@vger.kernel.org \
--cc=lvivier@redhat.com \
--cc=nrb@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=shan.gavin@gmail.com \
--cc=thuth@redhat.com \
/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