From: alison.schofield@intel.com
To: Davidlohr Bueso <dave@stgolabs.net>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: linux-cxl@vger.kernel.org
Subject: [PATCH v2 0/2] cxl/region: Improve Soft Reserved resource handling
Date: Fri, 4 Aug 2023 12:31:38 -0700 [thread overview]
Message-ID: <cover.1691176651.git.alison.schofield@intel.com> (raw)
From: Alison Schofield <alison.schofield@intel.com>
Changes in v2:
- Rebase to 6.5-rc1
v1: https://lore.kernel.org/linux-cxl/cover.1687568084.git.alison.schofield@intel.com/
Make the cxl/region driver handle these 2 observed scenarios:
1) Soft reserved resources were observed as sometimes being the parent
and sometimes being the child of a region resource. Patch 1 clears up
that inconsistency.
2) Soft reserved resources were also observed as stranded after region
teardown, making the address space the region released unavailable for
reallocation. Patch 2 implements soft reserved resource removal.
Alison Schofield (2):
cxl/region: Try to add a region resource to a soft reserved parent
cxl/region: Remove a soft reserved resource at region teardown
drivers/cxl/core/region.c | 164 +++++++++++++++++++++++++++++++++++---
1 file changed, 153 insertions(+), 11 deletions(-)
base-commit: 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5
--
2.37.3
next reply other threads:[~2023-08-04 19:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 19:31 alison.schofield [this message]
2023-08-04 19:31 ` [PATCH v2 1/2] cxl/region: Try to add a region resource to a soft reserved parent alison.schofield
2023-08-07 14:24 ` Jonathan Cameron
2023-08-15 0:10 ` Alison Schofield
2023-08-09 23:22 ` Dave Jiang
2023-08-15 0:12 ` Alison Schofield
2023-08-04 19:31 ` [PATCH v2 2/2] cxl/region: Remove a soft reserved resource at region teardown alison.schofield
2023-08-09 23:34 ` Dave Jiang
2023-08-15 0:13 ` Alison Schofield
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=cover.1691176651.git.alison.schofield@intel.com \
--to=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.