From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, quic_llindhol@quicinc.com
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>,
Pierre Gondois <pierre.gondois@arm.com>,
"Li, Yi1" <yi1.li@intel.com>,
"Lu, Xiaoyu1" <xiaoyu1.lu@intel.com>,
"Jiang, Guomin" <guomin.jiang@intel.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Sami Mujawar <sami.mujawar@arm.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [edk2-devel] [PATCH v5 2/6] CryptoPkg/CryptoPkg.ci.yaml: Allow dependency upon ArmPkg
Date: Tue, 21 Nov 2023 11:02:56 -0500 [thread overview]
Message-ID: <CAMj1kXGf8xaY=Me5VA6xjTiRX3jzjNqrpRWLBg8-Oidmb6oOJA@mail.gmail.com> (raw)
In-Reply-To: <ZVzS/1aoRDDDmYya@qc-i7.hemma.eciton.net>
On Tue, 21 Nov 2023 at 10:55, Leif Lindholm <quic_llindhol@quicinc.com> wrote:
>
> On Tue, Nov 21, 2023 at 14:46:05 +0000, Yao, Jiewen wrote:
> > This Bugzilla is filed in 2022-10-26. Now it is 2023-11-21.
>
> Oh, I'm sure I voiced the same opinion for many years before someone
> (rightly) told me to go gile that bugzilla.
>
> > I agree with you that it is a big task. May I know what is the plan?
> > E.g. who is working on that? When do you expect it will be done?
>
> On my list of "big items" to deal with, this comes after github PR
> migration and line-ending conversion.
>
> > According to the dependency rule, what we need is only *interface*
> > definition, but not *implementation*.
> > That means the really requirement here is to move *interface* from
> > ArmPkg to MdePkg, you can still keep the library implementation in
> > ArmPkg. (It is just a subset of this Bugzilla)
>
> That ... is an option I had not previously considered.
> Long-term we would still like to smash ArmLib into BaseLib, but if
> MdePkg maintainers would be OK with moving ArmLib.h into MdePkg...
>
> > Also, I don’t think CPUID check really matters here - since it is only implementation.
> > As long as, you have interface in MdePkg, then your INF can declare that interface.
> > You can still put real implementation in ArmPkg - no requirement to move.
> > That benefit is that you don’t need to add ArmPkg dependency in yaml.
>
> I can spin up a patch for that to get merged shortly after stable tag
> to give plenty of time to catch any issues that may arise from moving
> such a fundamental file. (These would likely be bugs, but
> nevertheless...)
>
This sounds like a reasonable solution to me for the short term.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111556): https://edk2.groups.io/g/devel/message/111556
Mute This Topic: https://groups.io/mt/102725178/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-11-21 16:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 8:47 [edk2-devel] [PATCH v5 0/6] CryptoPkg: Enable Openssl native instruction support for AARCH64 PierreGondois
2023-11-21 8:47 ` [edk2-devel] [PATCH v5 1/6] ArmPkg/ArmLib: Add macros/helper functions around AA64Isar0 register PierreGondois
2023-11-21 8:47 ` [edk2-devel] [PATCH v5 2/6] CryptoPkg/CryptoPkg.ci.yaml: Allow dependency upon ArmPkg PierreGondois
2023-11-21 11:27 ` Yao, Jiewen
2023-11-21 12:59 ` PierreGondois
2023-11-21 13:41 ` Yao, Jiewen
2023-11-21 14:26 ` Leif Lindholm
2023-11-21 14:46 ` Yao, Jiewen
2023-11-21 15:55 ` Leif Lindholm
2023-11-21 16:02 ` Ard Biesheuvel [this message]
2023-11-21 16:26 ` Yao, Jiewen
2023-11-21 8:47 ` [edk2-devel] [PATCH v5 3/6] CryptoPkg/OpensslLib: Add native instruction support for AARCH64 PierreGondois
2023-11-21 8:47 ` [edk2-devel] [PATCH v5 4/6] CryptoPkg/OpensslLib: Generate files for AARCH64 native support PierreGondois
2023-11-21 8:47 ` [edk2-devel] [PATCH v5 5/6] CryptoPkg/OpensslLib: Add AArch64Cap for arch specific hooks PierreGondois
2023-11-21 8:47 ` [edk2-devel] [PATCH v5 6/6] CryptoPkg: Enable Openssl Accel builds for AARCH64 PierreGondois
2023-11-21 16:22 ` [edk2-devel] [PATCH v5 0/6] CryptoPkg: Enable Openssl native instruction support " Ard Biesheuvel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMj1kXGf8xaY=Me5VA6xjTiRX3jzjNqrpRWLBg8-Oidmb6oOJA@mail.gmail.com' \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox