From: Alejandro Lucero Palau <alucerop@amd.com>
To: Huang Ying <ying.huang@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH 0/3] cxl: Preparation of type2 accelerators support
Date: Tue, 30 Jul 2024 07:10:25 +0100 [thread overview]
Message-ID: <b69304e8-d43c-940c-9ee0-d2345ef7b99d@amd.com> (raw)
In-Reply-To: <20240729084611.502889-1-ying.huang@intel.com>
Hi,
I'm a bit "surprised" by this patchset. As you rightly say in this cover
letter, there is a patchset under review, and I have not seen you
commenting there on the concerns stated in this cover letter.
I would say that is the first thing you should do, at least, to comment
there, suggest to do other way, pointing to other needed changes, and if
things do not go well for reaching an agreement, then a patchset like
this could make sense exposing another way.
Anyway, I think a CXL maintainer should say something about it, but
after 24hours, I had to say something.
About testing these changes, I wonder how did you proceed. If you have
used an emulated Type2 device, as I did with the first patchset version,
you should trigger some of the problems I found, what makes any Type2
initialization for getting a memdev and finally a cxl region to fail. In
other words, testing these changes can not be a partly initialised Type2
but a complete one. This does not mean a patch fixing a known and
obvious issue for supporting Type2 should not be approved if not tested,
since the Type2 support is not yet there, but mentioning testing makes
things confusing, at least for me.
On 7/29/24 09:46, Huang Ying wrote:
> There have been 2 series to add type 2 accelerators support in [1] and [2].
>
> [1] https://lore.kernel.org/linux-cxl/168592149709.1948938.8663425987110396027.stgit@dwillia2-xfh.jf.intel.com/
> [2] https://lore.kernel.org/linux-cxl/20240516081202.27023-1-alucerop@amd.com/
>
> Both provide relative complete support, but both are long too. To
> make it easier to review, some preparation of type2 accelerators
> support is implemented in this series. More complete support can be
> implemented based on it.
>
> This series has been tested with cxl_test via mocking a type2
> accelerator as in [1] above. Because more type2 accelerators support
> than that provided by this series is needed to simulate the device,
> the cxl_test patch isn't included in the series.
>
> Huang Ying (3):
> cxl: Set target type of root decoder based on CFMWS restrictions
> cxl: Set target type of region with that of root decoder
> cxl: Avoid to create dax regions for type2 accelerators
>
> drivers/cxl/acpi.c | 5 ++++-
> drivers/cxl/core/region.c | 11 ++++++++++-
> 2 files changed, 14 insertions(+), 2 deletions(-)
>
> Best Regards,
> Huang, Ying
next prev parent reply other threads:[~2024-07-30 6:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 8:46 Huang Ying
2024-07-29 8:46 ` [PATCH 1/3] cxl: Set target type of root decoder based on CFMWS restrictions Huang Ying
2024-08-01 1:22 ` Alison Schofield
2024-08-04 16:24 ` Jonathan Cameron
2024-08-06 1:28 ` Huang, Ying
2024-08-12 20:59 ` Fan Ni
2024-07-29 8:46 ` [PATCH 2/3] cxl: Set target type of region with that of root decoder Huang Ying
2024-08-01 1:35 ` Alison Schofield
2024-08-01 6:28 ` Huang, Ying
2024-08-04 16:31 ` Jonathan Cameron
2024-08-12 21:00 ` Fan Ni
2024-07-29 8:46 ` [PATCH 3/3] cxl: Avoid to create dax regions for type2 accelerators Huang Ying
2024-08-04 16:38 ` Jonathan Cameron
2024-08-06 5:52 ` Huang, Ying
2024-08-12 11:50 ` Alejandro Lucero Palau
2024-08-12 11:54 ` Alejandro Lucero Palau
2024-08-15 1:10 ` Huang, Ying
2024-07-30 6:10 ` Alejandro Lucero Palau [this message]
2024-07-30 6:34 ` [PATCH 0/3] cxl: Preparation of type2 accelerators support Huang, Ying
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=b69304e8-d43c-940c-9ee0-d2345ef7b99d@amd.com \
--to=alucerop@amd.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=ying.huang@intel.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
all inboxes | Powered by JetHome®