Re: [PATCH v5 4/6] x86: control memset() and memcpy() inlining

Le 06/06/2025 à 11:21, Jan Beulich a écrit : > On 05.06.2025 19:34, Teddy Astie wrote: >> Le 05/06/2025 à 12:28, Jan Beulich a écrit : >>> Stop the compiler from inlining non-trivial memset() and memcpy() (for >>> memset() see e.g. map_vcpu_info() or kimage_load_segments() for >>> examples). This w

Re: [PATCH v5 4/6] x86: control memset() and memcpy() inlining

On 05.06.2025 19:34, Teddy Astie wrote: > Le 05/06/2025 à 12:28, Jan Beulich a écrit : >> Stop the compiler from inlining non-trivial memset() and memcpy() (for >> memset() see e.g. map_vcpu_info() or kimage_load_segments() for >> examples). This way we even keep the compiler from using REP STOSQ /

Re: [PATCH v5 4/6] x86: control memset() and memcpy() inlining

Le 05/06/2025 à 12:28, Jan Beulich a écrit : > Stop the compiler from inlining non-trivial memset() and memcpy() (for > memset() see e.g. map_vcpu_info() or kimage_load_segments() for > examples). This way we even keep the compiler from using REP STOSQ / > REP MOVSQ when we'd prefer REP STOSB / REP

[PATCH v5 4/6] x86: control memset() and memcpy() inlining

Stop the compiler from inlining non-trivial memset() and memcpy() (for memset() see e.g. map_vcpu_info() or kimage_load_segments() for examples). This way we even keep the compiler from using REP STOSQ / REP MOVSQ when we'd prefer REP STOSB / REP MOVSB (when ERMS is available). With gcc10 this yie