[PATCH RESEND 0/6] Introduce extension implied rules

2024-06-05 Thread Jerry Zhang Jian
Reviewed-by: Jerry Zhang Jian -- 2.44.0

[PATCH v2] target/riscv: zvbb implies zvkb

2024-05-28 Thread Jerry Zhang Jian
- According to RISC-V crypto spec, Zvkb extension is a proper subset of the Zvbb extension. - Reference: https://github.com/riscv/riscv-crypto/blob/1769c2609bf4535632e0c0fd715778f212bb272e/doc/vector/riscv-crypto-vector-zvkb.adoc?plain=1#L10 Signed-off-by: Jerry Zhang Jian --- target/riscv

Re: [PATCH] target/riscv: zvbb implies zvkb

2024-05-28 Thread Jerry ZJ
Canary Mail You've received a secure email jerry.zhangj...@sifive.com has sent you a secure email via Canary Mail. Read Secure Email (https://secure.canarymail.io/read?obj_id=04c03de7-d745-472e-b026-7dd839bc34a0&obj_key=eGJUOWtORkFXenBvWTJyMSt4VGpWdz09&thr_id=04c03de7-d745-472e-b026-7dd839bc34a

Re: [PATCH] target/riscv: zvbb implies zvkb

2024-05-28 Thread Jerry Zhang Jian
Sorry, I had the bad mail client setting. Please ignore the previous email, and I will resubmit the patch. -- Jerry Jerry ZJ 於 2024年5月28日 週二 下午8:12寫道: > > *Canary Mail You've received a secure email* > jerry.zhangj...@sifive.com has sent you a secure email via Canary Mail. >

[PATCH] target/riscv: zvbb implies zvkb

2024-05-16 Thread Jerry Zhang Jian
- According to RISC-V crypto spec, Zvkb extension is a proper subset of the Zvbb extension. - Reference: https://github.com/riscv/riscv-crypto/blob/1769c2609bf4535632e0c0fd715778f212bb272e/doc/vector/riscv-crypto-vector-zvkb.adoc?plain=1#L10 Signed-off-by: Jerry Zhang Jian --- target/riscv

Re: [PATCH v10 08/18] target/riscv: add rva22u64 profile definition

2023-11-21 Thread Jerry Shih
ort them in `riscv,isa`? If we try to check the RVA22 profile in linux kernel running with qemu, the isa string is not match RVA22 profile. Thanks, Jerry

Re: [PATCH v10 08/18] target/riscv: add rva22u64 profile definition

2023-11-21 Thread Jerry Shih
in QEMU so we'll consider > + * all these named features as always enabled. > + * Hi Daniel, If the cache related extensions are `ignored/assumed enabled`, why don't we export them in `riscv,isa`? If we try to check the RVA22 profile in linux kernel running with qemu, the isa string is not match RVA22 profile. Thanks, Jerry

Re: [PATCH] target/riscv: don't enable Zfa by default

2023-11-06 Thread Jerry ZJ
,zba=true,zbb=true ./hello_rv32imac Then you will get the following error message: qemu-riscv32: Zfa extension requires F extension Since Zfa has just been ratified, I suppose disabling it by default makes sense and will not break anything that exists. Best Regards, Jerry ZJ SiFive Inc. Taiwan

Re: [PATCH] target/riscv: don't enable Zfa by default

2023-11-06 Thread Jerry ZJ
=true, Zicsr=true, Zifencei=true, zba=true, zbb=true, the QEMU will have the following error. Zfa extension requires F extension IMHO, we should not enable Zfa extension by default, especially when Zfa requires F to be enabled implicitly. Best Regards, Jerry ZJ SiFive Inc. Taiwan On Nov 6, 2023 at

[PATCH] target/riscv: don't enable Zfa by default

2023-11-06 Thread Jerry Zhang Jian
- Zfa requires F, we should not assume all CPUs have F extension support. Signed-off-by: Jerry Zhang Jian --- target/riscv/cpu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c index ac4a6c7eec..c9f11509c8 100644 --- a/target/riscv

Windows 10 client 4k

2020-07-27 Thread Jerry Geis
different way to do this - but I dont know what that is . Suggestions? My LInux host is running in 4K. Thanks, Jerry

