From: Hannes Reinecke <hare@suse.de>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
linux-ide@vger.kernel.org,
"Maciej S . Szmigiero" <mail@maciej.szmigiero.name>
Subject: Re: [PATCH 1/3] ata: libata: cleanup fua handling
Date: Fri, 21 Oct 2022 08:20:11 +0200 [thread overview]
Message-ID: <edb02b76-38bd-668a-a2a5-cd6537346735@suse.de> (raw)
In-Reply-To: <20221021053809.237651-2-damien.lemoal@opensource.wdc.com>
On 10/21/22 07:38, Damien Le Moal wrote:
> Move the detection of a device FUA support from
> ata_scsiop_mode_sense()/ata_dev_supports_fua() to device scan time in
> ata_dev_configure().
>
> The function ata_dev_config_fua() is introduced to detect a device FUA
> support and this support is indicated using the new device flag
> ATA_DFLAG_FUA. In order to blacklist known buggy devices, the horkage
> flag ATA_HORKAGE_NO_FUA is introduced. Similarly to other horkage flags,
> the arguments fua and nofua are also introduced to allow a user to
> control this horkage flag through the "force" libata module parameter.
>
> The ATA_DFLAG_FUA device flag is set only and only if all the following
> conditions are met:
> * libata.fua module parameter is set to 1
> * The device is not marked with the ATA_HORKAGE_NO_FUA flag, either from
> the blacklist or set by the user with libata.force=nofua
> * The device advertizes support for the WRITE DMA FUA EXT command,
> * The device supports LBA48 and is not restricted to single block PIO
>
> Note: Enabling or diabling libata fua support for all devices by default
> can now by done using either the "fua" module parameter or the
> "force=[port[.device]][no]fua" module parameter when libata.fua==1.
>
> Signed-off-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
> ---
> .../admin-guide/kernel-parameters.txt | 3 ++
> drivers/ata/libata-core.c | 29 +++++++++++++++++-
> drivers/ata/libata-scsi.c | 30 ++-----------------
> include/linux/libata.h | 8 +++--
> 4 files changed, 38 insertions(+), 32 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Ivo Totev, Andrew
Myers, Andrew McDonald, Martje Boudien Moerman
next prev parent reply other threads:[~2022-10-21 6:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 5:38 [PATCH 0/3] Improve libata support for FUA Damien Le Moal
2022-10-21 5:38 ` [PATCH 1/3] ata: libata: cleanup fua handling Damien Le Moal
2022-10-21 6:20 ` Hannes Reinecke [this message]
2022-10-21 5:38 ` [PATCH 2/3] ata: libata: allow toggling fua parameter at runtime Damien Le Moal
2022-10-21 6:21 ` Hannes Reinecke
2022-10-21 6:50 ` Damien Le Moal
2022-10-21 8:00 ` Damien Le Moal
2022-10-21 8:45 ` Hannes Reinecke
2022-10-21 8:48 ` Damien Le Moal
2022-10-21 5:38 ` [PATCH 3/3] ata: libata: Enable fua support by default Damien Le Moal
2022-10-21 6:22 ` Hannes Reinecke
2022-10-21 21:02 ` [PATCH 0/3] Improve libata support for FUA Maciej S. Szmigiero
2022-10-21 22:45 ` Damien Le Moal
2022-10-22 13:50 ` Hannes Reinecke
2022-10-23 0:27 ` Damien Le Moal
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=edb02b76-38bd-668a-a2a5-cd6537346735@suse.de \
--to=hare@suse.de \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
/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