linux-stable.git/include/linux/nvme.h, branch v5.6.2

nvme: hwmon: provide temperature min and max values for each sensor

2019-11-21T17:21:08+00:00

According to the NVMe specification, the over temperature threshold and
under temperature threshold features shall be implemented for Composite
Temperature if a non-zero WCTEMP field value is reported in the Identify
Controller data structure.  The features are also implemented for all
implemented temperature sensors (i.e., all Temperature Sensor fields that
report a non-zero value).

This provides the over temperature threshold and under temperature
threshold for each sensor as temperature min and max values of hwmon
sysfs attributes.

The WCTEMP is already provided as a temperature max value for Composite
Temperature, but this change isn't incompatible.  Because the default
value of the over temperature threshold for Composite Temperature is
the WCTEMP.

Now the alarm attribute for Composite Temperature indicates one of the
temperature is outside of a temperature threshold.  Because there is only
a single bit in Critical Warning field that indicates a temperature is
outside of a threshold.

Example output from the "sensors" command:

nvme-pci-0100
Adapter: PCI adapter
Composite:    +33.9°C  (low  = -273.1°C, high = +69.8°C)
                       (crit = +79.8°C)
Sensor 1:     +34.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +31.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 5:     +47.9°C  (low  = -273.1°C, high = +65261.8°C)

This also adds helper macros for kelvin from/to milli Celsius conversion,
and replaces the repeated code in hwmon.c.

Cc: Keith Busch 
Cc: Jens Axboe 
Cc: Christoph Hellwig 
Cc: Sagi Grimberg 
Cc: Jean Delvare 
Reviewed-by: Guenter Roeck 
Tested-by: Guenter Roeck 
Signed-off-by: Akinobu Mita 
Signed-off-by: Keith Busch

nvme: resync include/linux/nvme.h with nvmecli

2019-11-04T17:56:41+00:00

Update enumerations and structures in include/linux/nvme.h
to resync with the nvmecli.

All the updates are mentioned in the ratified NVMe 1.4 spec
https://nvmexpress.org/wp-content/uploads/NVM-Express-1_4-2019.06.10-Ratified.pdf

Reviewed-by: Christoph Hellwig 
Signed-off-by: Revanth Rajashekar 
Signed-off-by: Keith Busch 
Signed-off-by: Jens Axboe

nvme: introduce "Command Aborted By host" status code

2019-11-04T17:56:41+00:00

Fix the status code of canceled requests initiated by the host according
to TP4028 (Status Code 0x371):
"Command Aborted By host: The command was aborted as a result of host
action (e.g., the host disconnected the Fabric connection)."

Also in a multipath environment, unless otherwise specified, errors of
this type (path related) should be retried using a different path, if
one is available.

Signed-off-by: Max Gurtovoy 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Keith Busch 
Signed-off-by: Jens Axboe

nvme-pci: Add support for variable IO SQ element size

2019-08-29T19:55:02+00:00

The size of a submission queue element should always be 6 (64 bytes)
by spec.

However some controllers such as Apple's are not properly implementing
the standard and require a different size.

This provides the ground work for the subsequent quirks for these
controllers.

Signed-off-by: Benjamin Herrenschmidt 
Reviewed-by: Minwoo Im 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Sagi Grimberg

nvme: trace: support for Get LBA Status opcode parsed

2019-08-29T19:55:01+00:00

This patch adds Get LBA Status command's opcode to the macro that is
used by the trace feature.  Now we can see "get_lba_status" instead of
the opcode value itself.

Signed-off-by: Minwoo Im 
Signed-off-by: Sagi Grimberg

nvme: add Get LBA Status command opcode

2019-08-29T19:55:01+00:00

NVMe 1.4 added Get LBA Status command with opcode 0x86.

Signed-off-by: Minwoo Im 
Signed-off-by: Sagi Grimberg

nvme: add I/O characteristics fields

2019-07-09T21:15:37+00:00

Several new fields have been introduced in version 1.4 of the NVMe spec
at offsets that were defined as reserved in version 1.3d of the NVMe
spec. Update the definition of the nvme_id_ns data structure such that
it is in sync with version 1.4 of the NVMe spec. This change preserves
backwards compatibility.

Signed-off-by: Bart Van Assche 
Reviewed-by: Keith Busch 
Reviewed-by: Chaitanya Kulkarni 
Reviewed-by: Martin K. Petersen 
Reviewed-by: Hannes Reinecke 
Signed-off-by: Christoph Hellwig

nvme-trace: support for fabrics commands in host-side

2019-06-21T09:12:22+00:00

This patch introduces fabrics commands tracing feature from host-side.
This patch does not include any changes for the previous host-side
tracing, but just add fabrics commands parsing in cmd=() format.

Signed-off-by: Minwoo Im 
[hch: fixed some whitespace damage]
Signed-off-by: Christoph Hellwig

nvme-trace: move opcode symbol print to nvme.h

2019-06-21T09:12:19+00:00

The following patches are going to provide the target-side trace which
might need these kind of macros.  It would be great if it can be shared
between host and target side both.

Signed-off-by: Minwoo Im 
Signed-off-by: Christoph Hellwig

nvme: introduce nvme_is_fabrics to check fabrics cmd

2019-06-21T09:08:38+00:00

This patch introduces a nvme_is_fabrics() inline function to check
whether or not the given command structure is for fabrics.

Signed-off-by: Minwoo Im 
Reviewed-by: Sagi Grimberg 
Signed-off-by: Sagi Grimberg 
Signed-off-by: Christoph Hellwig