Reviewed-by: Jerry Zhang Jian
--
2.44.0
- 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
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
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.
>
- 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
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
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
,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
=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
- 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
different way to do
this - but I dont know what that is .
Suggestions? My LInux host is running in 4K.
Thanks,
Jerry
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
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
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
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 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
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
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-
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 \
[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
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
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,
> -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
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
>
&
> -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:
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
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
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
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
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
where development is at for APCI, or provide a
URL where I can RTFM?
TIA for any replies,
Jerry
31 matches
Mail list logo