From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, kraxel@redhat.com, yoshinoyatoko@163.com
Cc: "Ni, Ray" <ray.ni@intel.com>
Subject: Re: [edk2-devel] question about cxl device enumeration in pci bus driver
Date: Thu, 26 Oct 2023 11:49:28 +0200 [thread overview]
Message-ID: <5df5f698-7f1d-98f3-e6a2-7b1a4c978528@redhat.com> (raw)
In-Reply-To: <uibv43vu4b46jsnsa2qfrjuojtiovg2bdhuwwc5osjbefotelj@3yxkjovyrbm6>
On 10/26/23 10:33, Gerd Hoffmann wrote:
> On Thu, Oct 26, 2023 at 10:36:35AM +0800, Yoshinoya wrote:
>
>> CXL Host Bridge / Root Port / Switch / Device enumeration / HDM Config, maybe could be integrated into pci drivers stack.
>
> Point being? Can or should the firmware do anything useful with
> the CXL hardware? If so, what exactly and why?
>
> Current state of affairs is that the PCI stack does the usual PCI
> initialization (enumerate, assign resources to PCI bars) and leaves
> everything else to the OS.
(I don't know what "HDM Config" stands for.)
The only utility for driving CXL devices from the firmware could be, AFAICT:
- booting off of such a device (or at least "supporting OS boot" in some
manner)
- using such a device for UEFI console purposes
Laszlo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#110085): https://edk2.groups.io/g/devel/message/110085
Mute This Topic: https://groups.io/mt/102173204/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-10-26 9:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 6:01 [edk2-devel] question about cxl device enumeration in pci bus driver Yoshinoya
2023-10-25 10:13 ` Ni, Ray
2023-10-26 2:36 ` Yoshinoya
2023-10-26 8:33 ` Gerd Hoffmann
2023-10-26 9:49 ` Laszlo Ersek [this message]
2023-10-26 13:35 ` Jonathan Cameron via groups.io
2023-10-27 1:26 ` Yoshinoya
[not found] ` <1791D2898E0C74CA.20272@groups.io>
2023-10-27 1:29 ` Yoshinoya
2023-10-27 5:49 ` Ni, Ray
2023-11-06 11:20 ` Yoshinoya
2023-11-07 21:54 ` Brian J. Johnson
2023-11-17 1:41 ` Yoshinoya
2023-11-07 11:31 ` [edk2-devel] Use dynamic pcd in smm mode Yoshinoya
2023-11-07 12:45 ` Laszlo Ersek
2023-11-09 6:03 ` Yoshinoya
2023-11-17 2:15 ` [edk2-devel] question about PrmPkg Yoshinoya
2023-11-17 8:42 ` Laszlo Ersek
2023-11-17 16:04 ` Michael Kubacki
2023-11-20 2:09 ` Yoshinoya
2023-11-20 13:58 ` Michael Kubacki
2024-02-27 10:06 ` [edk2-devel] Question about SMM code privilege switch Yoshinoya
2024-03-04 1:20 ` Yoshinoya
2024-05-23 2:07 ` [edk2-devel] What PTSS abbreviation means Yoshinoya
2024-02-05 9:49 ` [edk2-devel] sctpackage failed to be compile with new udk codebase Yoshinoya
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=5df5f698-7f1d-98f3-e6a2-7b1a4c978528@redhat.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