On Tue, 2025-08-12 at 09:32 +0200, Krzysztof Kozlowski wrote:

External email : Please do not click links or open attachments until
you have verified the sender or the content.


On 12/08/2025 09:04, Liju-clr Chen (陳麗如) wrote:

quoted

we have guarded the gzvm driver with the CONFIG_MTK_GZVM Kconfig
option. This ensures the code is only compiled and active on
selected
platforms, and will not affect other users or systems.

That is simply not true, since it will be enabled in defconfig in
EVERY
platform. Look up approach of single kernel and single image.

Best regards,
Krzysztof

Hi Krzysztof,

Thank you for explaining why the Kconfig option cannot prevent
polluting all systems due to the single kernel approach.

As you mentioned, using Kconfig cannot solve the issue of polluting all
systems, so probing directly is not recommended.

The other method I know is to use a DT node, but the community does not
accept DT nodes without real hardware resources.

Currently, these are the only two methods I am aware of. I will
continue to look for other possible solutions, and any suggestions
would be appreciated.

Thank you again for your feedback.

Best Regards,
Liju-clr Chen