From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Riku Voipio <riku.voipio@iki.fi>,
Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH 7/9] user: Declare target-specific prototypes in 'user/cpu-target.h'
Date: Fri, 11 Feb 2022 10:19:26 +1100 [thread overview]
Message-ID: <cdd11da9-a90d-75ac-40f7-7086e7e40f66@linaro.org> (raw)
In-Reply-To: <20220209230030.93987-8-f4bug@amsat.org>
On 2/10/22 10:00, Philippe Mathieu-Daudé wrote:
> Move user-mode specific prototypes from "exec/exec-all.h"
> to "user/cpu-target.h".
>
> Signed-off-by: Philippe Mathieu-Daudé<f4bug@amsat.org>
> ---
Why a new cpu-target.h, and what is it supposed to mean? What else is going in there? It
all looks cpu_loop related so far.
Why is this separate from the next patch, with "cpu-common.h", which also appears to be
basically cpu_loop related?
r~
next prev parent reply other threads:[~2022-02-10 23:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 23:00 [PATCH 0/9] exec: Split some user-mode specific declarations from 'exec/exec-all.h' Philippe Mathieu-Daudé via
2022-02-09 23:00 ` [PATCH 1/9] accel/tcg: Add missing 'tcg/tcg.h' header Philippe Mathieu-Daudé via
2022-02-10 23:25 ` Richard Henderson
2022-02-11 9:34 ` Philippe Mathieu-Daudé via
2022-02-09 23:00 ` [PATCH 2/9] coverity-scan: Cover common-user/ Philippe Mathieu-Daudé via
2022-02-10 23:08 ` Richard Henderson
2022-02-11 11:56 ` Peter Maydell
2022-02-11 12:38 ` Philippe Mathieu-Daudé via
2022-02-11 12:54 ` Peter Maydell
2022-02-09 23:00 ` [PATCH 3/9] include: Move exec/user/ to user/ Philippe Mathieu-Daudé via
2022-02-10 23:12 ` Richard Henderson
2022-02-09 23:00 ` [PATCH 4/9] linux-user/exit: Add missing 'qemu/plugin.h' header Philippe Mathieu-Daudé via
2022-02-10 23:13 ` Richard Henderson
2022-02-09 23:00 ` [PATCH 5/9] linux-user/cpu_loop: Add missing 'exec/cpu-all.h' header Philippe Mathieu-Daudé via
2022-02-10 23:13 ` Richard Henderson
2022-02-09 23:00 ` [PATCH 6/9] exec: Define MMUAccessType in 'exec/cpu-tlb.h' header Philippe Mathieu-Daudé via
2022-02-10 23:14 ` Richard Henderson
2022-02-11 9:32 ` Philippe Mathieu-Daudé via
2022-02-09 23:00 ` [PATCH 7/9] user: Declare target-specific prototypes in 'user/cpu-target.h' Philippe Mathieu-Daudé via
2022-02-10 23:19 ` Richard Henderson [this message]
2022-02-11 9:30 ` Philippe Mathieu-Daudé via
2022-02-09 23:00 ` [PATCH 8/9] user: Declare target-agnostic prototypes in 'user/cpu-common.h' Philippe Mathieu-Daudé via
2022-02-09 23:00 ` [PATCH 9/9] user: Share preexit_cleanup() with linux and bsd implementations Philippe Mathieu-Daudé via
2022-02-10 23:23 ` 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=cdd11da9-a90d-75ac-40f7-7086e7e40f66@linaro.org \
--to=richard.henderson@linaro.org \
--cc=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).