On Tue, 6 Sept 2022 at 19:01, Rebecca Cran <quic_rc...@quicinc.com> wrote: > > On 9/5/22 09:55, Ard Biesheuvel wrote: > > I think you've got things covered: I suggested RPi4 because it uses > > A72, and I seem to remember the issues I observed were either on A57 > > or A72 (which are quite similar). But between Juno and HoneyComb, I > > don't think the RPi4 data point is that useful. > > My only concern is about the call in MpServicesTest: > > WriteBackDataCacheRange ((VOID *)&ApFunction, 32); > > Obviously the '32' is a magic number and should be something based on the > size of ApFunction. > But I don't think there's a portable way to calculate what that value should > be. >
Why exactly do we need that call? I understand that some of the code needs to be clean to the PoC (on ARM) so that the AP can fetch instructions with the MMU and caches disabled. But the actual routine passed into the API is called with the MMU and caches on, right? -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#93293): https://edk2.groups.io/g/devel/message/93293 Mute This Topic: https://groups.io/mt/93329491/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-