Re: [PATCH v2 2/5] target/arm/kvm: Make uncalled stubs explicitly unreachable

On Wed, Aug 12, 2020 at 12:16:43PM +0200, Auger Eric wrote: > Hi Drew, > > On 8/5/20 11:16 AM, Andrew Jones wrote: > > When we compile without KVM support !defined(CONFIG_KVM) we generate > > stubs for functions that the linker will still encounter. Sometimes > > these stubs can be executed

Re: [PATCH v2 2/5] target/arm/kvm: Make uncalled stubs explicitly unreachable

Hi Drew, On 8/5/20 11:16 AM, Andrew Jones wrote: > When we compile without KVM support !defined(CONFIG_KVM) we generate > stubs for functions that the linker will still encounter. Sometimes > these stubs can be executed safely and are placed in paths where they > get executed with or without KVM.

[PATCH v2 2/5] target/arm/kvm: Make uncalled stubs explicitly unreachable

When we compile without KVM support !defined(CONFIG_KVM) we generate stubs for functions that the linker will still encounter. Sometimes these stubs can be executed safely and are placed in paths where they get executed with or without KVM. Other functions should never be called without KVM. Those