[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250114193006.eqdbemtkmfkdapst@offworld>
Date: Tue, 14 Jan 2025 11:30:06 -0800
From: Davidlohr Bueso <dave@...olabs.net>
To: Dave Jiang <dave.jiang@...el.com>
Cc: dan.j.williams@...el.com, jonathan.cameron@...wei.com,
alison.schofield@...el.com, vishal.l.verma@...el.com,
ira.weiny@...el.com, fan.ni@...sung.com, a.manzanares@...sung.com,
sthanneeru.opensrc@...ron.com, emirakhur@...ron.com,
ajayjoshi@...ron.com, Ravis.OpenSrc@...ron.com,
sthanneeru@...ron.com, linux-cxl@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] cxl/pci: lockless background synchronous polling
On Tue, 14 Jan 2025, Dave Jiang wrote:
>On 10/21/24 8:18 PM, Davidlohr Bueso wrote:
>> +static inline bool cxl_is_background_cmd(u16 opcode)
>> +{
>> + switch (opcode) {
>> + case CXL_MBOX_OP_TRANSFER_FW:
>> + case CXL_MBOX_OP_ACTIVATE_FW:
>> + case CXL_MBOX_OP_SCAN_MEDIA:
>> + case CXL_MBOX_OP_SANITIZE:
>> + return true;
>> + default:
>> + return false;
>> + }
>> +}
>
>Should this information be pulled from the CEL entry? We should add the code to store the 'command effect' field when walking the CEL and store this information for each command. And then we can just check bit6 of the field rather than statically program that in the kernel.
Yeah, Will do.
Thanks,
Davidlohr
Powered by blists - more mailing lists