From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by mx.groups.io with SMTP id smtpd.web11.2402.1662486848592727872 for ; Tue, 06 Sep 2022 10:54:08 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=LlX9QGYY; spf=pass (domain: kernel.org, ip: 139.178.84.217, mailfrom: ardb@kernel.org) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id B557961518 for ; Tue, 6 Sep 2022 17:54:07 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 24398C433C1 for ; Tue, 6 Sep 2022 17:54:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1662486847; bh=Nulf4Bs4vhH5LV+P1wZvN905YUUyVM2dGBGhRcC8/5A=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=LlX9QGYYmHrEVIAKVKJqqlWiS9DoKjcJ+NDTyLQwjfclzRUZq+5p3iEWrfCcJa650 M6eF36WnGxRgbiiF9NOkdhNv4OYpfN6ca4mLcUcR2E5BLAAyWWmSdTCGn6z0B/4vKB HD32Ss9icMIPe17w1dsjlxuQJE6JTolXMnrHbz6H7P1K1gY7B083Dxb0PGgwL2DTJV Try97QZBTw5cpw/zG4r0ZTkliJdIN/wCB9V9cCT1cLehDkE7AxsYzJzfa7va7oXpgF hMRhNG1Z9jjXIfqwJ9/NE3byw3kJGuHGPQ69toUIqHPs2RbnFqD1Fwwb9hjO4fR5Np Ij/BoPoZBa8Jw== Received: by mail-lf1-f42.google.com with SMTP id f11so4538913lfa.6 for ; Tue, 06 Sep 2022 10:54:07 -0700 (PDT) X-Gm-Message-State: ACgBeo0SfdLsAjYs0X+A5hkDWKaU9SH23XWoQvZfEXP6VOySBMh2RmUv dZhc0dU6HFshfEgQYegBmVUSd7z7/fVdw3IfTvI= X-Google-Smtp-Source: AA6agR5wEDD5Cj899m3jDf7Jm/6eypHxudeHPrpFLz13uvgwumIMG1e67hKYoZJQiSi9GTAEKL+VmwkOYd9CbDQ3Yrw= X-Received: by 2002:a05:6512:4024:b0:497:4db:6ad0 with SMTP id br36-20020a056512402400b0049704db6ad0mr1837035lfb.637.1662486845127; Tue, 06 Sep 2022 10:54:05 -0700 (PDT) MIME-Version: 1.0 References: <20220829155955.3767-1-rebecca@quicinc.com> <1b826591-5abc-ef17-c47a-22918318eb20@quicinc.com> In-Reply-To: From: "Ard Biesheuvel" Date: Tue, 6 Sep 2022 19:53:53 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [edk2-devel] [PATCH 0/2] Add support EFI_MP_SERVICES_PROTOCOL on AARCH64 To: devel@edk2.groups.io, quic_rcran@quicinc.com Cc: Leif Lindholm , Ard Biesheuvel , Sami Mujawar , Jian J Wang , Liming Gao Content-Type: text/plain; charset="UTF-8" On Tue, 6 Sept 2022 at 19:01, Rebecca Cran 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?