Linux CXL
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Jonathan.Cameron@Huawei.com" <Jonathan.Cameron@Huawei.com>
Cc: "Jiang, Dave" <dave.jiang@intel.com>,
	"Schofield, Alison" <alison.schofield@intel.com>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"Weiny, Ira" <ira.weiny@intel.com>,
	"bwidawsk@kernel.org" <bwidawsk@kernel.org>,
	"Weight, Russell H" <russell.h.weight@intel.com>,
	"dave@stgolabs.net" <dave@stgolabs.net>
Subject: Re: [PATCH v3 1/4] cxl: add a firmware update mechanism using the sysfs firmware loader
Date: Wed, 14 Jun 2023 17:15:29 +0000	[thread overview]
Message-ID: <26a13b81674655e7c2b5f7c53c98ba321acfc358.camel@intel.com> (raw)
In-Reply-To: <20230614151417.00002f46@Huawei.com>

On Wed, 2023-06-14 at 15:14 +0100, Jonathan Cameron wrote:
> On Mon, 12 Jun 2023 00:55:56 -0600
> Vishal Verma <vishal.l.verma@intel.com> wrote:
> 
> > The sysfs based firmware loader mechanism was created to easily allow
> > userspace to upload firmware images to FPGA cards. This also happens to
> > be pretty suitable to create a user-initiated but kernel-controlled
> > firmware update mechanism for CXL devices, using the CXL specified
> > mailbox commands.
> > 
> > Since firmware update commands can be long-running, and can be processed
> > in the background by the endpoint device, it is desirable to have the
> > ability to chunk the firmware transfer down to smaller pieces, so that
> > one operation does not monopolize the mailbox, locking out any other
> > long running background commands entirely - e.g. security commands like
> > 'sanitize' or poison scanning operations.
> > 
> > The firmware loader mechanism allows a natural way to perform this
> > chunking, as after each mailbox command, that is restricted to the
> > maximum mailbox payload size, the cxl memdev driver relinquishes control
> > back to the fw_loader system and awaits the next chunk of data to
> > transfer. This opens opportunities for other background commands to
> > access the mailbox and send their own slices of background commands.
> > 
> > Add the necessary helpers and state tracking to be able to perform the
> > 'Get FW Info', 'Transfer FW', and 'Activate FW' mailbox commands as
> > described in the CXL spec. Wire these up to the firmware loader
> > callbacks, and register with that system to create the memX/firmware/
> > sysfs ABI.
> > 
> > Cc: Davidlohr Bueso <dave@stgolabs.net>
> > Cc: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
> > Cc: Russ Weight <russell.h.weight@intel.com>
> > Cc: Alison Schofield <alison.schofield@intel.com>
> > Cc: Ira Weiny <ira.weiny@intel.com>
> > Cc: Dave Jiang <dave.jiang@intel.com>
> > Cc: Ben Widawsky <bwidawsk@kernel.org>
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> 
> One issue and one trivial comment inline.
> With those fixed up and subject to the fact I haven't looked at the firmware
> class before...
> 
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>

Thanks for the review Jonathan - fixed these for v4!



  reply	other threads:[~2023-06-14 17:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  6:55 [PATCH v3 0/4] cxl: Add a firmware update mechanism and cxl_test emulation Vishal Verma
2023-06-12  6:55 ` [PATCH v3 1/4] cxl: add a firmware update mechanism using the sysfs firmware loader Vishal Verma
2023-06-13 18:34   ` Dave Jiang
2023-06-14 14:14   ` Jonathan Cameron
2023-06-14 17:15     ` Verma, Vishal L [this message]
2023-06-12  6:55 ` [PATCH v3 2/4] tools/testing/cxl: Fix command effects for inject/clear poison Vishal Verma
2023-06-13 18:37   ` Dave Jiang
2023-06-12  6:55 ` [PATCH v3 3/4] tools/testing/cxl: Use named effects for the Command Effect Log Vishal Verma
2023-06-13 18:38   ` Dave Jiang
2023-06-12  6:55 ` [PATCH v3 4/4] tools/testing/cxl: add firmware update emulation to CXL memdevs Vishal Verma
2023-06-13 18:41   ` Dave Jiang

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=26a13b81674655e7c2b5f7c53c98ba321acfc358.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=Jonathan.Cameron@Huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=bwidawsk@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=russell.h.weight@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox