From: Dave Jiang <dave.jiang@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
Cc: linux-cxl@vger.kernel.org, dan.j.williams@intel.com,
ira.weiny@intel.com, vishal.l.verma@intel.com,
alison.schofield@intel.com, rrichter@amd.com,
terry.bowman@amd.com
Subject: Re: [RFC PATCH 0/8] cxl: Introduce HDM decoder emulation from DVSEC range registers
Date: Mon, 19 Dec 2022 09:19:15 -0700 [thread overview]
Message-ID: <f2625c08-d6d5-2336-843d-13d906c0eccc@intel.com> (raw)
In-Reply-To: <20221219161223.000077f3@Huawei.com>
On 12/19/22 09:12, Jonathan Cameron wrote:
> On Wed, 30 Nov 2022 16:12:15 -0700
> Dave Jiang <dave.jiang@intel.com> wrote:
>
>> This series provides the emulation of HDM decoders from the programmed range
>> registers. From CXL 3.0 spec 8.1.3.8, there can be up to 2 ranges programmed.
>> Some device may not implement HDM decoder registers and some may not be
>> programmed by the BIOS. Under such scenarios, if one of more range registers
>> are programmed, then we can create an emulated HDM decoder per active range
>> indicated by the range registers. The emulated HDM decoders will show up as
>> locked and cannot be reprogrammed.
>>
>> Below is a table that indicates different scenarios the driver may encounter:
>>
>> rr: Range registers not programmed
>> hdm: HDM decoders not programmed
>> RR: Range registers programmed by BIOS
>> HDM: HDM decoders programmed by BIOS
>>
>> emulate HDM: Create HDM decoder software structs and use values from range registers.
>> keep HDM: Populate HDM decoder software structs with values in HDM decoder registers.
>>
>> rr RR rr hdm rr HDM RR hdm RR HDM
>> unsupported emulate HDM keep HDM keep HDM emulate HDM keep HDM
>>
>> This series is based on the current RCD work [1] that's going through upstream review.
>> For convenience, the kernel branch can be retrieved here [2].
>
> Just to check, why is this an RFC rather than a normal submission?
> Because of the unstable dependency?
That and also just making sure people are ok with the direction of the
series. I can remove the RFC for the next rev.
>
> At least at top level, it looks like a sensible approach.
>
>>
>> [1]: https://lore.kernel.org/linux-cxl/Y4ePZD776yXv2rG3@rric.localdomain/T/#t
>> [2]: https://git.kernel.org/pub/scm/linux/kernel/git/djiang/linux.git/log/?h=cxl-rch
>>
>> ---
>>
>> Dave Jiang (8):
>> cxl: break out range register decoding from cxl_hdm_decode_init()
>> cxl: export cxl_dvsec_rr_decode() to cxl_port
>> cxl: refactor cxl_hdm_decode_init()
>> cxl: emulate HDM decoder from DVSEC range registers
>> cxl: create emulated cxl_hdm for devices that do not have HDM decoders
>> cxl: create emulated decoders for devices without HDM decoders
>> cxl: suppress component register discovery failure warning for RCD
>> cxl: remove locked check for dvsec_range_allowed()
>>
>>
>> drivers/cxl/core/hdm.c | 115 +++++++++++++++++++++++---
>> drivers/cxl/core/pci.c | 179 +++++++++++++++++------------------------
>> drivers/cxl/cxl.h | 20 ++++-
>> drivers/cxl/cxlmem.h | 13 +--
>> drivers/cxl/cxlpci.h | 3 +-
>> drivers/cxl/pci.c | 2 +-
>> drivers/cxl/port.c | 19 +++--
>> 7 files changed, 215 insertions(+), 136 deletions(-)
>>
>> --
>>
>
prev parent reply other threads:[~2022-12-19 16:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 23:12 [RFC PATCH 0/8] cxl: Introduce HDM decoder emulation from DVSEC range registers Dave Jiang
2022-11-30 23:12 ` [RFC PATCH 1/8] cxl: break out range register decoding from cxl_hdm_decode_init() Dave Jiang
2022-12-19 15:59 ` Jonathan Cameron
2023-01-03 21:32 ` Dave Jiang
2022-11-30 23:12 ` [RFC PATCH 2/8] cxl: export cxl_dvsec_rr_decode() to cxl_port Dave Jiang
2022-12-19 16:11 ` Jonathan Cameron
2022-11-30 23:12 ` [RFC PATCH 3/8] cxl: refactor cxl_hdm_decode_init() Dave Jiang
2022-12-19 16:19 ` Jonathan Cameron
2022-11-30 23:12 ` [RFC PATCH 4/8] cxl: emulate HDM decoder from DVSEC range registers Dave Jiang
2022-12-19 16:42 ` Jonathan Cameron
2023-01-03 23:20 ` Dave Jiang
2023-01-04 16:07 ` Dave Jiang
2023-01-05 10:51 ` Jonathan Cameron
2022-11-30 23:12 ` [RFC PATCH 5/8] cxl: create emulated cxl_hdm for devices that do not have HDM decoders Dave Jiang
2022-12-19 16:52 ` Jonathan Cameron
2022-11-30 23:12 ` [RFC PATCH 6/8] cxl: create emulated decoders for devices without " Dave Jiang
2022-12-19 17:00 ` Jonathan Cameron
2022-11-30 23:12 ` [RFC PATCH 7/8] cxl: suppress component register discovery failure warning for RCD Dave Jiang
2022-12-19 17:35 ` Jonathan Cameron
2022-11-30 23:13 ` [RFC PATCH 8/8] cxl: remove locked check for dvsec_range_allowed() Dave Jiang
2022-12-19 16:12 ` [RFC PATCH 0/8] cxl: Introduce HDM decoder emulation from DVSEC range registers Jonathan Cameron
2022-12-19 16:19 ` Dave Jiang [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=f2625c08-d6d5-2336-843d-13d906c0eccc@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=rrichter@amd.com \
--cc=terry.bowman@amd.com \
--cc=vishal.l.verma@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