From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: <alison.schofield@intel.com>
Cc: Ben Widawsky <ben.widawsky@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v3 3/9] cxl/mbox: Move build of user mailbox cmd to a helper function
Date: Fri, 25 Mar 2022 10:43:48 +0000 [thread overview]
Message-ID: <20220325104348.00002709@huawei.com> (raw)
In-Reply-To: <20220324011126.1144504-4-alison.schofield@intel.com>
On Wed, 23 Mar 2022 18:11:20 -0700
alison.schofield@intel.com wrote:
> From: Alison Schofield <alison.schofield@intel.com>
>
> In preparation for moving the construction of a mailbox command
> to the validation path, extract the work into a helper function.
>
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
Some suggestions for possible improvements to code organization now
possible because everything is in one place.
Otherwise looks good to me.
Jonathan
> ---
> drivers/cxl/core/mbox.c | 60 +++++++++++++++++++++++++----------------
> 1 file changed, 37 insertions(+), 23 deletions(-)
>
> diff --git a/drivers/cxl/core/mbox.c b/drivers/cxl/core/mbox.c
> index 28131c6f7fcf..d4233cfb2f99 100644
> --- a/drivers/cxl/core/mbox.c
> +++ b/drivers/cxl/core/mbox.c
> @@ -207,6 +207,38 @@ static bool cxl_mem_raw_command_allowed(u16 opcode)
> return true;
> }
>
> +static int cxl_to_mbox_cmd(struct cxl_dev_state *cxlds,
> + struct cxl_mbox_cmd *mbox, u16 opcode,
> + size_t in_size, size_t out_size, u64 in_payload)
> +{
> + *mbox = (struct cxl_mbox_cmd) {
> + .opcode = opcode,
> + .size_in = in_size,
> + .size_out = out_size,
Given we are going to possibly override this later, my inclination would
be to not set it here and instead do
if (out_size < 0)
mbox->size_out = cxlds->payload_size
else
mbox->size_out = out_size;
or
mbox->size_out = out_size < 0 ? cxlds->payload_size : out_size;
> + };
> +
> + if (!in_size)
> + goto size_out;
> +
> + mbox->payload_in = vmemdup_user(u64_to_user_ptr(in_payload), in_size);
> + if (!mbox->payload_in)
> + return PTR_ERR(mbox->payload_in);
> +
> +size_out:
Why format this like this? Using a goto to skip a couple of lines of code
is a bit ugly.
if (in_size) {
mbox->payload_in = vmemdup_user(u64_to_user_ptr(in_payload), in_size);
if (!mbox->payload_in)
return PTR_ERR(mbox->payload_in);
}
etc
> + /* Prepare to handle a full payload for variable sized output */
> + if (out_size < 0)
> + mbox->size_out = cxlds->payload_size;
> +
> + if (mbox->size_out) {
> + mbox->payload_out = kvzalloc(mbox->size_out, GFP_KERNEL);
> + if (!mbox->payload_out) {
> + kvfree(mbox->payload_in);
> + return -ENOMEM;
> + }
> + }
> + return 0;
> +}
> +
> static int cxl_to_mem_cmd_raw(struct cxl_dev_state *cxlds,
> const struct cxl_send_command *send_cmd,
> struct cxl_mem_command *mem_cmd)
> @@ -397,27 +429,13 @@ static int handle_mailbox_cmd_from_user(struct cxl_dev_state *cxlds,
> s32 *size_out, u32 *retval)
> {
> struct device *dev = cxlds->dev;
> - struct cxl_mbox_cmd mbox_cmd = {
> - .opcode = cmd->opcode,
> - .size_in = cmd->info.size_in,
> - .size_out = cmd->info.size_out,
> - };
> + struct cxl_mbox_cmd mbox_cmd;
> int rc;
>
> - if (cmd->info.size_out) {
> - mbox_cmd.payload_out = kvzalloc(cmd->info.size_out, GFP_KERNEL);
> - if (!mbox_cmd.payload_out)
> - return -ENOMEM;
> - }
> -
> - if (cmd->info.size_in) {
> - mbox_cmd.payload_in = vmemdup_user(u64_to_user_ptr(in_payload),
> - cmd->info.size_in);
> - if (IS_ERR(mbox_cmd.payload_in)) {
> - kvfree(mbox_cmd.payload_out);
> - return PTR_ERR(mbox_cmd.payload_in);
> - }
> - }
> + rc = cxl_to_mbox_cmd(cxlds, &mbox_cmd, cmd->opcode, cmd->info.size_in,
> + cmd->info.size_out, in_payload);
> + if (rc)
> + return rc;
>
> dev_dbg(dev,
> "Submitting %s command for user\n"
> @@ -471,10 +489,6 @@ int cxl_send_cmd(struct cxl_memdev *cxlmd, struct cxl_send_command __user *s)
> if (rc)
> return rc;
>
> - /* Prepare to handle a full payload for variable sized output */
> - if (c.info.size_out < 0)
> - c.info.size_out = cxlds->payload_size;
> -
> rc = handle_mailbox_cmd_from_user(cxlds, &c, send.in.payload,
> send.out.payload, &send.out.size,
> &send.retval);
next prev parent reply other threads:[~2022-03-25 10:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 1:11 [PATCH v3 0/9] Do not allow set-partition immediate mode alison.schofield
2022-03-24 1:11 ` [PATCH v3 1/9] cxl/mbox: Move cxl_mem_command construction to helper funcs alison.schofield
2022-03-25 10:27 ` Jonathan Cameron
2022-03-26 0:01 ` Alison Schofield
2022-03-24 1:11 ` [PATCH v3 2/9] cxl/mbox: Move raw command warning to raw command validation alison.schofield
2022-03-25 10:32 ` Jonathan Cameron
2022-03-24 1:11 ` [PATCH v3 3/9] cxl/mbox: Move build of user mailbox cmd to a helper function alison.schofield
2022-03-25 10:43 ` Jonathan Cameron [this message]
2022-03-24 1:11 ` [PATCH v3 4/9] cxl/mbox: Construct a users cxl_mbox_cmd in the validation path alison.schofield
2022-03-25 10:54 ` Jonathan Cameron
2022-03-26 0:37 ` Alison Schofield
2022-03-24 1:11 ` [PATCH v3 5/9] cxl/mbox: Remove dependency on cxl_mem_command for a debug msg alison.schofield
2022-03-25 10:56 ` Jonathan Cameron
2022-03-26 0:26 ` Alison Schofield
2022-03-24 1:11 ` [PATCH v3 6/9] cxl/mbox: Make handle_mailbox_cmd_from_user() use a mbox param alison.schofield
2022-03-25 11:04 ` Jonathan Cameron
2022-03-26 0:25 ` Alison Schofield
2022-03-29 10:50 ` Jonathan Cameron
2022-03-24 1:11 ` [PATCH v3 7/9] cxl/mbox: Move cxl_mem_command param to a local variable alison.schofield
2022-03-25 11:10 ` Jonathan Cameron
2022-03-24 1:11 ` [PATCH v3 8/9] cxl/mbox: Block immediate mode in SET_PARTITION_INFO command alison.schofield
2022-03-25 11:18 ` Jonathan Cameron
2022-03-26 0:31 ` Alison Schofield
2022-03-24 1:11 ` [PATCH v3 9/9] cxl/pmem: Remove CXL SET_PARTITION_INFO from exclusive_cmds list alison.schofield
2022-03-25 11:19 ` Jonathan Cameron
2022-03-25 10:34 ` [PATCH v3 0/9] Do not allow set-partition immediate mode Jonathan Cameron
2022-03-30 1:24 ` Dan Williams
2022-03-30 15:05 ` Jonathan Cameron
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=20220325104348.00002709@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.