From: Laurent Vivier <laurent@vivier.eu>
To: Taylor Simpson <tsimpson@quicinc.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Alistair Francis <alistair.francis@wdc.com>,
Riku Voipio <riku.voipio@iki.fi>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH v3 1/4] scripts: add a script to generate syscall_nr.h
Date: Mon, 16 Mar 2020 17:45:51 +0100 [thread overview]
Message-ID: <ec9e86fe-76c2-bab0-6b08-c524e3582dba@vivier.eu> (raw)
In-Reply-To: <BYAPR02MB4886D8ECC90C0845C3BFE27FDEF90@BYAPR02MB4886.namprd02.prod.outlook.com>
Le 16/03/2020 à 17:21, Taylor Simpson a écrit :
>
>
>> -----Original Message-----
>> From: Laurent Vivier <laurent@vivier.eu>
>> Sent: Monday, March 16, 2020 3:56 AM
>> To: qemu-devel@nongnu.org
>> Cc: Laurent Vivier <laurent@vivier.eu>; Richard Henderson
>> <richard.henderson@linaro.org>; Riku Voipio <riku.voipio@iki.fi>; Taylor
>> Simpson <tsimpson@quicinc.com>; Alistair Francis
>> <alistair.francis@wdc.com>
>> Subject: [PATCH v3 1/4] scripts: add a script to generate syscall_nr.h
>>
>> This script is needed for targets based on asm-generic syscall numbers
>> generation
>>
>> +
>> +filter_defines()
>> +{
>> + grep -e "#define __NR_" -e "#define __NR3264"
>
> For Hexagon, we're still running a 4.9 kernel. When I tried out this script on that code base, there are a handful of these
> #undef __NR_syscalls
> #define __NR_syscalls 291
> This works fine with normal C preprocessing, and the last one wins. However, when the #undef's are filtered out, it lease to build errors from multiple #define's of TARGET_NR_syscalls. AFAIK, qemu doesn't use this, so it should be OK to filter out. So, I changed the above line to
> grep -e "#define __NR_" -e "#define __NR3264" | grep -v "__NR_syscalls"
>
> If you're OK incorporating that now, great! Otherwise, I'll add it to the Hexagon RFC patch series until we get to a newer kernel.
Sorry, I've just sent the pull-request.
Add it to your RFC, please.
It's why this script is only an helper, so it means once the file is
generated it can be edited before being committed.
Thanks,
Laurent
next prev parent reply other threads:[~2020-03-16 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 8:56 [PATCH v3 0/4] linux-user: generate syscall_nr.h from linux unistd.h Laurent Vivier
2020-03-16 8:56 ` [PATCH v3 1/4] scripts: add a script to generate syscall_nr.h Laurent Vivier
2020-03-16 16:21 ` Taylor Simpson
2020-03-16 16:45 ` Laurent Vivier [this message]
2020-03-16 19:27 ` Taylor Simpson
2020-03-16 20:20 ` Laurent Vivier
2020-03-16 8:56 ` [PATCH v3 2/4] linux-user, aarch64: sync syscall numbers with kernel v5.5 Laurent Vivier
2020-03-16 8:56 ` [PATCH v3 3/4] linux-user, nios2: " Laurent Vivier
2020-03-16 8:56 ` [PATCH v3 4/4] linux-user, openrisc: " Laurent Vivier
2020-03-16 10:55 ` [PATCH v3 0/4] linux-user: generate syscall_nr.h from linux unistd.h no-reply
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=ec9e86fe-76c2-bab0-6b08-c524e3582dba@vivier.eu \
--to=laurent@vivier.eu \
--cc=alistair.francis@wdc.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=riku.voipio@iki.fi \
--cc=tsimpson@quicinc.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 NNTP newsgroup(s).