From: Tomas Henzl <thenzl@redhat.com>
To: Sumit.Saxena@avagotech.com, linux-scsi@vger.kernel.org
Cc: martin.petersen@oracle.com, hch@infradead.org,
jbottomley@parallels.com, kashyap.desai@avagotech.com
Subject: Re: [PATCH RESEND 5/7] megaraid_sas : Make HBA operational after LD_MAP_SYNC DCMD in OCR path
Date: Fri, 21 Nov 2014 14:51:58 +0100 [thread overview]
Message-ID: <546F437E.1020203@redhat.com> (raw)
In-Reply-To: <201411170958.sAH9vxfw008970@palmhbs0.lsi.com>
On 11/17/2014 10:54 AM, Sumit.Saxena@avagotech.com wrote:
> In OCR(Online Controller Reset) path, driver sets adapter state to MEGASAS_HBA_OPERATIONAL before getting new RAID map.
> There will be a small window where IO will come from OS with old RAID map.
> This patch will update adapter state to MEGASAS_HBA_OPERATIONAL, only after driver has new RAID map to avoid
> any IOs getting build using old RAID map.
>
> Signed-off-by: Sumit Saxena <sumit.saxena@avagotech.com>
> Signed-off-by: Kashyap Desai <kashyap.desai@avagotech.com>
> ---
> drivers/scsi/megaraid/megaraid_sas_fusion.c | 26 +++++++++++++-------------
> 1 files changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/scsi/megaraid/megaraid_sas_fusion.c b/drivers/scsi/megaraid/megaraid_sas_fusion.c
> index 98dfc1d..4e259ed 100644
> --- a/drivers/scsi/megaraid/megaraid_sas_fusion.c
> +++ b/drivers/scsi/megaraid/megaraid_sas_fusion.c
> @@ -2803,11 +2803,6 @@ int megasas_reset_fusion(struct Scsi_Host *shost, int iotimeout)
> }
> }
>
> - clear_bit(MEGASAS_FUSION_IN_RESET,
> - &instance->reset_flags);
> - instance->instancet->enable_intr(instance);
> - instance->adprecovery = MEGASAS_HBA_OPERATIONAL;
> -
> if (megasas_get_ctrl_info(instance)) {
> dev_info(&instance->pdev->dev,
> "Failed from %s %d\n",
> @@ -2825,6 +2820,11 @@ int megasas_reset_fusion(struct Scsi_Host *shost, int iotimeout)
> if (!megasas_get_map_info(instance))
> megasas_sync_map_info(instance);
>
> + clear_bit(MEGASAS_FUSION_IN_RESET,
> + &instance->reset_flags);
> + instance->instancet->enable_intr(instance);
> + instance->adprecovery = MEGASAS_HBA_OPERATIONAL;
> +
> /* Restart SR-IOV heartbeat */
> if (instance->requestorId) {
> if (!megasas_sriov_start_heartbeat(instance, 0))
> @@ -2841,14 +2841,14 @@ int megasas_reset_fusion(struct Scsi_Host *shost, int iotimeout)
> "successful for scsi%d.\n",
> instance->host->host_no);
>
> - if (instance->crash_dump_drv_support) {
> - if (instance->crash_dump_app_support)
> - megasas_set_crash_dump_params(instance,
> - MR_CRASH_BUF_TURN_ON);
> - else
> - megasas_set_crash_dump_params(instance,
> - MR_CRASH_BUF_TURN_OFF);
> - }
> + if (instance->crash_dump_drv_support &&
> + instance->crash_dump_app_support)
> + megasas_set_crash_dump_params(instance,
> + MR_CRASH_BUF_TURN_ON);
> + else
> + megasas_set_crash_dump_params(instance,
> + MR_CRASH_BUF_TURN_OFF);
> +
> retval = SUCCESS;
> goto out;
> }
Reviewed-by: Tomas Henzl <thenzl@redhat.com>
prev parent reply other threads:[~2014-11-21 13:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 9:54 [PATCH RESEND 5/7] megaraid_sas : Make HBA operational after LD_MAP_SYNC DCMD in OCR path Sumit.Saxena
2014-11-21 13:51 ` Tomas Henzl [this message]
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=546F437E.1020203@redhat.com \
--to=thenzl@redhat.com \
--cc=Sumit.Saxena@avagotech.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=kashyap.desai@avagotech.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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.