From: Laurent Vivier <laurent@vivier.eu>
To: Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, Afonso Bordado <afonsobordado@gmail.com>
Subject: Re: [PULL 0/9] Linux user for 8.1 patches
Date: Mon, 15 May 2023 17:50:03 +0200 [thread overview]
Message-ID: <c05bbb2e-2739-c8c8-33c5-908a8a2c36e1@vivier.eu> (raw)
In-Reply-To: <4a37146d-b3b7-206d-cc75-617dc2a3674a@linaro.org>
Le 15/05/2023 à 15:55, Richard Henderson a écrit :
> On 5/15/23 01:31, Laurent Vivier wrote:
>> The following changes since commit 7c18f2d663521f1b31b821a13358ce38075eaf7d:
>>
>> Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into staging (2023-04-29 23:07:17
>> +0100)
>>
>> are available in the Git repository at:
>>
>> https://github.com/vivier/qemu.git tags/linux-user-for-8.1-pull-request
>>
>> for you to fetch changes up to 015ebc4aaa47612514a5c846b9db0d76b653b75f:
>>
>> linux-user: fix getgroups/setgroups allocations (2023-05-14 18:08:04 +0200)
>>
>> ----------------------------------------------------------------
>> linux-user pull request 20230512-v2
>>
>> add open_tree(), move_mount()
>> add /proc/cpuinfo for riscv
>> fixes and cleanup
>
> The new test in patch 1 fails:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/4285710689#L4825
>
> TEST cpuinfo on riscv64
> cpuinfo: /builds/qemu-project/qemu/tests/tcg/riscv64/cpuinfo.c:20: main: Assertion `strcmp(buffer,
> "isa\t\t: rv64imafdc_zicsr_zifencei\n") == 0' failed.
> timeout: the monitored command dumped core
> Aborted
> make[1]: *** [Makefile:174: run-cpuinfo] Error 134
> make: *** [/builds/qemu-project/qemu/tests/Makefile.include:56: run-tcg-tests-riscv64-linux-user]
> Error 2
> make: *** Waiting for unfinished jobs....
>
>
> r~
Strange, it worked for me:
https://gitlab.com/laurent_vivier/qemu/-/jobs/4281774977#L4844
Afonso, could you have a look?
Thanks,
Laurent
next prev parent reply other threads:[~2023-05-15 15:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 8:31 [PULL 0/9] Linux user for 8.1 patches Laurent Vivier
2023-05-15 8:31 ` [PULL 1/9] linux-user: Emulate /proc/cpuinfo output for riscv Laurent Vivier
2023-05-15 8:31 ` [PULL 2/9] linux-user: report ENOTTY for unknown ioctls Laurent Vivier
2023-05-15 8:31 ` [PULL 3/9] linux-user: Add move_mount() syscall Laurent Vivier
2023-05-15 8:31 ` [PULL 4/9] linux-user: Add open_tree() syscall Laurent Vivier
2023-05-15 8:31 ` [PULL 5/9] linux-user/main: Use list_cpus() instead of cpu_list() Laurent Vivier
2023-05-15 8:31 ` [PULL 6/9] linux-user: Add new flag VERIFY_NONE Laurent Vivier
2023-05-15 8:31 ` [PULL 7/9] linux-user: Don't require PROT_READ for mincore Laurent Vivier
2023-05-15 8:31 ` [PULL 8/9] linux-user: Fix mips fp64 executables loading Laurent Vivier
2023-05-15 8:31 ` [PULL 9/9] linux-user: fix getgroups/setgroups allocations Laurent Vivier
2023-05-15 13:55 ` [PULL 0/9] Linux user for 8.1 patches Richard Henderson
2023-05-15 15:50 ` Laurent Vivier [this message]
2023-05-16 9:11 ` Laurent Vivier
2023-05-16 10:20 ` Afonso Bordado
2023-05-16 10:46 ` Laurent Vivier
-- strict thread matches above, loose matches on Subject: below --
2023-05-17 8:01 Laurent Vivier
2023-05-17 16:04 ` Richard Henderson
2023-05-16 12:48 Laurent Vivier
2023-05-16 17:08 ` Richard Henderson
2023-05-17 6:21 ` Laurent Vivier
2023-05-12 11:22 Laurent Vivier
2023-05-13 6:36 ` Richard Henderson
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=c05bbb2e-2739-c8c8-33c5-908a8a2c36e1@vivier.eu \
--to=laurent@vivier.eu \
--cc=afonsobordado@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
/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 NNTP newsgroup(s).