From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Cc: Claudio Fontana <cfontana@suse.de>,
Laurent Vivier <laurent@vivier.eu>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 02/11] exec: Restrict hwaddr.h to sysemu/
Date: Tue, 6 Dec 2022 15:40:45 +0100 [thread overview]
Message-ID: <3f83743b-32f3-c9ec-fca5-e63ced14fe32@linaro.org> (raw)
In-Reply-To: <abeef930-8fc8-7afc-80d7-b9807fceb728@linaro.org>
On 6/12/22 15:32, Philippe Mathieu-Daudé wrote:
> On 26/5/21 20:15, Richard Henderson wrote:
>> On 5/17/21 4:11 AM, Philippe Mathieu-Daudé wrote:
>>> --- a/include/exec/hwaddr.h
>>> +++ b/include/exec/sysemu/hwaddr.h
>>> @@ -1,8 +1,9 @@
>>> /* Define hwaddr if it exists. */
>>> -#ifndef HWADDR_H
>>> -#define HWADDR_H
>>> +#ifndef EXEC_SYSEMU_HWADDR_H
>>> +#define EXEC_SYSEMU_HWADDR_H
>>> +#ifndef CONFIG_USER_ONLY
>>> #define HWADDR_BITS 64
>>> /* hwaddr is the type of a physical address (its size can
>>> @@ -23,4 +24,6 @@ typedef struct MemMapEntry {
>>> hwaddr size;
>>> } MemMapEntry;
>>> +#endif /* !CONFIG_USER_ONLY */
>>> +
>>> #endif
>>
>> Why no #error on this one, unlike the next patch.
>
> Because many files in user emulation include "exec/hwaddr.h" :(
See for example gdbstub/user.c:
int gdb_breakpoint_insert(CPUState *cs, int type, hwaddr addr, hwaddr len)
I suppose we should change the two hwaddr by vaddr:
/**
* vaddr:
* Type wide enough to contain any #target_ulong virtual address.
*/
next prev parent reply other threads:[~2022-12-06 14:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 11:11 [PATCH 00/11] exec: Restrict various system emulation specific headers (to sysemu) Philippe Mathieu-Daudé
2021-05-17 11:11 ` [PATCH 01/11] NOTFORMERGE target/arm: Restrict KVM files to softmmu Philippe Mathieu-Daudé
2021-05-17 11:11 ` [PATCH 02/11] exec: Restrict hwaddr.h to sysemu/ Philippe Mathieu-Daudé
2021-05-26 18:15 ` Richard Henderson
2022-12-06 14:32 ` Philippe Mathieu-Daudé
2022-12-06 14:40 ` Philippe Mathieu-Daudé [this message]
2022-12-06 14:53 ` Claudio Fontana
2022-12-06 15:38 ` Claudio Fontana
2022-12-06 17:09 ` Philippe Mathieu-Daudé
2022-12-06 17:17 ` Richard Henderson
2022-12-07 10:09 ` Claudio Fontana
2022-12-06 15:01 ` Peter Maydell
2021-05-17 11:11 ` [PATCH 03/11] exec: Restrict cputlb.h " Philippe Mathieu-Daudé
2021-05-17 11:11 ` [PATCH 04/11] exec: Restrict memory.h " Philippe Mathieu-Daudé
2021-05-17 11:11 ` [PATCH 05/11] exec: Restrict memory-internal.h " Philippe Mathieu-Daudé
2021-05-17 11:11 ` [PATCH 06/11] exec: Restrict address-spaces.h " Philippe Mathieu-Daudé
2021-05-17 11:11 ` [PATCH 07/11] exec: Extract CPU I/O instructions to "cpu-io.h" Philippe Mathieu-Daudé
2021-05-17 11:11 ` [PATCH 08/11] exec: Restrict ioport.h to sysemu/ Philippe Mathieu-Daudé
2021-05-17 11:11 ` [PATCH 09/11] exec: Restrict ram_addr.h " Philippe Mathieu-Daudé
2021-05-17 11:11 ` [PATCH 10/11] exec: Restrict ramblock.h " Philippe Mathieu-Daudé
2021-05-17 11:11 ` [PATCH 11/11] exec: Restrict confidential-guest-support.h " Philippe Mathieu-Daudé
2021-05-25 14:13 ` [PATCH 00/11] exec: Restrict various system emulation specific headers (to sysemu) Philippe Mathieu-Daudé
2021-11-06 14:58 ` Philippe Mathieu-Daudé
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=3f83743b-32f3-c9ec-fca5-e63ced14fe32@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=cfontana@suse.de \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.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).