From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>,
Richard Henderson <richard.henderson@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2 0/5] target/arm: Restrict TCG cpus to TCG accel
Date: Mon, 27 Apr 2020 15:42:29 +0200 [thread overview]
Message-ID: <25cbb189-19d2-5514-306f-51d176b61c39@redhat.com> (raw)
In-Reply-To: <CAFEAcA8j7y2VbM1U0Df-TEjS6Kh-iBGXA8Vg1ZrD5Ff6=WthjA@mail.gmail.com>
On 4/27/20 3:04 PM, Peter Maydell wrote:
> On Thu, 23 Apr 2020 at 08:34, Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>
>> These are the uncontroversial patches from "Support disabling
>> TCG on ARM (part 2)"
>> https://www.mail-archive.com/qemu-devel@nongnu.org/msg689168.html
>>
>> The other patches are blocked by the "accel: Allow targets to
>> use Kconfig" series:
>> https://www.mail-archive.com/qemu-devel@nongnu.org/msg689024.html
>>
>> All patches reviewed.
>>
>> Since v1:
>> - Dropped 'Make set_feature() available for other files' patch
>> which fails to build with KVM only, see:
>> https://lists.gnu.org/archive/html/qemu-devel/2020-04/msg03843.html
>>
>> Many thanks to Richard Henderson for his patience!
>>
>> Regards,
>>
>> Phil.
>>
>> Philippe Mathieu-Daudé (4):
>> target/arm: Restric the Address Translate write operation to TCG accel
>> target/arm/cpu: Use ARRAY_SIZE() to iterate over ARMCPUInfo[]
>> target/arm/cpu: Update coding style to make checkpatch.pl happy
>> target/arm: Restrict TCG cpus to TCG accel
>>
>> Thomas Huth (1):
>> target/arm: Make cpu_register() available for other files
>
>
> Patch 5 doesn't compile, because it moves code out from
> cpu.c to cpu_tcg.c, where it no longer has access to the
> file-local set_feature() function:
>
> CC arm-softmmu/target/arm/cpu_tcg.o
> /home/petmay01/linaro/qemu-from-laptop/qemu/target/arm/cpu_tcg.c:47:5:
> error: implicit declaration of function 'set_feature' is invalid in
> C99
> [-Werror,-Wimplicit-function-declaration]
> set_feature(&cpu->env, ARM_FEATURE_V5);
> ^
> [etc]
*Sigh* sorry for that, I'm still unsure what's the cleaner change to
deal with the different set_feature() KVM prototype:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg697523.html
>
> I've applied patches 1-4 to target-arm.next.
Thanks for this!
>
>
> thanks
> -- PMM
>
prev parent reply other threads:[~2020-04-27 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 7:33 [PATCH v2 0/5] target/arm: Restrict TCG cpus to TCG accel Philippe Mathieu-Daudé
2020-04-23 7:33 ` [PATCH v2 1/5] target/arm: Restric the Address Translate write operation " Philippe Mathieu-Daudé
2020-04-23 7:33 ` [PATCH v2 2/5] target/arm: Make cpu_register() available for other files Philippe Mathieu-Daudé
2020-04-23 7:33 ` [PATCH v2 3/5] target/arm/cpu: Use ARRAY_SIZE() to iterate over ARMCPUInfo[] Philippe Mathieu-Daudé
2020-04-23 7:33 ` [PATCH v2 4/5] target/arm/cpu: Update coding style to make checkpatch.pl happy Philippe Mathieu-Daudé
2020-04-23 7:33 ` [PATCH v2 5/5] target/arm: Restrict TCG cpus to TCG accel Philippe Mathieu-Daudé
2020-04-27 13:04 ` [PATCH v2 0/5] " Peter Maydell
2020-04-27 13:42 ` Philippe Mathieu-Daudé [this message]
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=25cbb189-19d2-5514-306f-51d176b61c39@redhat.com \
--to=philmd@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).