public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Igor Pylypiv <ipylypiv@google.com>
Cc: Damien Le Moal <dlemoal@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH v2] ata: libata-sata: Use LBA from sense data descriptor
Date: Thu, 10 Apr 2025 16:04:29 +0200	[thread overview]
Message-ID: <Z_fP7RKf5AbybyXB@ryzen> (raw)
In-Reply-To: <Z_fBaVZkcD9AtTaR@ryzen>

On Thu, Apr 10, 2025 at 03:02:33PM +0200, Niklas Cassel wrote:
> 
> I guess now when we do have access to the information, the most consistent
> thing would be to fill all field we can in qc->result_tf... but, to do this
> for every IO might slow things down.
> 
> So is there perhaps some logic to only filling LBA (in addition to STATUS
> and ERROR, which are filled for all NCQ commands), since that is the only
> field that can change, as per the specs.

Looking at this more closely:
https://github.com/torvalds/linux/blob/v6.15-rc1/include/linux/libata.h#L574-L577

FEATURE is a union with ERROR, so we cannot save it in qc->result_tf.

COMMAND is a union with STATUS, so we cannot save it in qc->result_tf.


The sense data descriptor does not provide AUXILIARY, nor DEVICE,
so we cannot save these.


I will send a v3 that does populate COUNT (7:0) and COUNT (15:8),
since it is only so few fields that we do have, we might as well
populate them properly.


Kind regards,
Niklas

  reply	other threads:[~2025-04-10 14:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-09  8:45 [PATCH v2] ata: libata-sata: Use LBA from sense data descriptor Niklas Cassel
2025-04-09 17:29 ` Igor Pylypiv
2025-04-10 13:02   ` Niklas Cassel
2025-04-10 14:04     ` Niklas Cassel [this message]
2025-04-10 17:00       ` Igor Pylypiv
2025-04-11  6:35         ` Niklas Cassel
2025-04-11  0:01       ` 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=Z_fP7RKf5AbybyXB@ryzen \
    --to=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=ipylypiv@google.com \
    --cc=linux-ide@vger.kernel.org \
    /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