qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: meson, NEED_CPU_H, CONFIG_TCG and tests/


From: Thomas Huth
Subject: Re: meson, NEED_CPU_H, CONFIG_TCG and tests/
Date: Fri, 19 Feb 2021 14:30:20 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0

On 19/02/2021 14.04, Claudio Fontana wrote:
Hi Paolo,

currently we have use of CONFIG_TCG in tests/,

but is that variable available at all in there?

I have to adapt some qemu/tests/qtest/* to work also without tcg for ARM,

but I think I am not seeing CONFIG_TCG filtering through, and I wonder whether all the 
checks in there are actually "wrong".

Looking at meson.build it would seem to me that only stuff in target/ would be 
able to see CONFIG_TCG,
as a result of

foreach target : target_dirs
   config_target = config_target_mak[target]
   target_name = config_target['TARGET_NAME']
   arch = config_target['TARGET_BASE_ARCH']
   arch_srcs = [config_target_h[target]]
   arch_deps = []
   c_args = ['-DNEED_CPU_H',
             '-DCONFIG_TARGET="@0@-config-target.h"'.format(target),
             '-DCONFIG_DEVICES="@0@-config-devices.h"'.format(target)]

But how could tests see this?

The test are generic, not target-specific code, so they can not see things like NEED_CPU_H, of course.

But CONFIG_TCG seems to be defined in config-host.h, so you should be able to use that define, shouldn't you?

 Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]