public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: yangxingui <yangxingui@huawei.com>,
	liyihang9@huawei.com, yanaijie@huawei.com
Cc: jejb@linux.ibm.com, martin.petersen@oracle.com,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxarm@huawei.com, prime.zeng@huawei.com,
	liuyonglong@huawei.com, kangfenglong@huawei.com,
	liyangyang20@huawei.com, f.fangjian@huawei.com,
	xiabing14@h-partners.com
Subject: Re: [PATCH v3 1/3] scsi: hisi_sas: Enable force phy when SATA disk directly connected
Date: Wed, 5 Mar 2025 16:15:41 +0000	[thread overview]
Message-ID: <cfef9d7d-adf9-43d8-9244-66f4eda081d2@oracle.com> (raw)
In-Reply-To: <2a59bb5c-797c-3745-384e-791a74858930@huawei.com>

On 05/03/2025 08:16, yangxingui wrote:
>>
>> Sure, something like that - you just need to get libsas to trigger the 
>> proper hw port id assignment for the device. As for specific 
>> implementation in the LLDD, that up to you guys.
> 
> Thank you for your suggestions. The disk was finally restored to normal, 
> but the error handling took a long time. Since the error handling would 
> set the host to the recovery state, other disks on the same host would 
> be blocked for a long time.

But that because you have IO inflight for the disk which was unplugged?

  reply	other threads:[~2025-03-05 16:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 13:05 [PATCH v3 0/3] scsi: hisi_sas: Fixed IO error caused by port id not updated Xingui Yang
2025-02-20 13:05 ` [PATCH v3 1/3] scsi: hisi_sas: Enable force phy when SATA disk directly connected Xingui Yang
2025-02-20 17:35   ` John Garry
2025-02-21  1:59     ` yangxingui
2025-02-24  8:29       ` John Garry
2025-02-24  9:36         ` yangxingui
2025-02-24 12:21           ` John Garry
2025-02-24 13:12             ` yangxingui
2025-02-24 17:34               ` John Garry
2025-02-25  1:48                 ` yangxingui
2025-02-25  8:19                   ` John Garry
2025-02-25  9:35                     ` yangxingui
2025-02-26  8:57                       ` John Garry
2025-02-27  8:33                         ` yangxingui
2025-03-04  9:48                           ` John Garry
2025-03-05  8:16                             ` yangxingui
2025-03-05 16:15                               ` John Garry [this message]
2025-03-06  1:44                                 ` yangxingui
2025-03-10 13:09                     ` yangxingui
2025-03-10 17:45                       ` John Garry
2025-03-11  1:53                         ` yangxingui
2025-03-12  9:44                         ` yangxingui
2025-03-12 11:19                           ` John Garry
2025-02-20 13:05 ` [PATCH v3 2/3] scsi: libsas: Move sas_put_device() to libsas.h Xingui Yang
2025-02-21  2:36   ` Jason Yan
2025-02-20 13:05 ` [PATCH v3 3/3] scsi: hisi_sas: Fixed IO error caused by port id not updated Xingui Yang

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=cfef9d7d-adf9-43d8-9244-66f4eda081d2@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=f.fangjian@huawei.com \
    --cc=jejb@linux.ibm.com \
    --cc=kangfenglong@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=liyangyang20@huawei.com \
    --cc=liyihang9@huawei.com \
    --cc=martin.petersen@oracle.com \
    --cc=prime.zeng@huawei.com \
    --cc=xiabing14@h-partners.com \
    --cc=yanaijie@huawei.com \
    --cc=yangxingui@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox