From: Dave Marquardt <[email protected]>

Add support for VFC_NOOP messages from VIOS to enable keep-alive
functionality between the client and server.

Define the VFC_NOOP CRQ format and add handling in both the main CRQ
handler (ibmvfc_handle_crq) and sub-CRQ handler (ibmvfc_handle_scrq).
Log unexpected NOOP messages if received before VIOS advertises support
during NPIV login.

Set the IBMVFC_CAN_USE_NOOP_CMD capability bit during NPIV login to
inform VIOS that the client can handle NOOP commands.

Signed-off-by: Dave Marquardt <[email protected]>
---
 drivers/scsi/ibmvscsi/ibmvfc-core.c | 22 ++++++++++++++++++++--
 1 file changed, 20 insertions(+), 2 deletions(-)

diff --git a/drivers/scsi/ibmvscsi/ibmvfc-core.c 
b/drivers/scsi/ibmvscsi/ibmvfc-core.c
index 537d2b565628..aec953f29e55 100644
--- a/drivers/scsi/ibmvscsi/ibmvfc-core.c
+++ b/drivers/scsi/ibmvscsi/ibmvfc-core.c
@@ -1562,7 +1562,9 @@ static void ibmvfc_set_login_info(struct ibmvfc_host 
*vhost)
                login_info->flags |= cpu_to_be16(IBMVFC_CLIENT_MIGRATED);
 
        login_info->max_cmds = cpu_to_be32(max_cmds);
-       login_info->capabilities = cpu_to_be64(IBMVFC_CAN_MIGRATE | 
IBMVFC_CAN_SEND_VF_WWPN);
+       login_info->capabilities =
+               cpu_to_be64(IBMVFC_CAN_MIGRATE | IBMVFC_CAN_SEND_VF_WWPN |
+                           IBMVFC_CAN_USE_NOOP_CMD);
 
        if (vhost->mq_enabled || vhost->using_channels) {
                login_info->capabilities |= 
cpu_to_be64(IBMVFC_CAN_USE_CHANNELS);
@@ -3647,6 +3649,14 @@ static void ibmvfc_handle_crq(struct ibmvfc_crq *crq, 
struct ibmvfc_host *vhost,
        if (crq->format == IBMVFC_ASYNC_EVENT)
                return;
 
+       if (crq->format == IBMVFC_NOOP) {
+               if (vhost->state == IBMVFC_ACTIVE &&
+                   !ibmvfc_check_caps(vhost, IBMVFC_SUPPORT_NOOP_CMD))
+                       dev_err_ratelimited(vhost->dev,
+                                           "Received unexpected NOOP command 
from partner\n");
+               return;
+       }
+
        /* The only kind of payload CRQs we should get are responses to
         * things we send. Make sure this response is to something we
         * actually sent
@@ -4177,7 +4187,15 @@ static void ibmvfc_handle_scrq(struct ibmvfc_crq *crq, 
struct ibmvfc_host *vhost
        case IBMVFC_CRQ_XPORT_EVENT:
                return;
        default:
-               dev_err(vhost->dev, "Got and invalid message type 0x%02x\n", 
crq->valid);
+               dev_err(vhost->dev, "Got an invalid message type 0x%02x\n", 
crq->valid);
+               return;
+       }
+
+       if (crq->format == IBMVFC_NOOP)
+               return;
+
+       if (unlikely(!evt)) {
+               dev_err(vhost->dev, "Received null event\n");
                return;
        }
 

-- 
2.55.0



Reply via email to