From: Alistair Francis <alistair23@gmail.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "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>,
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: Mon, 29 Apr 2024 12:01:50 +1000 [thread overview]
Message-ID: <CAKmqyKNRyRCqpvii=1JnAQ+=t_TVLiD1oQmFRbk8UkLSqCrDcQ@mail.gmail.com> (raw)
In-Reply-To: <6b154471-abfa-49a9-a269-912188c4730f@tls.msk.ru>
On Sun, Apr 28, 2024 at 2:41 AM Michael Tokarev <mjt@tls.msk.ru> wrote:
>
> 27.04.2024 18:17, Andrew Jones :
> > I wrote instructions [2] for how to cross-compile without a full environment/container once. It might be better for quick, local testing.
> >
> > [2] https://lore.kernel.org/qemu-riscv/20230726120706.335340-2-ajones@ventanamicro.com/
>
> I just extracted a few packages from debian riscv64 (like libglib & deps)
> in a separate dir and pointed various tools (pkgconf, gcc -I, gcc -L) to
> that dir.
>
>
> >> 49c211ffca00fdf7c is also needed. So it's 3 so far, still not compile-
> >> tested. Anything else?
> >
> > Those 3, the first of the series [1], are good. Not sure why it's still not compiling.
>
> Yes, I picked up these 3 I mentioned, in addition to the problematic one
> which is part of 8.2.3. Once I had the build environment, I tried compiling
> it, and it builds fine. I wrote it is not compile-TESTED, not as it fails
> to compile.
>
> Also, I tried to build qemu on a real riscv64 hardware (on a debian porterbox),
> -- it built fine (with the 3 mentioned changes applied) and is now running
> tests, but it looks like it will be fine too.
>
> > [1] https://lists.gnu.org/archive/html/qemu-devel/2023-12/msg01132.html
>
> So yes, I'm picking these additional 3 from this set, - the ones which
> I already mentioned.
Thanks so much for testing that.
I'm not really sure what to do about the RISC-V host builds. I keep
expecting distros to ship better RISC-V support, but still they don't
seem to have it
Alistair
>
> Thanks,
>
> /mjt
>
>
> --
> GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
> New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E
> Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5
> Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt
>
>
prev parent reply other threads:[~2024-04-29 2:02 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
2024-04-27 15:17 ` Andrew Jones
2024-04-27 16:39 ` Michael Tokarev
2024-04-29 2:01 ` Alistair Francis [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='CAKmqyKNRyRCqpvii=1JnAQ+=t_TVLiD1oQmFRbk8UkLSqCrDcQ@mail.gmail.com' \
--to=alistair23@gmail.com \
--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=mjt@tls.msk.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).