All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dai WeiBin \(David Dai\)" <david.dai@montage-tech.com>
To: <ben.widawsky@intel.com>
Cc: <linux-cxl@vger.kernel.org>
Subject: CXL mailbox background command
Date: Thu, 29 Apr 2021 09:24:14 +0800	[thread overview]
Message-ID: <008401d73c96$5dea8310$19bf8930$@montage-tech.com> (raw)

Hi Ben,

When we think of cxl mailbox background command, we met a difficult issue, how to handle switching between a background command end and another background command start?
The flow is as below:
1. Host/caller sends a command to cxl device.
2. CXL device identifies the command as a background command, then cxl device returns background command started.
3. CXL device start to handle background command
4. Host/caller can send other commands to cxl device when background command is ongoing on device side
5. At a special point host/caller is sending a command to device when the background command just is finished, the new command will be handled as a background command by device
6. That means the old background command ends, background Operation is set to 0, immediately the new background command is started, background Operation is set to 1 again at once.
7. So Host driver doesn’t have a chance to check the old background command has been finished, it still see “background Operation == 1”
8. Mailbox Status Register and Background Command Status Register are both read-only, that results there is not a handshake between host and device

Do you have any suggestion about this?

Thanks,
David




             reply	other threads:[~2021-04-29  1:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29  1:24 Dai WeiBin (David Dai) [this message]
2021-04-29  4:26 CXL mailbox background command Dai WeiBin (David Dai)
2021-04-29  9:18 ` Jonathan Cameron
2021-04-30  1:18   ` Dai WeiBin (David Dai)
2021-04-29 20:32 ` Dan Williams
2021-04-30  1:42   ` Dai WeiBin (David Dai)

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='008401d73c96$5dea8310$19bf8930$@montage-tech.com' \
    --to=david.dai@montage-tech.com \
    --cc=ben.widawsky@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    /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.