Commit 5fc0df93 authored by Dave Airlie's avatar Dave Airlie

Merge v5.6 into drm-next

msm needed rc6, so I just went and merged release
(msm has been in drm-next outside of this tree)
Signed-off-by: default avatarDave Airlie <airlied@redhat.com>
parents 700d6ab9 7111951b
...@@ -86,6 +86,8 @@ ForEachMacros: ...@@ -86,6 +86,8 @@ ForEachMacros:
- 'bio_for_each_segment_all' - 'bio_for_each_segment_all'
- 'bio_list_for_each' - 'bio_list_for_each'
- 'bip_for_each_vec' - 'bip_for_each_vec'
- 'bitmap_for_each_clear_region'
- 'bitmap_for_each_set_region'
- 'blkg_for_each_descendant_post' - 'blkg_for_each_descendant_post'
- 'blkg_for_each_descendant_pre' - 'blkg_for_each_descendant_pre'
- 'blk_queue_for_each_rl' - 'blk_queue_for_each_rl'
...@@ -115,6 +117,7 @@ ForEachMacros: ...@@ -115,6 +117,7 @@ ForEachMacros:
- 'drm_client_for_each_connector_iter' - 'drm_client_for_each_connector_iter'
- 'drm_client_for_each_modeset' - 'drm_client_for_each_modeset'
- 'drm_connector_for_each_possible_encoder' - 'drm_connector_for_each_possible_encoder'
- 'drm_for_each_bridge_in_chain'
- 'drm_for_each_connector_iter' - 'drm_for_each_connector_iter'
- 'drm_for_each_crtc' - 'drm_for_each_crtc'
- 'drm_for_each_encoder' - 'drm_for_each_encoder'
...@@ -136,9 +139,10 @@ ForEachMacros: ...@@ -136,9 +139,10 @@ ForEachMacros:
- 'for_each_bio' - 'for_each_bio'
- 'for_each_board_func_rsrc' - 'for_each_board_func_rsrc'
- 'for_each_bvec' - 'for_each_bvec'
- 'for_each_card_auxs'
- 'for_each_card_auxs_safe'
- 'for_each_card_components' - 'for_each_card_components'
- 'for_each_card_links' - 'for_each_card_pre_auxs'
- 'for_each_card_links_safe'
- 'for_each_card_prelinks' - 'for_each_card_prelinks'
- 'for_each_card_rtds' - 'for_each_card_rtds'
- 'for_each_card_rtds_safe' - 'for_each_card_rtds_safe'
...@@ -166,6 +170,7 @@ ForEachMacros: ...@@ -166,6 +170,7 @@ ForEachMacros:
- 'for_each_dpcm_fe' - 'for_each_dpcm_fe'
- 'for_each_drhd_unit' - 'for_each_drhd_unit'
- 'for_each_dss_dev' - 'for_each_dss_dev'
- 'for_each_efi_handle'
- 'for_each_efi_memory_desc' - 'for_each_efi_memory_desc'
- 'for_each_efi_memory_desc_in_map' - 'for_each_efi_memory_desc_in_map'
- 'for_each_element' - 'for_each_element'
...@@ -190,6 +195,7 @@ ForEachMacros: ...@@ -190,6 +195,7 @@ ForEachMacros:
- 'for_each_lru' - 'for_each_lru'
- 'for_each_matching_node' - 'for_each_matching_node'
- 'for_each_matching_node_and_match' - 'for_each_matching_node_and_match'
- 'for_each_member'
- 'for_each_memblock' - 'for_each_memblock'
- 'for_each_memblock_type' - 'for_each_memblock_type'
- 'for_each_memcg_cache_index' - 'for_each_memcg_cache_index'
...@@ -200,9 +206,11 @@ ForEachMacros: ...@@ -200,9 +206,11 @@ ForEachMacros:
- 'for_each_msi_entry' - 'for_each_msi_entry'
- 'for_each_msi_entry_safe' - 'for_each_msi_entry_safe'
- 'for_each_net' - 'for_each_net'
- 'for_each_net_continue_reverse'
- 'for_each_netdev' - 'for_each_netdev'
- 'for_each_netdev_continue' - 'for_each_netdev_continue'
- 'for_each_netdev_continue_rcu' - 'for_each_netdev_continue_rcu'
- 'for_each_netdev_continue_reverse'
- 'for_each_netdev_feature' - 'for_each_netdev_feature'
- 'for_each_netdev_in_bond_rcu' - 'for_each_netdev_in_bond_rcu'
- 'for_each_netdev_rcu' - 'for_each_netdev_rcu'
...@@ -254,10 +262,10 @@ ForEachMacros: ...@@ -254,10 +262,10 @@ ForEachMacros:
- 'for_each_reserved_mem_region' - 'for_each_reserved_mem_region'
- 'for_each_rtd_codec_dai' - 'for_each_rtd_codec_dai'
- 'for_each_rtd_codec_dai_rollback' - 'for_each_rtd_codec_dai_rollback'
- 'for_each_rtdcom' - 'for_each_rtd_components'
- 'for_each_rtdcom_safe'
- 'for_each_set_bit' - 'for_each_set_bit'
- 'for_each_set_bit_from' - 'for_each_set_bit_from'
- 'for_each_set_clump8'
- 'for_each_sg' - 'for_each_sg'
- 'for_each_sg_dma_page' - 'for_each_sg_dma_page'
- 'for_each_sg_page' - 'for_each_sg_page'
...@@ -267,6 +275,7 @@ ForEachMacros: ...@@ -267,6 +275,7 @@ ForEachMacros:
- 'for_each_subelement_id' - 'for_each_subelement_id'
- '__for_each_thread' - '__for_each_thread'
- 'for_each_thread' - 'for_each_thread'
- 'for_each_wakeup_source'
- 'for_each_zone' - 'for_each_zone'
- 'for_each_zone_zonelist' - 'for_each_zone_zonelist'
- 'for_each_zone_zonelist_nodemask' - 'for_each_zone_zonelist_nodemask'
...@@ -330,6 +339,7 @@ ForEachMacros: ...@@ -330,6 +339,7 @@ ForEachMacros:
- 'list_for_each' - 'list_for_each'
- 'list_for_each_codec' - 'list_for_each_codec'
- 'list_for_each_codec_safe' - 'list_for_each_codec_safe'
- 'list_for_each_continue'
- 'list_for_each_entry' - 'list_for_each_entry'
- 'list_for_each_entry_continue' - 'list_for_each_entry_continue'
- 'list_for_each_entry_continue_rcu' - 'list_for_each_entry_continue_rcu'
...@@ -351,6 +361,7 @@ ForEachMacros: ...@@ -351,6 +361,7 @@ ForEachMacros:
- 'llist_for_each_entry' - 'llist_for_each_entry'
- 'llist_for_each_entry_safe' - 'llist_for_each_entry_safe'
- 'llist_for_each_safe' - 'llist_for_each_safe'
- 'mci_for_each_dimm'
- 'media_device_for_each_entity' - 'media_device_for_each_entity'
- 'media_device_for_each_intf' - 'media_device_for_each_intf'
- 'media_device_for_each_link' - 'media_device_for_each_link'
...@@ -444,10 +455,16 @@ ForEachMacros: ...@@ -444,10 +455,16 @@ ForEachMacros:
- 'virtio_device_for_each_vq' - 'virtio_device_for_each_vq'
- 'xa_for_each' - 'xa_for_each'
- 'xa_for_each_marked' - 'xa_for_each_marked'
- 'xa_for_each_range'
- 'xa_for_each_start' - 'xa_for_each_start'
- 'xas_for_each' - 'xas_for_each'
- 'xas_for_each_conflict' - 'xas_for_each_conflict'
- 'xas_for_each_marked' - 'xas_for_each_marked'
- 'xbc_array_for_each_value'
- 'xbc_for_each_key_value'
- 'xbc_node_for_each_array_value'
- 'xbc_node_for_each_child'
- 'xbc_node_for_each_key_value'
- 'zorro_for_each_dev' - 'zorro_for_each_dev'
#IncludeBlocks: Preserve # Unknown to clang-format-5.0 #IncludeBlocks: Preserve # Unknown to clang-format-5.0
......
...@@ -225,6 +225,7 @@ Pratyush Anand <pratyush.anand@gmail.com> <pratyush.anand@st.com> ...@@ -225,6 +225,7 @@ Pratyush Anand <pratyush.anand@gmail.com> <pratyush.anand@st.com>
Praveen BP <praveenbp@ti.com> Praveen BP <praveenbp@ti.com>
Punit Agrawal <punitagrawal@gmail.com> <punit.agrawal@arm.com> Punit Agrawal <punitagrawal@gmail.com> <punit.agrawal@arm.com>
Qais Yousef <qsyousef@gmail.com> <qais.yousef@imgtec.com> Qais Yousef <qsyousef@gmail.com> <qais.yousef@imgtec.com>
Quentin Monnet <quentin@isovalent.com> <quentin.monnet@netronome.com>
Quentin Perret <qperret@qperret.net> <quentin.perret@arm.com> Quentin Perret <qperret@qperret.net> <quentin.perret@arm.com>
Rafael J. Wysocki <rjw@rjwysocki.net> <rjw@sisk.pl> Rafael J. Wysocki <rjw@rjwysocki.net> <rjw@sisk.pl>
Rajesh Shah <rajesh.shah@intel.com> Rajesh Shah <rajesh.shah@intel.com>
......
...@@ -110,6 +110,8 @@ stable kernels. ...@@ -110,6 +110,8 @@ stable kernels.
+----------------+-----------------+-----------------+-----------------------------+ +----------------+-----------------+-----------------+-----------------------------+
| Cavium | ThunderX GICv3 | #23154 | CAVIUM_ERRATUM_23154 | | Cavium | ThunderX GICv3 | #23154 | CAVIUM_ERRATUM_23154 |
+----------------+-----------------+-----------------+-----------------------------+ +----------------+-----------------+-----------------+-----------------------------+
| Cavium | ThunderX GICv3 | #38539 | N/A |
+----------------+-----------------+-----------------+-----------------------------+
| Cavium | ThunderX Core | #27456 | CAVIUM_ERRATUM_27456 | | Cavium | ThunderX Core | #27456 | CAVIUM_ERRATUM_27456 |
+----------------+-----------------+-----------------+-----------------------------+ +----------------+-----------------+-----------------+-----------------------------+
| Cavium | ThunderX Core | #30115 | CAVIUM_ERRATUM_30115 | | Cavium | ThunderX Core | #30115 | CAVIUM_ERRATUM_30115 |
......
...@@ -23,6 +23,8 @@ properties: ...@@ -23,6 +23,8 @@ properties:
- items: - items:
- const: allwinner,sun7i-a20-crypto - const: allwinner,sun7i-a20-crypto
- const: allwinner,sun4i-a10-crypto - const: allwinner,sun4i-a10-crypto
- items:
- const: allwinner,sun8i-a33-crypto
reg: reg:
maxItems: 1 maxItems: 1
......
...@@ -5,6 +5,7 @@ Required properties: ...@@ -5,6 +5,7 @@ Required properties:
* "cypress,tm2-touchkey" - for the touchkey found on the tm2 board * "cypress,tm2-touchkey" - for the touchkey found on the tm2 board
* "cypress,midas-touchkey" - for the touchkey found on midas boards * "cypress,midas-touchkey" - for the touchkey found on midas boards
* "cypress,aries-touchkey" - for the touchkey found on aries boards * "cypress,aries-touchkey" - for the touchkey found on aries boards
* "coreriver,tc360-touchkey" - for the Coreriver TouchCore 360 touchkey
- reg: I2C address of the chip. - reg: I2C address of the chip.
- interrupts: interrupt to which the chip is connected (see interrupt - interrupts: interrupt to which the chip is connected (see interrupt
binding[0]). binding[0]).
......
...@@ -110,6 +110,13 @@ PROPERTIES ...@@ -110,6 +110,13 @@ PROPERTIES
Usage: required Usage: required
Definition: See soc/fsl/qman.txt and soc/fsl/bman.txt Definition: See soc/fsl/qman.txt and soc/fsl/bman.txt
- fsl,erratum-a050385
Usage: optional
Value type: boolean
Definition: A boolean property. Indicates the presence of the
erratum A050385 which indicates that DMA transactions that are
split can result in a FMan lock.
============================================================================= =============================================================================
FMan MURAM Node FMan MURAM Node
......
...@@ -205,6 +205,8 @@ patternProperties: ...@@ -205,6 +205,8 @@ patternProperties:
description: Colorful GRP, Shenzhen Xueyushi Technology Ltd. description: Colorful GRP, Shenzhen Xueyushi Technology Ltd.
"^compulab,.*": "^compulab,.*":
description: CompuLab Ltd. description: CompuLab Ltd.
"^coreriver,.*":
description: CORERIVER Semiconductor Co.,Ltd.
"^corpro,.*": "^corpro,.*":
description: Chengdu Corpro Technology Co., Ltd. description: Chengdu Corpro Technology Co., Ltd.
"^cortina,.*": "^cortina,.*":
......
...@@ -266,11 +266,15 @@ to use. ...@@ -266,11 +266,15 @@ to use.
attached (via the dmaengine_desc_attach_metadata() helper to the descriptor. attached (via the dmaengine_desc_attach_metadata() helper to the descriptor.
From the DMA driver the following is expected for this mode: From the DMA driver the following is expected for this mode:
- DMA_MEM_TO_DEV / DEV_MEM_TO_MEM - DMA_MEM_TO_DEV / DEV_MEM_TO_MEM
The data from the provided metadata buffer should be prepared for the DMA The data from the provided metadata buffer should be prepared for the DMA
controller to be sent alongside of the payload data. Either by copying to a controller to be sent alongside of the payload data. Either by copying to a
hardware descriptor, or highly coupled packet. hardware descriptor, or highly coupled packet.
- DMA_DEV_TO_MEM - DMA_DEV_TO_MEM
On transfer completion the DMA driver must copy the metadata to the client On transfer completion the DMA driver must copy the metadata to the client
provided metadata buffer before notifying the client about the completion. provided metadata buffer before notifying the client about the completion.
After the transfer completion, DMA drivers must not touch the metadata After the transfer completion, DMA drivers must not touch the metadata
...@@ -284,10 +288,14 @@ to use. ...@@ -284,10 +288,14 @@ to use.
and dmaengine_desc_set_metadata_len() is provided as helper functions. and dmaengine_desc_set_metadata_len() is provided as helper functions.
From the DMA driver the following is expected for this mode: From the DMA driver the following is expected for this mode:
- get_metadata_ptr
- get_metadata_ptr()
Should return a pointer for the metadata buffer, the maximum size of the Should return a pointer for the metadata buffer, the maximum size of the
metadata buffer and the currently used / valid (if any) bytes in the buffer. metadata buffer and the currently used / valid (if any) bytes in the buffer.
- set_metadata_len
- set_metadata_len()
It is called by the clients after it have placed the metadata to the buffer It is called by the clients after it have placed the metadata to the buffer
to let the DMA driver know the number of valid bytes provided. to let the DMA driver know the number of valid bytes provided.
......
...@@ -850,3 +850,11 @@ business doing so. ...@@ -850,3 +850,11 @@ business doing so.
d_alloc_pseudo() is internal-only; uses outside of alloc_file_pseudo() are d_alloc_pseudo() is internal-only; uses outside of alloc_file_pseudo() are
very suspect (and won't work in modules). Such uses are very likely to very suspect (and won't work in modules). Such uses are very likely to
be misspelled d_alloc_anon(). be misspelled d_alloc_anon().
---
**mandatory**
[should've been added in 2016] stale comment in finish_open() nonwithstanding,
failure exits in ->atomic_open() instances should *NOT* fput() the file,
no matter what. Everything is handled by the caller.
...@@ -258,11 +258,11 @@ conditions. ...@@ -258,11 +258,11 @@ conditions.
| option | condition | size read write read write | | option | condition | size read write read write |
+--------------+-----------+-----------------------------------------+ +--------------+-----------+-----------------------------------------+
| | good | fixed yes no yes yes | | | good | fixed yes no yes yes |
| remount-ro | read-only | fixed yes no yes no | | remount-ro | read-only | as is yes no yes no |
| (default) | offline | 0 no no no no | | (default) | offline | 0 no no no no |
+--------------+-----------+-----------------------------------------+ +--------------+-----------+-----------------------------------------+
| | good | fixed yes no yes yes | | | good | fixed yes no yes yes |
| zone-ro | read-only | fixed yes no yes no | | zone-ro | read-only | as is yes no yes no |
| | offline | 0 no no no no | | | offline | 0 no no no no |
+--------------+-----------+-----------------------------------------+ +--------------+-----------+-----------------------------------------+
| | good | 0 no no yes yes | | | good | 0 no no yes yes |
...@@ -270,7 +270,7 @@ conditions. ...@@ -270,7 +270,7 @@ conditions.
| | offline | 0 no no no no | | | offline | 0 no no no no |
+--------------+-----------+-----------------------------------------+ +--------------+-----------+-----------------------------------------+
| | good | fixed yes yes yes yes | | | good | fixed yes yes yes yes |
| repair | read-only | fixed yes no yes no | | repair | read-only | as is yes no yes no |
| | offline | 0 no no no no | | | offline | 0 no no no no |
+--------------+-----------+-----------------------------------------+ +--------------+-----------+-----------------------------------------+
...@@ -307,8 +307,16 @@ condition changes. The defined behaviors are as follow: ...@@ -307,8 +307,16 @@ condition changes. The defined behaviors are as follow:
* zone-offline * zone-offline
* repair * repair
The I/O error actions defined for each behavior are detailed in the previous The run-time I/O error actions defined for each behavior are detailed in the
section. previous section. Mount time I/O errors will cause the mount operation to fail.
The handling of read-only zones also differs between mount-time and run-time.
If a read-only zone is found at mount time, the zone is always treated in the
same manner as offline zones, that is, all accesses are disabled and the zone
file size set to 0. This is necessary as the write pointer of read-only zones
is defined as invalib by the ZBC and ZAC standards, making it impossible to
discover the amount of data that has been written to the zone. In the case of a
read-only zone discovered at run-time, as indicated in the previous section.
the size of the zone file is left unchanged from its last updated value.
Zonefs User Space Tools Zonefs User Space Tools
======================= =======================
......
...@@ -237,7 +237,7 @@ This is solely useful to speed up test compiles. ...@@ -237,7 +237,7 @@ This is solely useful to speed up test compiles.
KBUILD_EXTRA_SYMBOLS KBUILD_EXTRA_SYMBOLS
-------------------- --------------------
For modules that use symbols from other modules. For modules that use symbols from other modules.
See more details in modules.txt. See more details in modules.rst.
ALLSOURCE_ARCHS ALLSOURCE_ARCHS
--------------- ---------------
......
...@@ -44,7 +44,7 @@ intermediate:: ...@@ -44,7 +44,7 @@ intermediate::
def_bool y def_bool y
Then, Kconfig moves onto the evaluation stage to resolve inter-symbol Then, Kconfig moves onto the evaluation stage to resolve inter-symbol
dependency as explained in kconfig-language.txt. dependency as explained in kconfig-language.rst.
Variables Variables
......
...@@ -924,7 +924,7 @@ When kbuild executes, the following steps are followed (roughly): ...@@ -924,7 +924,7 @@ When kbuild executes, the following steps are followed (roughly):
$(KBUILD_AFLAGS_MODULE) is used to add arch-specific options that $(KBUILD_AFLAGS_MODULE) is used to add arch-specific options that
are used for assembler. are used for assembler.
From commandline AFLAGS_MODULE shall be used (see kbuild.txt). From commandline AFLAGS_MODULE shall be used (see kbuild.rst).
KBUILD_CFLAGS_KERNEL KBUILD_CFLAGS_KERNEL
$(CC) options specific for built-in $(CC) options specific for built-in
...@@ -937,7 +937,7 @@ When kbuild executes, the following steps are followed (roughly): ...@@ -937,7 +937,7 @@ When kbuild executes, the following steps are followed (roughly):
$(KBUILD_CFLAGS_MODULE) is used to add arch-specific options that $(KBUILD_CFLAGS_MODULE) is used to add arch-specific options that
are used for $(CC). are used for $(CC).
From commandline CFLAGS_MODULE shall be used (see kbuild.txt). From commandline CFLAGS_MODULE shall be used (see kbuild.rst).
KBUILD_LDFLAGS_MODULE KBUILD_LDFLAGS_MODULE
Options for $(LD) when linking modules Options for $(LD) when linking modules
...@@ -945,7 +945,7 @@ When kbuild executes, the following steps are followed (roughly): ...@@ -945,7 +945,7 @@ When kbuild executes, the following steps are followed (roughly):
$(KBUILD_LDFLAGS_MODULE) is used to add arch-specific options $(KBUILD_LDFLAGS_MODULE) is used to add arch-specific options
used when linking modules. This is often a linker script. used when linking modules. This is often a linker script.
From commandline LDFLAGS_MODULE shall be used (see kbuild.txt). From commandline LDFLAGS_MODULE shall be used (see kbuild.rst).
KBUILD_LDS KBUILD_LDS
......
...@@ -470,9 +470,9 @@ build. ...@@ -470,9 +470,9 @@ build.
The syntax of the Module.symvers file is:: The syntax of the Module.symvers file is::
<CRC> <Symbol> <Namespace> <Module> <Export Type> <CRC> <Symbol> <Module> <Export Type> <Namespace>
0xe1cc2a05 usb_stor_suspend USB_STORAGE drivers/usb/storage/usb-storage EXPORT_SYMBOL_GPL 0xe1cc2a05 usb_stor_suspend drivers/usb/storage/usb-storage EXPORT_SYMBOL_GPL USB_STORAGE
The fields are separated by tabs and values may be empty (e.g. The fields are separated by tabs and values may be empty (e.g.
if no namespace is defined for an exported symbol). if no namespace is defined for an exported symbol).
......
...@@ -40,9 +40,6 @@ example usage ...@@ -40,9 +40,6 @@ example usage
# Delete a snapshot using: # Delete a snapshot using:
$ devlink region del pci/0000:00:05.0/cr-space snapshot 1 $ devlink region del pci/0000:00:05.0/cr-space snapshot 1
# Trigger (request) a snapshot be taken:
$ devlink region trigger pci/0000:00:05.0/cr-space
# Dump a snapshot: # Dump a snapshot:
$ devlink region dump pci/0000:00:05.0/fw-health snapshot 1 $ devlink region dump pci/0000:00:05.0/fw-health snapshot 1
0000000000000000 0014 95dc 0014 9514 0035 1670 0034 db30 0000000000000000 0014 95dc 0014 9514 0035 1670 0034 db30
......
...@@ -8,9 +8,9 @@ Overview ...@@ -8,9 +8,9 @@ Overview
======== ========
The net_failover driver provides an automated failover mechanism via APIs The net_failover driver provides an automated failover mechanism via APIs
to create and destroy a failover master netdev and mananges a primary and to create and destroy a failover master netdev and manages a primary and
standby slave netdevs that get registered via the generic failover standby slave netdevs that get registered via the generic failover
infrastructrure. infrastructure.
The failover netdev acts a master device and controls 2 slave devices. The The failover netdev acts a master device and controls 2 slave devices. The
original paravirtual interface is registered as 'standby' slave netdev and original paravirtual interface is registered as 'standby' slave netdev and
...@@ -29,7 +29,7 @@ virtio-net accelerated datapath: STANDBY mode ...@@ -29,7 +29,7 @@ virtio-net accelerated datapath: STANDBY mode
============================================= =============================================
net_failover enables hypervisor controlled accelerated datapath to virtio-net net_failover enables hypervisor controlled accelerated datapath to virtio-net
enabled VMs in a transparent manner with no/minimal guest userspace chanages. enabled VMs in a transparent manner with no/minimal guest userspace changes.
To support this, the hypervisor needs to enable VIRTIO_NET_F_STANDBY To support this, the hypervisor needs to enable VIRTIO_NET_F_STANDBY
feature on the virtio-net interface and assign the same MAC address to both feature on the virtio-net interface and assign the same MAC address to both
......
...@@ -159,7 +159,7 @@ Socket Interface ...@@ -159,7 +159,7 @@ Socket Interface
set SO_RDS_TRANSPORT on a socket for which the transport has set SO_RDS_TRANSPORT on a socket for which the transport has
been previously attached explicitly (by SO_RDS_TRANSPORT) or been previously attached explicitly (by SO_RDS_TRANSPORT) or
implicitly (via bind(2)) will return an error of EOPNOTSUPP. implicitly (via bind(2)) will return an error of EOPNOTSUPP.
An attempt to set SO_RDS_TRANSPPORT to RDS_TRANS_NONE will An attempt to set SO_RDS_TRANSPORT to RDS_TRANS_NONE will
always return EINVAL. always return EINVAL.
RDMA for RDS RDMA for RDS
......
...@@ -53,6 +53,29 @@ key management interface to perform common hypervisor activities such as ...@@ -53,6 +53,29 @@ key management interface to perform common hypervisor activities such as
encrypting bootstrap code, snapshot, migrating and debugging the guest. For more encrypting bootstrap code, snapshot, migrating and debugging the guest. For more
information, see the SEV Key Management spec [api-spec]_ information, see the SEV Key Management spec [api-spec]_
The main ioctl to access SEV is KVM_MEM_ENCRYPT_OP. If the argument
to KVM_MEM_ENCRYPT_OP is NULL, the ioctl returns 0 if SEV is enabled
and ``ENOTTY` if it is disabled (on some older versions of Linux,
the ioctl runs normally even with a NULL argument, and therefore will
likely return ``EFAULT``). If non-NULL, the argument to KVM_MEM_ENCRYPT_OP
must be a struct kvm_sev_cmd::
struct kvm_sev_cmd {
__u32 id;
__u64 data;
__u32 error;
__u32 sev_fd;
};
The ``id`` field contains the subcommand, and the ``data`` field points to
another struct containing arguments specific to command. The ``sev_fd``
should point to a file descriptor that is opened on the ``/dev/sev``
device, if needed (see individual commands).
On output, ``error`` is zero on success, or an error code. Error codes
are defined in ``<linux/psp-dev.h>`.
KVM implements the following commands to support common lifecycle events of SEV KVM implements the following commands to support common lifecycle events of SEV
guests, such as launching, running, snapshotting, migrating and decommissioning. guests, such as launching, running, snapshotting, migrating and decommissioning.
...@@ -90,6 +113,8 @@ Returns: 0 on success, -negative on error ...@@ -90,6 +113,8 @@ Returns: 0 on success, -negative on error
On success, the 'handle' field contains a new handle and on error, a negative value. On success, the 'handle' field contains a new handle and on error, a negative value.
KVM_SEV_LAUNCH_START requires the ``sev_fd`` field to be valid.
For more details, see SEV spec Section 6.2. For more details, see SEV spec Section 6.2.
3. KVM_SEV_LAUNCH_UPDATE_DATA 3. KVM_SEV_LAUNCH_UPDATE_DATA
......
...@@ -4073,7 +4073,6 @@ F: drivers/scsi/snic/ ...@@ -4073,7 +4073,6 @@ F: drivers/scsi/snic/
CISCO VIC ETHERNET NIC DRIVER CISCO VIC ETHERNET NIC DRIVER
M: Christian Benvenuti <benve@cisco.com> M: Christian Benvenuti <benve@cisco.com>
M: Govindarajulu Varadarajan <_govind@gmx.com> M: Govindarajulu Varadarajan <_govind@gmx.com>
M: Parvi Kaustubhi <pkaustub@cisco.com>
S: Supported S: Supported
F: drivers/net/ethernet/cisco/enic/ F: drivers/net/ethernet/cisco/enic/
...@@ -4572,7 +4571,7 @@ F: drivers/infiniband/hw/cxgb4/ ...@@ -4572,7 +4571,7 @@ F: drivers/infiniband/hw/cxgb4/
F: include/uapi/rdma/cxgb4-abi.h F: include/uapi/rdma/cxgb4-abi.h
CXGB4VF ETHERNET DRIVER (CXGB4VF) CXGB4VF ETHERNET DRIVER (CXGB4VF)
M: Casey Leedom <leedom@chelsio.com> M: Vishal Kulkarni <vishal@gmail.com>
L: netdev@vger.kernel.org L: netdev@vger.kernel.org
W: http://www.chelsio.com W: http://www.chelsio.com
S: Supported S: Supported
...@@ -6230,7 +6229,6 @@ S: Supported ...@@ -6230,7 +6229,6 @@ S: Supported
F: drivers/scsi/be2iscsi/ F: drivers/scsi/be2iscsi/
Emulex 10Gbps NIC BE2, BE3-R, Lancer, Skyhawk-R DRIVER (be2net) Emulex 10Gbps NIC BE2, BE3-R, Lancer, Skyhawk-R DRIVER (be2net)
M: Sathya Perla <sathya.perla@broadcom.com>
M: Ajit Khaparde <ajit.khaparde@broadcom.com> M: Ajit Khaparde <ajit.khaparde@broadcom.com>
M: Sriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>