> -----Original Message-----
> From: Wathsala Wathawana Vithanage <wathsala.vithan...@arm.com>
> Sent: Friday, July 5, 2024 9:32 PM
> To: Pavan Nikhilesh Bhagavatula <pbhagavat...@marvell.com>;
> tho...@monjalon.net
> Cc: Tyler Retzlaff <roret...@linux.microsoft.com>; Ruifeng Wang
> <ruifeng.w...@arm.com>; dev@dpdk.org; nd <n...@arm.com>; Dhruv
> Tripathi <dhruv.tripa...@arm.com>; Honnappa Nagarahalli
> <honnappa.nagaraha...@arm.com>; Jack Bond-Preston <jack.bond-
> pres...@foss.arm.com>; Nick Connolly <nick.conno...@arm.com>; Vinod
> Krishna <vinod.kris...@arm.com>; david.march...@redhat.com; nd
> <n...@arm.com>; nd <n...@arm.com>
> Subject: [EXTERNAL] RE: [PATCH v2 2/2] eal: add Arm WFET in power
> management intrinsics
>
> > > We are using this flag to allow application to choose between WFE and
> non- > WFE code path. > The non-WFE path performs slightly better. > Is it
> correct if I assume that this flag is not used to indicate the availability
>
> >
> > We are using this flag to allow application to choose between WFE and non-
> > WFE code path.
> > The non-WFE path performs slightly better.
> >
>
> Is it correct if I assume that this flag is not used to indicate the
> availability
> of WFE instruction in any of your platforms?
> If so, then its usage is to choose between WFE and non-WFE implementations
> for performance reasons.
>
Yes, its purely for performance reasons.
>
>
