netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alejandro Lucero Palau <alucerop@amd.com>
To: Alison Schofield <alison.schofield@intel.com>,
	alejandro.lucero-palau@amd.com
Cc: linux-cxl@vger.kernel.org, netdev@vger.kernel.org,
	dan.j.williams@intel.com, edward.cree@amd.com,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, dave.jiang@intel.com
Subject: Re: [PATCH v14 00/22] Type2 device basic support
Date: Thu, 8 May 2025 15:55:10 +0100	[thread overview]
Message-ID: <1bfb63d8-d16e-4779-b23a-8fbf34342ead@amd.com> (raw)
In-Reply-To: <aBwQGNx4uK0f9aCS@aschofie-mobl2.lan>

>
> Hi Alejandro,


Hi Allison,


Thank you for your reviews.


My replies below.


>
> I commented on a few things in the individual patches and had a couple
> of series wide comments that I'll share here.
>
> I came into this set with the expectation that it was a model for Type 2
> device support and I expect it is, but without the summary I was hoping
> for. As I review the patches I can pick this stuff out, but would have
> appreciated each patch commit message stating its purpose more clearly.
> We get so use to reading this as a patchset, ie a short story, but once
> this set merges, the patches all must stand on their own, so including as
> much story in each commit message is needed. At the minimum, every patch to
> drivers/cxl/ in this set should explicitly state that this is being done in
> support of, or in preparation for, Type 2.


I understand and fully agree. I'll be sure about all patches clearly 
linked to the type2 support.


> I sorted the set into 3 buckets as I read.
>
> 1)These are the changes made to existing paths in the CXL driver to enable
>    Type 2. These change the existing driver behavior.
>
> 2)These are the patches that add new functionality to the CXL driver,
>    that is only exported for use by the Type 2 driver. These new
>    functions are not used in drivers/cxl/.
>
> 3)The sfx driver code. (which I glanced at)
>
> I'm wondering if bucket #2 is something to be documented in the
> Documentation/driver-api/cxl/.


It makes sense. But if I may say this, I think this could wait for a 
following-up as a Type2 driver guide including some of the problems I'm 
struggling with right now, not about the patchset itself, but some 
assumptions about what the BIOS does. Also, as the cover letter 
mentions, this is "basic support", so a first step which will have more 
steps following soon hopefully paving the proper road for this CXL 
functionality.


>
> Other general comments:
>
> - Consider each drivers/cxl/ function exported for use in sfc for a kernel
>    doc comment if not already present.


OK.


>
> - Some of the added Kernel-doc headers are missing  a Return: field


I'll check it.


>
> - "Printing numbers in parentheses (%d) adds no value and should be avoided."
>     See: Documentation/process/coding-style.rst.


I'll fix those.


>
> - Follow cxl conventions. Commit messages in drivers/cxl begine w uppercase


I'll fix those as well.


Thank you!


