| /openbmc/u-boot/doc/ |
| H A D | README.nvme | 6 What is NVMe
9 NVM Express (NVMe) is a register level interface that allows host software to
21 memory that is formatted into logical blocks. An NVMe namespace is equivalent
26 There is an NVMe uclass driver (driver name "nvme"), an NVMe host controller
27 driver (driver name "nvme") and an NVMe namespace block driver (driver name
28 "nvme-blk"). The host controller driver is supposed to probe the hardware and
31 is triggered by the NVMe uclass driver and the actual work is done in the NVMe
36 It only support basic block read/write functions in the NVMe driver.
40 CONFIG_NVME Enable NVMe device support
41 CONFIG_CMD_NVME Enable basic NVMe commands
[all …]
|
| /openbmc/linux/drivers/nvme/host/ |
| H A D | Kconfig | 16 module will be called nvme.
19 bool "NVMe multipath support"
22 This option enables support for multipath access to NVMe
24 /dev/nvmeXnY device will show up for each NVMe namespace,
28 bool "NVMe verbose error reporting"
31 This option enables verbose reporting for NVMe errors. The
36 bool "NVMe hardware monitoring"
39 This provides support for NVMe hardware monitoring. If enabled,
40 a hardware monitoring device will be created for each NVMe drive
53 This provides support for the NVMe over Fabrics protocol using
[all …]
|
| H A D | Makefile | 5 obj-$(CONFIG_NVME_CORE) += nvme-core.o
6 obj-$(CONFIG_BLK_DEV_NVME) += nvme.o
7 obj-$(CONFIG_NVME_FABRICS) += nvme-fabrics.o
8 obj-$(CONFIG_NVME_RDMA) += nvme-rdma.o
9 obj-$(CONFIG_NVME_FC) += nvme-fc.o
10 obj-$(CONFIG_NVME_TCP) += nvme-tcp.o
11 obj-$(CONFIG_NVME_APPLE) += nvme-apple.o
13 nvme-core-y += core.o ioctl.o sysfs.o pr.o
14 nvme-core-$(CONFIG_NVME_VERBOSE_ERRORS) += constants.o
15 nvme-core-$(CONFIG_TRACING) += trace.o
[all …]
|
| H A D | fabrics.c | 3 * NVMe over Fabrics common host code.
13 #include "nvme.h"
125 * @ctrl: Host NVMe controller instance which we got the address
151 * nvmf_reg_read32() - NVMe Fabrics "Property Get" API function.
152 * @ctrl: Host NVMe controller instance maintaining the admin
154 * the allocated NVMe controller resource on the target system.
156 * register (see the fabrics section of the NVMe standard).
161 * from an NVMe controller on the target system.
164 * NVMe fabrics space.)
168 * > 0: NVMe error status code
[all …]
|
| /openbmc/linux/drivers/nvme/target/ |
| H A D | Kconfig | 4 tristate "NVMe Target support"
10 This enabled target side support for the NVMe protocol, that is
11 it allows the Linux kernel to implement NVMe subsystems and
12 controllers and export Linux block devices as NVMe namespaces.
16 To configure the NVMe target you probably want to use the nvmetcli
20 bool "NVMe Target Passthrough support"
24 This enables target side NVMe passthru controller support for the
25 NVMe Over Fabrics protocol. It allows for hosts to manage and
26 directly access an actual NVMe controller residing on the target
32 tristate "NVMe loopback device support"
[all …]
|
| /openbmc/qemu/docs/system/devices/ |
| H A D | nvme.rst | 2 NVMe Emulation
5 QEMU provides NVMe emulation through the ``nvme``, ``nvme-ns`` and
6 ``nvme-subsys`` devices.
10 * `Adding NVMe Devices`_, `additional namespaces`_ and `NVM subsystems`_.
15 Adding NVMe Devices
21 The QEMU emulated NVMe controller implements version 1.4 of the NVM Express
29 The simplest way to attach an NVMe controller on the QEMU PCI bus is to add the
35 -device nvme,serial=deadbeef,drive=nvm
37 There are a number of optional general parameters for the ``nvme`` device. Some
38 are mentioned here, but see ``-device nvme,help`` to list all possible
[all …]
|
| /openbmc/docs/designs/ |
| H A D | nvmemi-over-smbus.md | 1 ### NVMe-MI over SMBus
9 Currently, OpenBMC does not support NVMe drive information. NVMe-MI
10 specification defines a command that can read the NVMe drive information via
11 SMBus directly. The NVMe drive can provide its information or status, like
13 monitor NVMe drives so appropriate action can be taken.
17 NVMe-MI specification defines a command called
18 `NVM Express Basic Management Command` that can read the NVMe drives information
22 For our purpose is retrieve NVMe drives information, therefore, using NVM
23 Express Basic Management Command where describe in NVMe-MI specification to
24 communicate with NVMe drives. According to different platforms, temperature
[all …]
|
| /openbmc/linux/Documentation/nvme/ |
| H A D | feature-and-quirk-policy.rst | 4 Linux NVMe feature and and quirk policy
8 Linux NVMe driver and what is not.
16 The Linux NVMe host driver in drivers/nvme/host/ supports devices
17 implementing the NVM Express (NVMe) family of specifications, which
20 - the NVMe Base specification
23 - the NVMe Management Interface specification
25 See https://nvmexpress.org/developers/ for the NVMe specifications.
31 NVMe is a large suite of specifications, and contains features that are only
36 maintainability of the NVMe host driver.
38 Any feature implemented in the Linux NVMe host driver must support the
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/nvme/ |
| H A D | apple,nvme-ans.yaml | 4 $id: http://devicetree.org/schemas/nvme/apple,nvme-ans.yaml#
16 - apple,t8103-nvme-ans2
17 - apple,t8112-nvme-ans2
18 - apple,t6000-nvme-ans2
19 - const: apple,nvme-ans2
23 - description: NVMe and NVMMU registers
28 - const: nvme
38 - description: power domain for the NVMe controller.
39 - description: power domain for the first PCIe bus connecting the NVMe
42 connecting the NVMe controller to the storage modules.
[all …]
|
| /openbmc/u-boot/cmd/ |
| H A D | nvme.c | 10 #include <nvme.h>
44 nvme, 8, 1, do_nvme,
46 "scan - scan NVMe devices\n"
47 "nvme detail - show details of current NVMe device\n"
48 "nvme info - show all available NVMe devices\n"
49 "nvme device [dev] - show or set current NVMe device\n"
50 "nvme part [dev] - print partition table of one or all NVMe devices\n"
51 "nvme read addr blk# cnt - read `cnt' blocks starting at block\n"
53 "nvme write addr blk# cnt - write `cnt' blocks starting at block\n"
|
| /openbmc/qemu/tests/qtest/ |
| H A D | nvme-test.c | 2 * QTest testcase for NVMe
16 #include "block/nvme.h"
27 QNvme *nvme = obj; in nvme_get_driver() local
30 return &nvme->dev; in nvme_get_driver()
33 fprintf(stderr, "%s not present in nvme\n", interface); in nvme_get_driver()
39 QNvme *nvme = g_new0(QNvme, 1); in nvme_create() local
42 qpci_device_init(&nvme->dev, bus, addr); in nvme_create()
43 nvme->obj.get_driver = nvme_get_driver; in nvme_create()
45 return &nvme->obj; in nvme_create()
52 QNvme *nvme = obj; in nvmetest_oob_cmb_test() local
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | KeyPolicy.v1_0_1.json | 109 "description": "NVMe-oF specific properties.",
110 …"longDescription": "This property shall contain NVMe-oF specific properties for this key policy. …
138 "NVMeoF": "An NVMe-oF key policy."
141 "NVMeoF": "This value shall indicate the key policy is for an NVMe-oF key."
147 "description": "NVMe-oF specific properties.",
148 … "longDescription": "This type shall contain NVMe-oF specific properties for a key policy.",
204 … contain the OEM-defined security protocols that this key policy allows. NVMe-oF channels are res…
236 …operty shall contain the security protocols that this key policy allows. NVMe-oF channels are res…
260 "description": "The NVMe cipher suites that a key is allowed to use.",
270 …as defined by the 'Mandatory and Recommended Cipher Suites' clause in the NVMe TCP Transport Speci…
[all …]
|
| H A D | StorageControllerMetrics.v1_0_3.json | 37 …"longDescription": "The object shall contain the NVMe-defined 'Endurance Group Critical Warning Su…
85 "description": "The NVMe SMART metrics.",
86 …"longDescription": "This object shall contain the NVMe SMART metrics as defined by the NVMe SMART/…
104 …"longDescription": "This property shall contain the NVMe-defined 'Available Spare', which represen…
116 …"longDescription": "This property shall contain the NVMe-defined 'Available Spare Threshold' as a …
128 …s for this storage controller. Services shall derive this value from the NVMe-defined 'Composite …
138 …"longDescription": "This property shall contain the NVMe-defined 'Controller Busy Time', which rep…
147 …"longDescription": "This property shall contain the NVMe-defined 'Critical Composite Temperature T…
156 "description": "The NVMe SMART critical warnings.",
157 … "longDescription": "The property shall contain the NVMe-defined 'Critical Warning'."
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | nvme-tcp.h | 3 * NVMe over Fabrics TCP protocol header.
10 #include <linux/nvme.h>
62 * struct nvme_tcp_hdr - nvme tcp pdu common header
79 * struct nvme_tcp_icreq_pdu - nvme tcp initialize connection request pdu
97 * struct nvme_tcp_icresp_pdu - nvme tcp initialize connection response pdu
115 * struct nvme_tcp_term_pdu - nvme tcp terminate connection pdu
130 * struct nvme_tcp_cmd_pdu - nvme tcp command capsule pdu
133 * @cmd: nvme command
141 * struct nvme_tcp_rsp_pdu - nvme tcp response capsule pdu
144 * @hdr: nvme-tcp generic header
[all …]
|
| H A D | nvme-fc-driver.h | 14 * ********************** FC-NVME LS API ********************
16 * Data structures used by both FC-NVME hosts and FC-NVME
17 * targets to perform FC-NVME LS requests or transmit
25 * to the LLDD to perform a NVME-FC LS request and obtain
27 * Used by nvme-fc transport (host) to send LS's such as
71 * to request the transmit the NVME-FC LS response to a
72 * NVME-FC LS request. The structure originates in the LLDD
75 * FC exchange context for the NVME-FC LS request that was
80 * Used by the LLDD to pass the nvme-fc transport (host)
86 * or nvme-fc layer via the xxx_rcv_ls_req() transport routines.
[all …]
|
| /openbmc/linux/drivers/scsi/qla2xxx/ |
| H A D | qla_nvme.c | 9 #include <linux/nvme.h>
10 #include <linux/nvme-fc.h>
47 "%s: Not registering target since Host NVME is not enabled\n", in qla_nvme_register_remote()
114 /* Allocate a queue for NVMe traffic */
170 struct srb_iocb *nvme; in qla_nvme_release_fcp_cmd_kref() local
176 nvme = &sp->u.iocb_cmd; in qla_nvme_release_fcp_cmd_kref()
177 fd = nvme->u.nvme.desc; in qla_nvme_release_fcp_cmd_kref()
183 fd->rcv_rsplen = le16_to_cpu(nvme->u.nvme.rsp_pyld_len); in qla_nvme_release_fcp_cmd_kref()
315 __func__, sp, sp->handle, fcport, sp->u.iocb_cmd.u.nvme.desc, fcport->deleted); in qla_nvme_abort_work()
374 struct srb_iocb *nvme; in qla_nvme_xmt_ls_rsp() local
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-bsp/nvme-cli/ |
| H A D | nvme-cli_2.11.bb | 1 SUMMARY = "NVMe management command line interface"
2 HOMEPAGE = "https://github.com/linux-nvme/nvme-cli"
11 SRC_URI = "git://github.com/linux-nvme/nvme-cli.git;branch=master;protocol=https \
12 file://0001-nvme-print-add-fallback-for-non-standard-locale-cate.patch \
22 ${sbindir}/nvme gen-hostnqn > ${sysconfdir}/nvme/hostnqn
23 ${bindir}/uuidgen > ${sysconfdir}/nvme/hostid
37 # git/plugins/virtium/virtium-nvme.c:205:63: error: passing argument 1 of 'localtime' from incompat…
|
| /openbmc/u-boot/include/ |
| H A D | nvme.h | 15 * This issues an identify command to the NVMe controller to return a data
18 * @dev: NVMe controller device
33 * @dev: NVMe controller device
49 * @dev: NVMe controller device
61 * nvme_scan_namespace - scan all namespaces attached to NVMe controllers
63 * This probes all registered NVMe uclass device drivers in the system,
64 * and tries to find all namespaces attached to the NVMe controllers.
71 * nvme_print_info - print detailed NVMe controller and namespace information
73 * This prints out detailed human readable NVMe controller and namespace
76 * @udev: NVMe controller device
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-bletchley/recipes-phosphor/sensors/ |
| H A D | phosphor-nvme_%.bbappend | 6 file://nvme-json-rewrite \
7 file://nvme-json-rewrite.conf \
15 install -m 0755 ${UNPACKDIR}/nvme-json-rewrite ${D}${libexecdir}/${PN}/
17 install -d ${D}${sysconfdir}/nvme
18 install -m 0644 -D ${UNPACKDIR}/nvme_config.json ${D}${sysconfdir}/nvme
22 nvme-json-rewrite.conf:xyz.openbmc_project.nvme.manager.service.d/nvme-json-rewrite.conf \
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | KeyPolicy_v1.xml | 77 <Annotation Term="OData.Description" String="NVMe-oF specific properties."/>
78 …<Annotation Term="OData.LongDescription" String="This property shall contain NVMe-oF specific prop…
88 <Annotation Term="OData.Description" String="An NVMe-oF key policy."/>
89 …="OData.LongDescription" String="This value shall indicate the key policy is for an NVMe-oF key."/>
95 <Annotation Term="OData.Description" String="NVMe-oF specific properties."/>
96 …<Annotation Term="OData.LongDescription" String="This type shall contain NVMe-oF specific properti…
100 …operty shall contain the security protocols that this key policy allows. NVMe-oF channels are res…
105 … contain the OEM-defined security protocols that this key policy allows. NVMe-oF channels are res…
130 …<Annotation Term="OData.Description" String="The NVMe security protocols that a key is allowed to …
131 …<Annotation Term="OData.LongDescription" String="This enumeration shall list the NVMe security pro…
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-bsp/nvme-cli/nvme-cli/ |
| H A D | 0001-nvme-print-add-fallback-for-non-standard-locale-cate.patch | 4 Subject: [PATCH] nvme-print: add fallback for non-standard locale category
16 Upstream-Status: Backport [https://github.com/linux-nvme/nvme-cli/commit/9444ce03a27b8d423f8170cf75…
19 nvme-print.c | 4 ++++
22 diff --git a/nvme-print.c b/nvme-print.c
24 --- a/nvme-print.c
25 +++ b/nvme-print.c
|
| H A D | 0002-plugins-netapp-add-include-of-libgen.h-for-basename-.patch | 14 Upstream-Status: Backport [https://github.com/linux-nvme/nvme-cli/commit/ac4818952c872ba465a2d0f486…
17 plugins/netapp/netapp-nvme.c | 1 +
20 diff --git a/plugins/netapp/netapp-nvme.c b/plugins/netapp/netapp-nvme.c
22 --- a/plugins/netapp/netapp-nvme.c
23 +++ b/plugins/netapp/netapp-nvme.c
31 #include "nvme.h"
|
| /openbmc/entity-manager/configurations/ |
| H A D | mtjefferson_bp.json | 18 "Name": "nvme$ADDRESS / 82 * 8 + 0",
24 "Name": "nvme$ADDRESS / 82 * 8 + 1",
30 "Name": "nvme$ADDRESS / 82 * 8 + 2",
36 "Name": "nvme$ADDRESS / 82 * 8 + 3",
42 "Name": "nvme$ADDRESS / 82 * 8 + 4",
48 "Name": "nvme$ADDRESS / 82 * 8 + 5",
54 "Name": "nvme$ADDRESS / 82 * 8 + 6",
60 "Name": "nvme$ADDRESS / 82 * 8 + 7",
|
| H A D | mtmitchell_bp.json | 12 "Name": "nvme$BUS % 100 * 8 + 0",
18 "Name": "nvme$BUS % 100 * 8 + 1",
24 "Name": "nvme$BUS % 100 * 8 + 2",
30 "Name": "nvme$BUS % 100 * 8 + 3",
36 "Name": "nvme$BUS % 100 * 8 + 4",
42 "Name": "nvme$BUS % 100 * 8 + 5",
48 "Name": "nvme$BUS % 100 * 8 + 6",
54 "Name": "nvme$BUS % 100 * 8 + 7",
|
| /openbmc/linux/drivers/scsi/lpfc/ |
| H A D | lpfc_nvme.c | 54 /* NVME initiator-based functions */
108 * NVME qidx == 0 is the admin queue, so both admin queue in lpfc_nvme_create_queue()
179 * @remoteport: Pointer to an nvme transport remoteport instance.
181 * This is a template downcall. NVME transport calls this function
213 * transport. Remove the ndlp reference for the NVME transport before in lpfc_nvme_remoteport_delete()
231 * NVME and SCSI rport unregister requests are complete. in lpfc_nvme_remoteport_delete()
241 * lpfc_nvme_handle_lsreq - Process an unsolicited NVME LS request
243 * @axchg: pointer to exchange context for the NVME LS request
245 * This routine is used for processing an asychronously received NVME LS
247 * to the nvme-fc transport via nvme_fc_rcv_ls_req().
[all …]
|