public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
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 v3 3/6] ata: libata: cleanup fua handling
Date: Thu, 27 Oct 2022 11:32:18 +0200	[thread overview]
Message-ID: <9559f516-eb6b-1be5-15a4-92706d56a586@suse.de> (raw)
In-Reply-To: <20221027075026.240017-4-damien.lemoal@opensource.wdc.com>

On 10/27/22 09:50, 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

'detect a device FUA support'?
maybe 'to detect if a device supports FUA'?

> 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 libata.force= 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 advertizes support for the WRITE DMA FUA EXT command,
> * 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 supports NCQ (while this is not mandated by the standards,
>    this restriction is introduced to avoid problems with older non-NCQ
>    devices).
> 
> 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                     | 30 ++++++++++++++++++-
>   drivers/ata/libata-scsi.c                     | 30 ++-----------------
>   include/linux/libata.h                        |  8 +++--
>   4 files changed, 39 insertions(+), 32 deletions(-)
> Other than that:

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


  reply	other threads:[~2022-10-27  9:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27  7:50 [PATCH v3 0/6] Improve libata support for FUA Damien Le Moal
2022-10-27  7:50 ` [PATCH v3 1/6] ata: libata: Introduce ata_ncq_supported() Damien Le Moal
2022-10-27  9:24   ` Hannes Reinecke
2022-10-27  7:50 ` [PATCH v3 2/6] ata: libata: Rename and cleanup ata_rwcmd_protocol() Damien Le Moal
2022-10-27  9:25   ` Hannes Reinecke
2022-10-27  9:43   ` Sergei Shtylyov
2022-10-27  7:50 ` [PATCH v3 3/6] ata: libata: cleanup fua handling Damien Le Moal
2022-10-27  9:32   ` Hannes Reinecke [this message]
2022-10-27  7:50 ` [PATCH v3 4/6] ata: libata: Fix FUA handling in ata_build_rw_tf() Damien Le Moal
2022-10-27  8:21   ` Niklas Cassel
2022-10-27  9:12     ` Damien Le Moal
2022-10-27  9:42   ` Hannes Reinecke
2022-10-27 22:22     ` Damien Le Moal
2022-10-28 10:01       ` Hannes Reinecke
2022-10-28 16:45       ` Maciej S. Szmigiero
2022-10-28 16:45   ` Maciej S. Szmigiero
2022-10-27  7:50 ` [PATCH v3 5/6] ata: libata: blacklist FUA support for known buggy drives Damien Le Moal
2022-10-27  7:50 ` [PATCH v3 6/6] ata: libata: Enable fua support by default 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=9559f516-eb6b-1be5-15a4-92706d56a586@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