From: <sthanneeru.opensrc@micron.com>
To: <linux-cxl@vger.kernel.org>, <linux-mm@kvack.org>,
<sthanneeru.opensrc@micron.com>
Cc: <Jonathan.Cameron@huawei.com>, <dan.j.williams@intel.com>,
<john@jagalactic.com>, <emirakhur@micron.com>,
<ajayjoshi@micron.com>, <Ravis.OpenSrc@micron.com>,
<sthanneeru@micron.com>
Subject: [PATCH v2 0/2] Add log related mailbox commands
Date: Thu, 22 Feb 2024 22:53:48 +0530 [thread overview]
Message-ID: <20240222172350.512-1-sthanneeru.opensrc@micron.com> (raw)
From: Srinivasulu Thanneeru <sthanneeru.opensrc@micron.com>
Add support to expose following mailbox commands to userspace
for clearing and populating the Vendor debug log and
Component State dump log in certain scenarios,
allowing for the aggregation of results over time.
1. CXL r3.1 8.2.9.5.3 Get Log Capabilities.
2. CXL r3.1 8.2.9.5.4 Clear Log commands.
3. CXL r3.1 8.2.9.5.6 Get Supported Logs Sub-List.
---
Changes in v2:
- Add descption for exposing these mailbox log commands to ioctl.
- Create seperate patch for 'Clear log'.
- Restrict the ‘Clear log’ action to only apply to
Vendor debug logs and Component state dump logs.
- Rename get log sublist to get supported log sublist.
- Link to v1: https://lore.kernel.org/linux-mm/20240207103634.199-1-sthanneeru.opensrc@micron.com/
---
Srinivasulu Thanneeru (2):
cxl/mbox: Add Get Log Capabilities and Get Supported Logs Sub-List
commands
cxl/mbox: Add Clear Log mailbox command
drivers/cxl/core/mbox.c | 13 +++++++++++++
drivers/cxl/cxlmem.h | 6 ++++++
include/uapi/linux/cxl_mem.h | 3 +++
3 files changed, 22 insertions(+)
--
2.25.1
next reply other threads:[~2024-02-22 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 17:23 sthanneeru.opensrc [this message]
2024-02-22 17:23 ` [PATCH v2 1/2] cxl/mbox: Add Get Log Capabilities and Get Supported Logs Sub-List commands sthanneeru.opensrc
2024-02-22 17:23 ` [PATCH v2 2/2] cxl/mbox: Add Clear Log mailbox command sthanneeru.opensrc
2024-03-04 20:39 ` [PATCH v2 0/2] Add log related mailbox commands Dan Williams
2024-03-05 10:16 ` Srinivasulu Opensrc
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=20240222172350.512-1-sthanneeru.opensrc@micron.com \
--to=sthanneeru.opensrc@micron.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Ravis.OpenSrc@micron.com \
--cc=ajayjoshi@micron.com \
--cc=dan.j.williams@intel.com \
--cc=emirakhur@micron.com \
--cc=john@jagalactic.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sthanneeru@micron.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).