From: Richard Henderson <richard.henderson@linaro.org>
To: "Gustavo Romero" <gustavo.romero@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, alex.bennee@linaro.org
Cc: peter.maydell@linaro.org
Subject: Re: [PATCH v6 06/11] target/arm: Factor out code for setting MTE TCF0 field
Date: Fri, 28 Jun 2024 10:00:18 -0700 [thread overview]
Message-ID: <ea688598-b4a5-40f4-a749-c155ecc0988c@linaro.org> (raw)
In-Reply-To: <790bf46c-bf01-b8db-2030-af669cd98c49@linaro.org>
On 6/28/24 08:49, Gustavo Romero wrote:
> I thought you meant osdep.h should not be included _at all_ in my case, either
> in mte_user_helper.h or in mte_user_helper.c. Maybe the wording in the docs
> should be "Do not include "qemu/osdep.h" from header files. Include it from .c
> files, when necessary.".
Not "when necessary", always, and always first.
See the "Include directives" section of docs/devel/style.rst, which does explicitly say
'Do not include "qemu/osdep.h" from header files'.
> I think we agree osdep.h is necessary and must be put in mte_user_helper.c. But
> that left me wondering how it would work for sources including mte_user_helper.h,
> because it can be the case they don't have the declarations for the types used in
> the function prototypes, in this case, for CPUArchState and abi_long types in
> arm_set_mte_tcf0.
CPUArchState will come from qemu/typedefs.h via osdep.h.
For this particular function, 'int' would have been enough,
since we only care about the low two bits.
r~
next prev parent reply other threads:[~2024-06-28 17:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 5:08 [PATCH v6 00/11] Add MTE stubs for aarch64 user mode Gustavo Romero
2024-06-28 5:08 ` [PATCH v6 01/11] gdbstub: Clean up process_string_cmd Gustavo Romero
2024-06-28 7:05 ` Philippe Mathieu-Daudé
2024-06-28 5:08 ` [PATCH v6 02/11] gdbstub: Move GdbCmdParseEntry into a new header file Gustavo Romero
2024-06-28 5:08 ` [PATCH v6 03/11] gdbstub: Add support for target-specific stubs Gustavo Romero
2024-06-28 5:08 ` [PATCH v6 04/11] target/arm: Fix exception case in allocation_tag_mem_probe Gustavo Romero
2024-06-28 5:08 ` [PATCH v6 05/11] target/arm: Make some MTE helpers widely available Gustavo Romero
2024-06-28 5:08 ` [PATCH v6 06/11] target/arm: Factor out code for setting MTE TCF0 field Gustavo Romero
2024-06-28 7:08 ` Philippe Mathieu-Daudé
2024-06-28 15:49 ` Gustavo Romero
2024-06-28 16:18 ` Philippe Mathieu-Daudé
2024-06-28 17:00 ` Richard Henderson [this message]
2024-06-28 18:13 ` Gustavo Romero
2024-06-29 18:38 ` Peter Maydell
2024-06-28 12:14 ` Alex Bennée
2024-06-28 14:55 ` Gustavo Romero
2024-06-28 15:15 ` Alex Bennée
2024-06-28 5:08 ` [PATCH v6 07/11] gdbstub: Make hex conversion function non-internal Gustavo Romero
2024-06-28 5:08 ` [PATCH v6 08/11] gdbstub: Pass CPU context to command handler Gustavo Romero
2024-06-28 5:08 ` [PATCH v6 09/11] gdbstub: Use true to set cmd_startswith Gustavo Romero
2024-06-28 5:08 ` [PATCH v6 10/11] gdbstub: Add support for MTE in user mode Gustavo Romero
2024-06-28 5:08 ` [PATCH v6 11/11] tests/tcg/aarch64: Add MTE gdbstub tests Gustavo Romero
2024-06-28 12:34 ` [PATCH v6 00/11] Add MTE stubs for aarch64 user mode Alex Bennée
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=ea688598-b4a5-40f4-a749-c155ecc0988c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=gustavo.romero@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).