From: Michael Tokarev <mjt@tls.msk.ru>
To: Andrew Jones <ajones@ventanamicro.com>,
Yong-Xuan Wang <yongxuan.wang@sifive.com>,
qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
qemu-stable <qemu-stable@nongnu.org>
Cc: greentime.hu@sifive.com, vincent.chen@sifive.com,
frank.chang@sifive.com, jim.shu@sifive.com,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Bin Meng" <bin.meng@windriver.com>,
"Weiwei Li" <liwei1518@gmail.com>,
"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH v2 1/1] target/riscv/kvm: fix timebase-frequency when using KVM acceleration
Date: Sat, 27 Apr 2024 10:24:04 +0300 [thread overview]
Message-ID: <97934a65-f62f-49e9-820b-07463c3029ed@tls.msk.ru> (raw)
In-Reply-To: <c174a8cd-4a53-4a28-8688-aa62c7eab45e@tls.msk.ru>
27.04.2024 09:59, Michael Tokarev wrote:
> 27.04.2024 09:23, Andrew Jones wrote:
...
>> It's possible to cross-compile qemu, so it'd be good to add that to the CI for riscv until we can add native compiling.
>
> Yes, definitely. Qemu is already being cross-compiled on all "other"
> architectures during CI. But it is also being *run*, not just compiled.
> And this is what's broken on riscv64 for almost a year now, and this
> job has been disabled. Instead, the *run* part of this job needs to
> be disabled, but *build* part should be kept.
Aha. I was wrong. And I was there before too, for sure, - just forgot
about it. In order to be cross-compiled, the cross-build environment
needs to have target -dev libraries, not only the cross-compiler.
And this is where debian riscv64 port is failing.
So no, it is not currently possible to cross-compile qemu at least
on debian without building whole cross-environment with all libraries
and other necessary stuff.
I'll try to use debian riscv64 porterbox to at least verify the new
set of patches we'll pick here to fix this breakage, at least compiles
on riscv64 :)
> 10f86d1b845087d1 isn't sufficient, since it relies on 450bd6618fda3d
> "target/riscv/kvm: change KVM_REG_RISCV_FP_D to u64". In the same series
> there also was 49c211ffca00fdf7c "target/riscv/kvm: change KVM_REG_RISCV_FP_F
> to u32" - is it also needed?
49c211ffca00fdf7c is also needed. So it's 3 so far, still not compile-
tested. Anything else?
/mjt
next prev parent reply other threads:[~2024-04-27 7:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 6:15 [PATCH v2 1/1] target/riscv/kvm: fix timebase-frequency when using KVM acceleration Yong-Xuan Wang
2024-03-14 6:55 ` Philippe Mathieu-Daudé
2024-03-22 4:46 ` Alistair Francis
2024-03-22 4:47 ` Alistair Francis
2024-04-26 23:44 ` Michael Tokarev
2024-04-27 6:23 ` Andrew Jones
2024-04-27 6:59 ` Michael Tokarev
2024-04-27 7:24 ` Michael Tokarev [this message]
2024-04-27 15:17 ` Andrew Jones
2024-04-27 16:39 ` Michael Tokarev
2024-04-29 2:01 ` Alistair Francis
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=97934a65-f62f-49e9-820b-07463c3029ed@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=frank.chang@sifive.com \
--cc=greentime.hu@sifive.com \
--cc=jim.shu@sifive.com \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=vincent.chen@sifive.com \
--cc=yongxuan.wang@sifive.com \
--cc=zhiwei_liu@linux.alibaba.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 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.