aboutsummaryrefslogtreecommitdiff
path: root/hw/net/vmxnet3_defs.h
diff options
context:
space:
mode:
authorYuval Shaia <yuval.shaia@oracle.com>2018-12-21 16:40:25 +0200
committerMarcel Apfelbaum <marcel.apfelbaum@gmail.com>2018-12-22 11:09:56 +0200
commit2b05705dc8ad80c09a3aa9cc70c14fb8323b0fd3 (patch)
treef3d3a9f7632b9fd1dcfa8a2dbdd83de617222289 /hw/net/vmxnet3_defs.h
parent4a5c9903f3164cef134e7f81b361b3fa7d5c0b52 (diff)
downloadqemu-2b05705dc8ad80c09a3aa9cc70c14fb8323b0fd3.zip
qemu-2b05705dc8ad80c09a3aa9cc70c14fb8323b0fd3.tar.gz
qemu-2b05705dc8ad80c09a3aa9cc70c14fb8323b0fd3.tar.bz2
hw/pvrdma: Add support to allow guest to configure GID table
The control over the RDMA device's GID table is done by updating the device's Ethernet function addresses. Usually the first GID entry is determined by the MAC address, the second by the first IPv6 address and the third by the IPv4 address. Other entries can be added by adding more IP addresses. The opposite is the same, i.e. whenever an address is removed, the corresponding GID entry is removed. The process is done by the network and RDMA stacks. Whenever an address is added the ib_core driver is notified and calls the device driver add_gid function which in turn update the device. To support this in pvrdma device we need to hook into the create_bind and destroy_bind HW commands triggered by pvrdma driver in guest. Whenever a change is made to the pvrdma port's GID table a special QMP message is sent to be processed by libvirt to update the address of the backend Ethernet device. Signed-off-by: Yuval Shaia <yuval.shaia@oracle.com> Reviewed-by: Marcel Apfelbaum<marcel.apfelbaum@gmail.com> Signed-off-by: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Diffstat (limited to 'hw/net/vmxnet3_defs.h')
0 files changed, 0 insertions, 0 deletions