Re: Qemu on Windows 10 - no acceleration found

2020-03-21 Thread Jerry Geis
Perfect Stefan - that did the trick. Thank you. Jerry On Sat, Mar 21, 2020 at 3:14 AM Stefan Weil wrote: > Am 20.03.20 um 21:22 schrieb Jerry Geis: > > > So I tried --enable-whpx and I get Invalid option. Im on Windows 10 > > and QEMU 4.2.0 > > > > I'm co

Re: Qemu on Windows 10 - no acceleration found

2020-03-20 Thread Jerry Geis
So I tried --enable-whpx and I get Invalid option. Im on Windows 10 and QEMU 4.2.0 I'm confused. Then I don't know where to download the HAXM. The place I found is GIT and it wants the user to compile it. I was looking for just an EXE. Thanks Jerry

Qemu on Windows 10 - no acceleration found

2020-03-20 Thread Jerry Geis
Hi All, I have tried QEMU on Windows 10 host with and without HyperV active in the features list. Neither seemed to affect the "really slow" speed. Either option results in -enable-kvm giving "no acceleration found". How do I enable acceleration on QEMU for windows. Jerry

Re: How do UEFI on Windows host

2020-02-14 Thread Jerry Geis
I dont know how to get all files listing on windows. But, I cd \program files\qemu dir *.fd edk2-x86_64-code.fd edk2-x86_64-secure-code.fd It seems like from other posts these might be the files - but still not sure how to do "boot" a command line for UEFI. Jerry

How do UEFI on Windows host

2020-02-12 Thread Jerry Geis
How do I start a UEFI install (centos 8) for UEFI with 4.2.0 on Windows host ??? I can do a regular install just fine. I desire to do UEFI install. Thanks, Jerry

Qemu 4.2.0 on Windows host

2020-02-06 Thread Jerry Geis
I am trying to figure out how to boot a linux external USB disk from windows host ? I do this all the time on linux - simply -hda /dev/sdb But how do I reference the USB on Windows ? Thanks, Jerry

[Qemu-devel] [Bug 1831115] Re: qemu 4.0.0 on aarch64: uefi firmware oversize

2019-05-31 Thread Jerry
4.0.0, kernel: 4.19.46-1-ARCH, hostname: jerry-n1.localdomain LC_ALL=C \ PATH=/usr/local/sbin:/usr/local/bin:/usr/bin \ HOME=/var/lib/libvirt/qemu/domain-2-debiantesting \ XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-2-debiantesting/.local/share \ XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-2-

[Qemu-devel] [Bug 1831115] Re: qemu 4.0.0 on aarch64: uefi firmware oversize

2019-05-31 Thread Jerry
6-1-ARCH, hostname: jerry-n1.localdomain LC_ALL=C \ PATH=/usr/local/sbin:/usr/local/bin:/usr/bin \ HOME=/var/lib/libvirt/qemu/domain-2-debiantesting \ XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-2-debiantesting/.local/share \ XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-2-debiantesting/.cache \

[Qemu-devel] [Bug 1831115] Re: qemu 4.0.0 on aarch64: uefi firmware oversize

2019-05-31 Thread Jerry
[jerry@jerry-n1 aarch64]$ du -b * 67108864AAVMF_CODE.fd 67108864AAVMF_VARS.fd 67108864QEMU_EFI.fd 67108864QEMU_VARS.fd 2097152 QEMU_EFI.fd.orig 786432 QEMU_VARS.fd.orig Both files have been padded to 64MB. (if padding means filling it with /dev/zero

[Qemu-devel] [Bug 1831115] [NEW] qemu 4.0.0 on aarch64: uefi firmware oversize

2019-05-30 Thread Jerry
e qemu-efi-aarch64 0~20181115.85588389-3) Below is my libvirt log. 2019-05-30 15:07:44.216+: starting up libvirt version: 5.3.0, qemu version: 4.0.0, kernel: 4.19.46-1-ARCH, hostname: jerry-n1.localdomain LC_ALL=C \ PATH=/usr/local/sbin:/usr/local/bin:/usr/bin \ HOME=/var/lib/libvirt/qem

Re: [Qemu-devel] Question about VM inner route entry's lost when vhost-user reconnect

