From: Dan Williams <dan.j.williams@intel.com>
To: Alejandro Lucero Palau <alucerop@amd.com>,
Dan Williams <dan.j.williams@intel.com>,
<linux-cxl@vger.kernel.org>
Cc: <dave.jiang@intel.com>, <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH] Documentation: CXL Maturity Map
Date: Wed, 3 Jul 2024 16:26:35 -0700 [thread overview]
Message-ID: <6685de2b88d78_4fe7f2944f@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <09ea58f3-b54f-2bc2-bf6f-9a05e9db361d@amd.com>
Alejandro Lucero Palau wrote:
> Apologies for the late answer.
>
>
> RAS is covered but what about how CXL/PCI devices are handled after a
> slot reset?
>
> I did expose my concern in that area when discussing the Type2 support
> patchset, and if I'm not wrong this is not properly supported: nothing
> for device detachment which should occur before the slot reset, nothing
> for resume function after the slot reset. This is obviously more
> important for Type2 devices and maybe not required for Type3.
Circling back to this as I go to post v2...
I think those type-2 RAS aspects are important, but it is not clear that
they are a concern of the CXL core. Endpoint drivers are enabled to get
pre and post reset notification via their registered 'struct
pci_error_handlers' operations. This maturity list is more targeted at
the CXL core infrastructure capabilities and type-2 drivers are going to
have their own localized maturity level.
I do need to go look more closely at your RAS assertions on that set. I
had otherwise been waiting a new posting with the sfc integration.
prev parent reply other threads:[~2024-07-03 23:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20240617165830uscas1p12e867fc6ad52fa7cfa32955f3150dd6f@uscas1p1.samsung.com>
2024-05-25 0:53 ` [PATCH] Documentation: CXL Maturity Map Dan Williams
2024-06-06 3:23 ` Alison Schofield
2024-06-17 22:25 ` Davidlohr Bueso
2024-06-17 22:38 ` Dan Williams
2024-06-06 14:40 ` Jonathan Cameron
2024-06-17 22:50 ` Dan Williams
2024-06-20 17:45 ` Jonathan Cameron
2024-06-17 16:58 ` Adam Manzanares
2024-06-17 22:54 ` Dan Williams
2024-06-27 17:52 ` Adam Manzanares
2024-06-19 16:02 ` Alejandro Lucero Palau
2024-07-03 23:26 ` Dan Williams [this message]
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-all 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=6685de2b88d78_4fe7f2944f@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alucerop@amd.com \
--cc=dave.jiang@intel.com \
--cc=linux-cxl@vger.kernel.org \
/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