>
>
> -- Alison
>

      reply	other threads:[~2025-05-08 14:55 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-17 21:29 [PATCH v14 00/22] Type2 device basic support alejandro.lucero-palau
2025-04-17 21:29 ` [PATCH v14 01/22] cxl: add type2 " alejandro.lucero-palau
2025-05-07 14:37   ` Jonathan Cameron
2025-05-08 15:47     ` Alejandro Lucero Palau
2025-05-08  0:25   ` Alison Schofield
2025-05-08 10:19     ` Alejandro Lucero Palau
2025-04-17 21:29 ` [PATCH v14 02/22] sfc: add cxl support alejandro.lucero-palau
2025-05-07 14:42   ` Jonathan Cameron
2025-05-08 15:05     ` Edward Cree
2025-05-08  0:33   ` Alison Schofield
2025-05-08 12:41     ` Alejandro Lucero Palau
2025-05-08 17:12       ` Alison Schofield
2025-05-08 17:17         ` Alejandro Lucero Palau
2025-04-17 21:29 ` [PATCH v14 03/22] cxl: move pci generic code alejandro.lucero-palau
2025-05-08  0:36   ` Alison Schofield
2025-05-08 12:45     ` Alejandro Lucero Palau
2025-05-08 17:20       ` Alison Schofield
2025-05-08 17:20       ` Dave Jiang
2025-04-17 21:29 ` [PATCH v14 04/22] cxl: move register/capability check to driver alejandro.lucero-palau
2025-05-08  0:55   ` Alison Schofield
2025-05-08 13:13     ` Alejandro Lucero Palau
2025-04-17 21:29 ` [PATCH v14 05/22] cxl: add function for type2 cxl regs setup alejandro.lucero-palau
2025-05-07 14:47   ` Jonathan Cameron
2025-04-17 21:29 ` [PATCH v14 06/22] sfc: make regs setup with checking and set media ready alejandro.lucero-palau
2025-04-17 21:29 ` [PATCH v14 07/22] cxl: support dpa initialization without a mailbox alejandro.lucero-palau
2025-04-17 21:29 ` [PATCH v14 08/22] sfc: initialize dpa alejandro.lucero-palau
2025-05-07 14:49   ` Jonathan Cameron
2025-05-08 15:06   ` Edward Cree
2025-04-17 21:29 ` [PATCH v14 09/22] cxl: prepare memdev creation for type2 alejandro.lucero-palau
2025-05-08  1:06   ` Alison Schofield
2025-05-12 10:38     ` Alejandro Lucero Palau
2025-04-17 21:29 ` [PATCH v14 10/22] sfc: create type2 cxl memdev alejandro.lucero-palau
2025-04-17 21:29 ` [PATCH v14 11/22] cxl: define a driver interface for HPA free space enumeration alejandro.lucero-palau
2025-04-22 16:22   ` Jonathan Cameron
2025-04-28  8:00     ` Alejandro Lucero Palau
2025-05-08  1:13   ` Alison Schofield
2025-05-08 14:09     ` Alejandro Lucero Palau
2025-05-08 17:31       ` Alison Schofield
2025-04-17 21:29 ` [PATCH v14 12/22] sfc: obtain root decoder with enough HPA free space alejandro.lucero-palau
2025-04-17 21:29 ` [PATCH v14 13/22] cxl: define a driver interface for DPA allocation alejandro.lucero-palau
2025-05-08 18:02   ` Alison Schofield
2025-05-09  7:40     ` Alejandro Lucero Palau
2025-04-17 21:29 ` [PATCH v14 14/22] sfc: get endpoint decoder alejandro.lucero-palau
2025-04-17 21:29 ` [PATCH v14 15/22] cxl: make region type based on endpoint type alejandro.lucero-palau
2025-04-17 21:29 ` [PATCH v14 16/22] cxl/region: factor out interleave ways setup alejandro.lucero-palau
2025-05-08  1:16   ` Alison Schofield
2025-05-08 14:32     ` Alejandro Lucero Palau
2025-04-17 21:29 ` [PATCH v14 17/22] cxl/region: factor out interleave granularity setup alejandro.lucero-palau
2025-04-17 21:29 ` [PATCH v14 18/22] cxl: allow region creation by type2 drivers alejandro.lucero-palau
2025-04-17 21:29 ` [PATCH v14 19/22] cxl: add region flag for precluding a device memory to be used for dax alejandro.lucero-palau
2025-05-08 18:20   ` Alison Schofield
2025-05-09  8:16     ` Alejandro Lucero Palau
2025-04-17 21:29 ` [PATCH v14 20/22] sfc: create cxl region alejandro.lucero-palau
2025-04-17 21:29 ` [PATCH v14 21/22] cxl: add function for obtaining region range alejandro.lucero-palau
2025-05-08  1:24   ` Alison Schofield
2025-05-08 14:32     ` Alejandro Lucero Palau
2025-04-17 21:29 ` [PATCH v14 22/22] sfc: support pio mapping based on cxl alejandro.lucero-palau
2025-05-07 15:11 ` [PATCH v14 00/22] Type2 device basic support Jonathan Cameron
2025-05-08  1:59 ` Alison Schofield
2025-05-08 14:55   ` Alejandro Lucero Palau [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=1bfb63d8-d16e-4779-b23a-8fbf34342ead@amd.com \
    --to=alucerop@amd.com \
    --cc=alejandro.lucero-palau@amd.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=edward.cree@amd.com \
    --cc=kuba@kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).