From: Thomas Huth <thuth@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>,
Bruno Piazera Larsen <bruno.larsen@eldorado.org.br>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Lucas Mateus Martins Araujo e Castro
<lucas.araujo@eldorado.org.br>,
Fernando Eckhardt Valle <fernando.valle@eldorado.org.br>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
Andre Fernando da Silva <andre.silva@eldorado.org.br>,
Matheus Kowalczuk Ferst <matheus.ferst@eldorado.org.br>,
Luis Fernando Fujita Pires <luis.pires@eldorado.org.br>
Subject: Re: Discussion: Patch series that adds disable-tcg option for ppc targets
Date: Sat, 10 Apr 2021 07:43:36 +0200 [thread overview]
Message-ID: <d9fbd209-6bb9-982d-5bbd-580cbfa27c34@redhat.com> (raw)
In-Reply-To: <YGv7ku+6XNMW1QFM@yekko.fritz.box>
On 06/04/2021 08.11, David Gibson wrote:
> On Mon, Apr 05, 2021 at 01:32:18PM +0000, Bruno Piazera Larsen wrote:
[...]
>> * exclude 8 files from the build (dfp_helper.c, excp_helper.c,
>> fpu_helper.c, int_helper.c, mem_helper.c, misc_helper.c, *
>> translate.c, timebase_helper.c);
>
> That looks about right.
IIRC you don't only have to exclude translate.c from the build, you also
have to separate translate_init.c.inc from it, i.e. turn
translate_init.c.inc into a proper .c file and get rid of the #include
"translate_init.c.inc" statement in translate.c, since many functions in the
translate_init.c.inc file are still needed for the KVM-only builds, too. So
maybe that's a good place to start as a first mini series.
Thomas
next prev parent reply other threads:[~2021-04-10 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 13:32 Discussion: Patch series that adds disable-tcg option for ppc targets Bruno Piazera Larsen
2021-04-06 6:11 ` David Gibson
2021-04-10 5:43 ` Thomas Huth [this message]
2021-04-06 18:38 Bruno Piazera Larsen
2021-04-06 20:48 ` Fabiano Rosas
2021-04-07 3:01 ` David Gibson
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=d9fbd209-6bb9-982d-5bbd-580cbfa27c34@redhat.com \
--to=thuth@redhat.com \
--cc=andre.silva@eldorado.org.br \
--cc=bruno.larsen@eldorado.org.br \
--cc=david@gibson.dropbear.id.au \
--cc=fernando.valle@eldorado.org.br \
--cc=lucas.araujo@eldorado.org.br \
--cc=luis.pires@eldorado.org.br \
--cc=matheus.ferst@eldorado.org.br \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).