2019-03-19 Thread Lilijun (Jerry, Cloud Networking)
mail.com] > Sent: Wednesday, March 13, 2019 10:55 PM > To: Lilijun (Jerry, Cloud Networking) > Cc: qemu-devel@nongnu.org; wangxin (U) > ; wangyunjian > > Subject: Re: [Qemu-devel] Question about VM inner route entry's lost when > vhost-user reconnect > > On Tue, Mar 12,

Re: [Qemu-devel] Question about VM inner route entry's lost when vhost-user reconnect

2019-03-11 Thread Lilijun (Jerry, Cloud Networking)
> -Original Message- > From: Stefan Hajnoczi [mailto:stefa...@gmail.com] > Sent: Monday, March 11, 2019 5:47 PM > To: Lilijun (Jerry, Cloud Networking) > Cc: qemu-devel@nongnu.org; wangxin (U) > ; wangyunjian > > Subject: Re: [Qemu-devel] Question about VM

Re: [Qemu-devel] Question about VM inner route entry's lost when vhost-user reconnect

2019-03-07 Thread Lilijun (Jerry, Cloud Networking)
to:stefa...@gmail.com] > Sent: Wednesday, March 06, 2019 6:07 PM > To: Lilijun (Jerry, Cloud Networking) > Cc: qemu-devel@nongnu.org; wangxin (U) > ; wangyunjian > > Subject: Re: [Qemu-devel] Question about VM inner route entry's lost when > vhost-user reconnect > &

Re: [Qemu-devel] Question about VM virtio device's link down delay when vhost-user reconnect

2019-03-07 Thread Lilijun (Jerry, Cloud Networking)
> -Original Message- > From: Michael S. Tsirkin [mailto:m...@redhat.com] > > On Wed, Mar 06, 2019 at 07:36:44AM +0000, Lilijun (Jerry, Cloud Networking) > wrote: > > Thanks a lot for your advice. > > > > Maybe there are two methods to add this option:

Re: [Qemu-devel] Question about VM virtio device's link down delay when vhost-user reconnect

2019-03-05 Thread Lilijun (Jerry, Cloud Networking)
uot; virsh qemu-monitor-command vm1 --hmp info chardev " to lookup that status. Another one is to add new type event for Qemu to notify libvirt or other upper level components. Jerry > -Original Message- > From: Michael S. Tsirkin [mailto:m...@redhat.com] > Sent: Tuesday, Marc

[Qemu-devel] Question about VM virtio device's link down delay when vhost-user reconnect

2019-03-04 Thread Lilijun (Jerry, Cloud Networking)
t's connections before the time of "link_down_delay" ms passed, we need not do that link down notification to VM. Or else, if that's timeout, VM can be notified the link down event as before. Is there any other opinions about this solution? Or some better ideas? Thanks. B.R. Jerry

[Qemu-devel] Question about VM inner route entry's lost when vhost-user reconnect

2019-03-04 Thread Lilijun (Jerry, Cloud Networking)
ailed. Is there some work on this problem? Can we keep the vNIC's link up status when do vhost-user's reconnecting work? Thanks. Jerry

[Qemu-devel] 答复: Can we increase vring size over 1024?

2016-09-05 Thread Lilijun (Jerry)
com; jasow...@redhat.com; virtio-...@lists.oasis-open.org; Huangpeng (Peter); qemu-devel@nongnu.org; k...@vger.kernel.org; Lilijun (Jerry) 主题: Re: [Qemu-devel] Can we increase vring size over 1024? On Fri, Sep 02, 2016 at 06:55:35AM +, Gonglei (Arei) wrote: > Michael, you made a presentation ab

[Qemu-devel] Re: [PATCH] Implement ACPI specs 3.0, 4.7.2.5

2007-07-20 Thread Jerry Kemp
Does this mean that there will be ACPI updates in the next Qemu release? Thanks, Jerry K Sylvain Petreolle wrote: Maybe nobody had a look on it, like these 3 others. I added their links on the qemu-devel archives. Implement ACPI specs 3.0, 4.7.2.5 Add support for VDI images ipc endianness

[Qemu-devel] What is the current support state for APCI

2007-07-18 Thread Jerry Kemp
where development is at for APCI, or provide a URL where I can RTFM? TIA for any replies, Jerry