From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: Richard Henderson <richard.henderson@linaro.org>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, gshan@redhat.com
Subject: Re: [PATCH v3 2/3] exec: Extract 'page-vary.h' header
Date: Tue, 23 Mar 2021 19:22:07 +0100 [thread overview]
Message-ID: <ddf09d50-9bf6-c828-7fa7-896f9ceb38df@amsat.org> (raw)
In-Reply-To: <20210323161601.454996-3-richard.henderson@linaro.org>
On 3/23/21 5:16 PM, Richard Henderson wrote:
> In the next commit we will extract the generic code out of
> page-vary.c, only keeping the target specific code. Both
> files will use the same TargetPageBits structure, so make
> its declaration in a shared header.
>
> As the common header can not use target specific types,
> use a uint64_t to hold the page mask value, and add a
> cast back to target_long in the TARGET_PAGE_MASK definitions.
>
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Message-Id: <20210322112427.4045204-3-f4bug@amsat.org>
> Signed-off-by: Richard Henderson <richard.henderson@linaro.org>
> ---
> include/exec/cpu-all.h | 11 ++++-------
> include/exec/page-vary.h | 29 +++++++++++++++++++++++++++++
> 2 files changed, 33 insertions(+), 7 deletions(-)
> create mode 100644 include/exec/page-vary.h
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
next prev parent reply other threads:[~2021-03-23 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 16:15 [PATCH v3 0/3] exec: Build page-vary-common.c with -fno-lto Richard Henderson
2021-03-23 16:15 ` [PATCH v3 1/3] exec: Rename exec-vary.c as page-vary.c Richard Henderson
2021-03-23 18:21 ` Philippe Mathieu-Daudé
2021-03-23 16:16 ` [PATCH v3 2/3] exec: Extract 'page-vary.h' header Richard Henderson
2021-03-23 18:22 ` Philippe Mathieu-Daudé [this message]
2021-03-23 16:16 ` [PATCH v3 3/3] exec: Build page-vary-common.c with -fno-lto 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=ddf09d50-9bf6-c828-7fa7-896f9ceb38df@amsat.org \
--to=f4bug@amsat.org \
--cc=gshan@redhat.com \
--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).