From: ira.weiny@intel.com
To: Ben Widawsky <ben.widawsky@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: Ira Weiny <ira.weiny@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/5] Map register blocks individually
Date: Fri, 21 May 2021 17:11:49 -0700 [thread overview]
Message-ID: <20210522001154.2680157-1-ira.weiny@intel.com> (raw)
From: Ira Weiny <ira.weiny@intel.com>
Changes for v2:
Incorporate feedback from Dan
Ensure memory blocks are individually reserved as well as mapped
Remove pci device management in favor of lower level device management
Drop version checking
Reorder patches
Update commit messages
Some hardware implementations mix component and device registers into the same
BAR and the driver stack is going to have independent mapping implementations
for those 2 cases. Furthermore, it will be nice to have finer grained mappings
should user space want to map some register blocks.
Unfortunately, the information for the register blocks is contained inside the
BARs themselves. Which means the BAR must be mapped, probed, and unmapped
prior to the registers being mapped individually.
The series starts by introducing the helper function
cxl_decode_register_block(). Then breaks out region reservation and register
mapping. Separates mapping the registers into a probe stage and mapping stage.
The probe stage creates list of register blocks which is then iterated to map
the individual register blocks.
Once mapping is performed in 2 steps the pci device management is removed and
the resource reservation can be done per register block as well.
Finally, the mapping the HDM decoder register block is added.
Ben Widawsky (1):
cxl: Add HDM decoder capbilities
Ira Weiny (4):
cxl/mem: Introduce cxl_decode_register_block()
cxl/mem: Reserve all device regions at once
cxl/mem: Map registers based on capabilities
cxl/mem: Reserve individual register block regions
drivers/cxl/core.c | 182 +++++++++++++++++++++++++++++++++++++++++----
drivers/cxl/cxl.h | 98 +++++++++++++++++++++---
drivers/cxl/pci.c | 168 ++++++++++++++++++++++++++++++++---------
drivers/cxl/pci.h | 1 +
4 files changed, 388 insertions(+), 61 deletions(-)
--
2.28.0.rc0.12.gb6a658bd00c9
next reply other threads:[~2021-05-22 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 0:11 ira.weiny [this message]
2021-05-22 0:11 ` [PATCH v2 1/5] cxl/mem: Introduce cxl_decode_register_block() ira.weiny
2021-05-25 9:53 ` Jonathan Cameron
2021-05-22 0:11 ` [PATCH v2 2/5] cxl/mem: Reserve all device regions at once ira.weiny
2021-05-25 9:54 ` Jonathan Cameron
2021-05-22 0:11 ` [PATCH v2 3/5] cxl/mem: Map registers based on capabilities ira.weiny
2021-05-25 9:52 ` Jonathan Cameron
2021-05-27 17:53 ` Ira Weiny
2021-05-22 0:11 ` [PATCH v2 4/5] cxl/mem: Reserve individual register block regions ira.weiny
2021-05-25 9:59 ` Jonathan Cameron
2021-05-22 0:11 ` [PATCH v2 5/5] cxl: Add HDM decoder capbilities ira.weiny
2021-05-25 14:28 ` Jonathan Cameron
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=20210522001154.2680157-1-ira.weiny@intel.com \
--to=ira.weiny@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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