From: Srinivasulu Opensrc <sthanneeru.opensrc@micron.com>
To: Dan Williams <dan.j.williams@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>
Cc: "Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
"john@jagalactic.com" <john@jagalactic.com>,
Eishan Mirakhur <emirakhur@micron.com>,
Ajay Joshi <ajayjoshi@micron.com>,
Ravis OpenSrc <Ravis.OpenSrc@micron.com>,
Srinivasulu Thanneeru <sthanneeru@micron.com>
Subject: RE: [EXT] RE: [PATCH v3 0/2] Add log related mailbox commands
Date: Mon, 1 Apr 2024 06:03:07 +0000 [thread overview]
Message-ID: <38d0842e1f774c82b2f8f58f4d7ab07f@micron.com> (raw)
In-Reply-To: <66035c2e8ba17_770232948b@dwillia2-xfh.jf.intel.com.notmuch>
>-----Original Message-----
>From: Dan Williams <dan.j.williams@intel.com>
>Sent: Wednesday, March 27, 2024 5:07 AM
>To: Srinivasulu Opensrc <sthanneeru.opensrc@micron.com>; linux-
>cxl@vger.kernel.org
>Cc: Jonathan.Cameron@huawei.com; dan.j.williams@intel.com;
>john@jagalactic.com; Eishan Mirakhur <emirakhur@micron.com>; Ajay Joshi
><ajayjoshi@micron.com>; Ravis OpenSrc <Ravis.OpenSrc@micron.com>;
>Srinivasulu Thanneeru <sthanneeru@micron.com>
>Subject: [EXT] RE: [PATCH v3 0/2] Add log related mailbox commands
>
>CAUTION: EXTERNAL EMAIL. Do not click links or open attachments unless you
>recognize the sender and were expecting this message.
>
>
>sthanneeru.opensrc@ wrote:
>> From: Srinivasulu Thanneeru <sthanneeru.opensrc@micron.com>
>>
>> Add support to expose following mailbox commands to userspace
>> for clearing and populating the Vendor debug 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 v3:
>> - 'Component State Dump log' has several caveats for ioctl()
>> not being a suitable ABI as pointed in v2.(Dan Williams)
>> - Remove Component State Dump from Clear log filter.
>> - Implement a seperate patch(yet to do) to address issues as pointed in v2.
>
>Circling back to this question... I had overlooked the fact that in v3.1
>the "Request Abort Background Operation" command was added (8.2.9.1.5).
>With that the kernel can safely support background commands with
>indefinite residency. So as long as the device supports that command and
>advertises that Log populate requests can be cancelled then we can build
>a facility to cancel any user-submitted background commands when a
>kernel internal need for the background command slot arises.
I don't have the access to test "Request Abort Background Operation."
Previously, we posted RFC for default time for background operations.
https://lore.kernel.org/linux-mm/20240207105349.301-1-sthanneeru.opensrc@micron.com/
Could you please guide me on how to proceed with this current patch series?
next prev parent reply other threads:[~2024-04-01 6:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 7:12 [PATCH v3 0/2] Add log related mailbox commands sthanneeru.opensrc
2024-03-13 7:12 ` [PATCH v3 1/2] cxl/mbox: Add Get Log Capabilities and Get Supported Logs Sub-List commands sthanneeru.opensrc
2024-04-26 16:02 ` Jonathan Cameron
2024-03-13 7:12 ` [PATCH v3 2/2] cxl/mbox: Add Clear Log mailbox command sthanneeru.opensrc
2024-04-26 16:05 ` Jonathan Cameron
2024-03-26 23:37 ` [PATCH v3 0/2] Add log related mailbox commands Dan Williams
2024-04-01 6:03 ` Srinivasulu Opensrc [this message]
2024-04-05 17:31 ` [EXT] " Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2024-04-09 1:58 ajay.opensrc
2024-04-24 2:13 ` ajay.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=38d0842e1f774c82b2f8f58f4d7ab07f@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=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