From: Dave Jiang <dave.jiang@intel.com>
To: Jeongtae Park <jtp.park@samsung.com>, <linux-cxl@vger.kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"Ben Widawsky" <bwidawsk@kernel.org>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Davidlohr Bueso <dave@stgolabs.net>, Fan Ni <fan.ni@samsung.com>,
Kyungsan Kim <ks0204.kim@samsung.com>,
Wonjae Lee <wj28.lee@samsung.com>,
Hojin Nam <hj96.nam@samsung.com>,
Junhyeok Im <junhyeok.im@samsung.com>,
Jehoon Park <jehoon.park@samsung.com>,
"Jeongtae Park" <jeongtae.park@gmail.com>
Subject: Re: [RFC PATCH 0/3] cxl: Fix background operation handling
Date: Mon, 25 Sep 2023 15:56:54 -0700 [thread overview]
Message-ID: <5476c53d-d49e-61ba-5f78-abefc5f8c7cf@intel.com> (raw)
In-Reply-To: <20230922130528.3475445-1-jtp.park@samsung.com>
On 9/22/23 06:05, Jeongtae Park wrote:
> Hello,
>
> We are currently trying to add background commands like
> fw-related and sanitize operation. However, as we modified
> the code, we found that there was a lot of duplication of
> code, so we would like to modify the existing background
> command handling a little bit. We want to make the most of
> the existing background command handling so that we can
> easily add other background commands in the future.
>
> The first patch modifies the existing sanitize operation
> handling to allow other background commands to be used
> with it, and the second patch modifies sanitize to work
> with the modified code. Finally, the third patch adds a
> sysfs file related to the background operation.
> This sysfs entry is select/poll capable from userspace
> to notify upon completion of a background operation.
>
> Thanks,
> /jtpark
Hi Jeongtae,
For the next version of the series you send out, can you please make sure the series is threaded? Currently all your series are coming as individual mails. Thanks!
>
> Jeongtae Park (3):
> cxl: Modify background cmd handling for the others
> cxl/mbox: Update sanitize opcode support
> cxl/memdev: Add background command sysfs file
>
> Documentation/ABI/testing/sysfs-bus-cxl | 10 ++++
> drivers/cxl/core/mbox.c | 5 +-
> drivers/cxl/core/memdev.c | 71 +++++++++++++++++++++++--
> drivers/cxl/cxlmem.h | 33 ++++++++++--
> drivers/cxl/pci.c | 65 +++++++++++-----------
> 5 files changed, 141 insertions(+), 43 deletions(-)
>
>
> base-commit: fe77cc2e5a6a7c85f5c6ef8a39d7694ffc7f41c9
next prev parent reply other threads:[~2023-09-25 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230922130253epcas2p3112ca71e8a1dcf42967543063322df1e@epcas2p3.samsung.com>
2023-09-22 13:05 ` [RFC PATCH 0/3] cxl: Fix background operation handling Jeongtae Park
2023-09-25 22:56 ` Dave Jiang [this message]
2023-10-05 8:24 ` Jeongtae Park
2023-09-28 1:02 ` Davidlohr Bueso
2023-10-05 9:06 ` Jeongtae Park
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=5476c53d-d49e-61ba-5f78-abefc5f8c7cf@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=bwidawsk@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=hj96.nam@samsung.com \
--cc=jehoon.park@samsung.com \
--cc=jeongtae.park@gmail.com \
--cc=jonathan.cameron@huawei.com \
--cc=jtp.park@samsung.com \
--cc=junhyeok.im@samsung.com \
--cc=ks0204.kim@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=wj28.lee@samsung.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