Fixed up a couple spots that were out of line with the PAPR in regards
to its defined VSCSI protocol. Did away with some magic numbers directly
in the code. Fixed a minor endian issue.
--
v2 changes:
-Renamed CRQ header enums and added enums for INIT formats
-Check that crq->valid != VIOSRP_CRQ_FREE before handling in place
of hacky bitwise & to check for first bit being set.
-Added define for AIX os_type
-Left sysfs config attribute to prevent breaking userspace
Tyrel Datwyler (7):
ibmvscsi: Correct values for several viosrp_crq_format enums
ibmvscsi: Add and use enums for valid CRQ header values
ibmvscsi: Replace magic values in set_adpater_info() with defines
ibmvscsi: Use of_root to access OF device tree root node
ibmvscsi: Remove unsupported host config MAD
ibmvscsi: Add endian conversions to sysfs attribute show functions
ibmvscsi: use H_CLOSED instead of magic number
drivers/scsi/ibmvscsi/ibmvscsi.c | 128 ++++++++++-----------------------------
drivers/scsi/ibmvscsi/viosrp.h | 26 +++++---
2 files changed, 49 insertions(+), 105 deletions(-)
--
2.5.0
The PAPR defines four valid header values for the first byte of a
CRQ message. Namely, an unused/empty message (0x00), a valid
command/response entry (0x80), a valid initialization entry (0xC0),
and a valid transport event (0xFF). Further, initialization responses
have two formats namely initialize (0x01) and initialize complete
(0x02). Define these values as enums and use them in the code in
place of their magic number equivalents.
Signed-off-by: Tyrel Datwyler <redacted>
---
drivers/scsi/ibmvscsi/ibmvscsi.c | 18 +++++++++---------
drivers/scsi/ibmvscsi/viosrp.h | 12 ++++++++++++
2 files changed, 21 insertions(+), 9 deletions(-)
@@ -231,7 +231,7 @@ static void ibmvscsi_task(void *data)/* Pull all the valid messages off the CRQ */while((crq=crq_queue_next_crq(&hostdata->queue))!=NULL){ibmvscsi_handle_crq(crq,hostdata);-crq->valid=0x00;+crq->valid=VIOSRP_CRQ_FREE;}vio_enable_interrupts(vdev);
@@ -1791,7 +1791,7 @@ static void ibmvscsi_handle_crq(struct viosrp_crq *crq,dev_err(hostdata->dev,"unknown crq message type: %d\n",crq->format);}return;-case0xFF:/* Hypervisor telling us the connection is closed */+caseVIOSRP_CRQ_XPORT_EVENT:/* Hypervisor telling us the connection is closed */scsi_block_requests(hostdata->host);atomic_set(&hostdata->request_limit,0);if(crq->format==0x06){
@@ -1807,7 +1807,7 @@ static void ibmvscsi_handle_crq(struct viosrp_crq *crq,ibmvscsi_reset_host(hostdata);}return;-case0x80:/* real payload */+caseVIOSRP_CRQ_CMD_RSP:/* real payload */break;default:dev_err(hostdata->dev,"got an invalid message type 0x%02x\n",
The values returned by the show functions for the host os_type,
mad_version, and partition_number attributes get their values
directly from the madapter_info struct whose associated fields are
__be32 typed. Added endian conversion to ensure these values are
sane on LE platforms.
Signed-off-by: Tyrel Datwyler <redacted>
Reviewed-by: Johannes Thumshirn <redacted>
---
drivers/scsi/ibmvscsi/ibmvscsi.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
In a couple places the magic value of 2 is used to check the return
code of hypercalls. This translates to H_CLOSED.
Signed-off-by: Tyrel Datwyler <redacted>
---
drivers/scsi/ibmvscsi/ibmvscsi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
@@ -314,7 +314,7 @@ static int ibmvscsi_reset_crq_queue(struct crq_queue *queue,rc=plpar_hcall_norets(H_REG_CRQ,vdev->unit_address,queue->msg_token,PAGE_SIZE);-if(rc==2){+if(rc==H_CLOSED){/* Adapter is good, but other end is not ready */dev_warn(hostdata->dev,"Partner adapter not ready\n");}elseif(rc!=0){
@@ -364,7 +364,7 @@ static int ibmvscsi_init_crq_queue(struct crq_queue *queue,rc=ibmvscsi_reset_crq_queue(queue,hostdata);-if(rc==2){+if(rc==H_CLOSED){/* Adapter is good, but other end is not ready */dev_warn(hostdata->dev,"Partner adapter not ready\n");retrc=0;
The root node of the OF device tree is exported as of_root. No need
to look up the root by path name. Instead just get a reference
directly via of_root.
Signed-off-by: Tyrel Datwyler <redacted>
Reviewed-by: Johannes Thumshirn <redacted>
---
drivers/scsi/ibmvscsi/ibmvscsi.c | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
@@ -248,25 +248,23 @@ static void ibmvscsi_task(void *data)staticvoidgather_partition_info(void){-structdevice_node*rootdn;-constchar*ppartition_name;const__be32*p_number_ptr;/* Retrieve information about this partition */-rootdn=of_find_node_by_path("/");-if(!rootdn){+if(!of_root)return;-}-ppartition_name=of_get_property(rootdn,"ibm,partition-name",NULL);+of_node_get(of_root);++ppartition_name=of_get_property(of_root,"ibm,partition-name",NULL);if(ppartition_name)strncpy(partition_name,ppartition_name,sizeof(partition_name));-p_number_ptr=of_get_property(rootdn,"ibm,partition-no",NULL);+p_number_ptr=of_get_property(of_root,"ibm,partition-no",NULL);if(p_number_ptr)partition_number=of_read_number(p_number_ptr,1);-of_node_put(rootdn);+of_node_put(of_root);}staticvoidset_adapter_info(structibmvscsi_host_data*hostdata)
A VIOSRP_HOST_CONFIG_TYPE management datagram (MAD) has existed in
the code for some time. From what information I've gathered from
Brian King this was likely implemented on the host side in a SLES 9
based VIOS, which is no longer supported anywhere. Further, it is
not defined in PAPR or supported by any AIX based VIOS.
Treating as bit rot and removing the associated host config code.
The config attribute and its show function are left as not to break
userspace. The behavior remains the same returning nothing.
Signed-off-by: Tyrel Datwyler <redacted>
---
drivers/scsi/ibmvscsi/ibmvscsi.c | 71 +++-------------------------------------
drivers/scsi/ibmvscsi/viosrp.h | 7 ----
2 files changed, 4 insertions(+), 74 deletions(-)
@@ -1853,62 +1853,6 @@ static void ibmvscsi_handle_crq(struct viosrp_crq *crq,}/**-*ibmvscsi_get_host_config:Sendthecommandtotheservertogethost-*configurationdata.Thedataisopaquetous.-*/-staticintibmvscsi_do_host_config(structibmvscsi_host_data*hostdata,-unsignedchar*buffer,intlength)-{-structviosrp_host_config*host_config;-structsrp_event_struct*evt_struct;-unsignedlongflags;-dma_addr_taddr;-intrc;--evt_struct=get_event_struct(&hostdata->pool);-if(!evt_struct){-dev_err(hostdata->dev,"couldn't allocate event for HOST_CONFIG!\n");-return-1;-}--init_event_struct(evt_struct,-sync_completion,-VIOSRP_MAD_FORMAT,-info_timeout);--host_config=&evt_struct->iu.mad.host_config;--/* The transport length field is only 16-bit */-length=min(0xffff,length);--/* Set up a lun reset SRP command */-memset(host_config,0x00,sizeof(*host_config));-host_config->common.type=cpu_to_be32(VIOSRP_HOST_CONFIG_TYPE);-host_config->common.length=cpu_to_be16(length);-addr=dma_map_single(hostdata->dev,buffer,length,DMA_BIDIRECTIONAL);--if(dma_mapping_error(hostdata->dev,addr)){-if(!firmware_has_feature(FW_FEATURE_CMO))-dev_err(hostdata->dev,-"dma_mapping error getting host config\n");-free_event_struct(&hostdata->pool,evt_struct);-return-1;-}--host_config->buffer=cpu_to_be64(addr);--init_completion(&evt_struct->comp);-spin_lock_irqsave(hostdata->host->host_lock,flags);-rc=ibmvscsi_send_srp_event(evt_struct,hostdata,info_timeout*2);-spin_unlock_irqrestore(hostdata->host->host_lock,flags);-if(rc==0)-wait_for_completion(&evt_struct->comp);-dma_unmap_single(hostdata->dev,addr,length,DMA_BIDIRECTIONAL);--returnrc;-}--/***ibmvscsi_slave_configure:Setthe"allow_restart"flagforeachdisk.*@sdev:structscsi_devicedevicetoconfigure*
The enum values for VIOSRP_LINUX_FORMAT and VIOSRP_INLINE_FORMAT are
off by one. They are currently defined as 0x06 and 0x07 respetively.
These values are defined in PAPR correctly as 0x05 and 0x06. This
inconsistency has gone unnoticed as neither enum is currently used.
The possible future support of PING messages between the VIOS and
client adapter relies on VIOSRP_INLINE_FORMAT crq messages.
Corrected these enum values to match PAPR definitions.
Signed-off-by: Tyrel Datwyler <redacted>
Reviewed-by: Johannes Thumshirn <redacted>
---
drivers/scsi/ibmvscsi/viosrp.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
From: Johannes Thumshirn <hidden> Date: 2016-02-11 08:51:51
On Wed, Feb 10, 2016 at 07:32:23PM -0600, Tyrel Datwyler wrote:
The PAPR defines four valid header values for the first byte of a
CRQ message. Namely, an unused/empty message (0x00), a valid
command/response entry (0x80), a valid initialization entry (0xC0),
and a valid transport event (0xFF). Further, initialization responses
have two formats namely initialize (0x01) and initialize complete
(0x02). Define these values as enums and use them in the code in
place of their magic number equivalents.
Signed-off-by: Tyrel Datwyler <redacted>
Reviewed-by: Johannes Thumshirn <redacted>
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
From: Johannes Thumshirn <hidden> Date: 2016-02-11 08:53:33
On Wed, Feb 10, 2016 at 07:32:26PM -0600, Tyrel Datwyler wrote:
A VIOSRP_HOST_CONFIG_TYPE management datagram (MAD) has existed in
the code for some time. From what information I've gathered from
Brian King this was likely implemented on the host side in a SLES 9
based VIOS, which is no longer supported anywhere. Further, it is
not defined in PAPR or supported by any AIX based VIOS.
Treating as bit rot and removing the associated host config code.
The config attribute and its show function are left as not to break
userspace. The behavior remains the same returning nothing.
Signed-off-by: Tyrel Datwyler <redacted>
Reviewed-by: Johannes Thumshirn <redacted>
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
From: Johannes Thumshirn <hidden> Date: 2016-02-11 08:54:26
On Wed, Feb 10, 2016 at 07:32:28PM -0600, Tyrel Datwyler wrote:
In a couple places the magic value of 2 is used to check the return
code of hypercalls. This translates to H_CLOSED.
Signed-off-by: Tyrel Datwyler <redacted>
Reviewed-by: Johannes Thumshirn <redacted>
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
Tyrel:
Thanks for incorporating the suggestions.
Reviewed-by: Manoj Kumar <redacted>
---
Manoj Kumar
On 2/10/2016 7:32 PM, Tyrel Datwyler wrote:
quoted hunk
The PAPR defines four valid header values for the first byte of a
CRQ message. Namely, an unused/empty message (0x00), a valid
command/response entry (0x80), a valid initialization entry (0xC0),
and a valid transport event (0xFF). Further, initialization responses
have two formats namely initialize (0x01) and initialize complete
(0x02). Define these values as enums and use them in the code in
place of their magic number equivalents.
Signed-off-by: Tyrel Datwyler <redacted>
---
drivers/scsi/ibmvscsi/ibmvscsi.c | 18 +++++++++---------
drivers/scsi/ibmvscsi/viosrp.h | 12 ++++++++++++
2 files changed, 21 insertions(+), 9 deletions(-)
@@ -231,7 +231,7 @@ static void ibmvscsi_task(void *data)/* Pull all the valid messages off the CRQ */while((crq=crq_queue_next_crq(&hostdata->queue))!=NULL){ibmvscsi_handle_crq(crq,hostdata);-crq->valid=0x00;+crq->valid=VIOSRP_CRQ_FREE;}vio_enable_interrupts(vdev);
@@ -1791,7 +1791,7 @@ static void ibmvscsi_handle_crq(struct viosrp_crq *crq,dev_err(hostdata->dev,"unknown crq message type: %d\n",crq->format);}return;-case0xFF:/* Hypervisor telling us the connection is closed */+caseVIOSRP_CRQ_XPORT_EVENT:/* Hypervisor telling us the connection is closed */scsi_block_requests(hostdata->host);atomic_set(&hostdata->request_limit,0);if(crq->format==0x06){
@@ -1807,7 +1807,7 @@ static void ibmvscsi_handle_crq(struct viosrp_crq *crq,ibmvscsi_reset_host(hostdata);}return;-case0x80:/* real payload */+caseVIOSRP_CRQ_CMD_RSP:/* real payload */break;default:dev_err(hostdata->dev,"got an invalid message type 0x%02x\n",
The enum values for VIOSRP_LINUX_FORMAT and VIOSRP_INLINE_FORMAT are
off by one. They are currently defined as 0x06 and 0x07 respetively.
These values are defined in PAPR correctly as 0x05 and 0x06. This
inconsistency has gone unnoticed as neither enum is currently used.
The possible future support of PING messages between the VIOS and
client adapter relies on VIOSRP_INLINE_FORMAT crq messages.
Corrected these enum values to match PAPR definitions.
Signed-off-by: Tyrel Datwyler <redacted>
Reviewed-by: Johannes Thumshirn <redacted>
---
drivers/scsi/ibmvscsi/viosrp.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
From: James Bottomley <James.Bottomley@HansenPartnership.com> Date: 2016-02-12 16:43:19
On Wed, 2016-02-10 at 19:32 -0600, Tyrel Datwyler wrote:
Add defines for mad version and mad os_type, and replace the magic
numbers in set_adapter_info() accordingly.
Signed-off-by: Tyrel Datwyler <redacted>
---
On Wed, 2016-02-10 at 19:32 -0600, Tyrel Datwyler wrote:
quoted
Add defines for mad version and mad os_type, and replace the magic
numbers in set_adapter_info() accordingly.
Signed-off-by: Tyrel Datwyler <redacted>
---
The patch is slightly changed from v1. A define for AIX os type was
added as mentioned in the cover letter v2 changes, and I moved the
defines to the mad_adapter_info_data structure around the fields they apply.
-Tyrel
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: James Bottomley <James.Bottomley@HansenPartnership.com> Date: 2016-02-12 16:53:13
On Fri, 2016-02-12 at 08:51 -0800, Tyrel Datwyler wrote:
On 02/12/2016 08:43 AM, James Bottomley wrote:
quoted
On Wed, 2016-02-10 at 19:32 -0600, Tyrel Datwyler wrote:
quoted
Add defines for mad version and mad os_type, and replace the
magic
numbers in set_adapter_info() accordingly.
Signed-off-by: Tyrel Datwyler <redacted>
---
The patch is slightly changed from v1. A define for AIX os type was
added as mentioned in the cover letter v2 changes, and I moved the
defines to the mad_adapter_info_data structure around the fields they
apply.