2007-05-09 01:00:38 +00:00
|
|
|
obj-$(CONFIG_MLX4_CORE) += mlx4_core.o
|
|
|
|
|
|
|
|
|
|
mlx4_core-y := alloc.o catas.o cmd.o cq.o eq.o fw.o icm.o intf.o main.o mcg.o \
|
mlx4_core: resource tracking for HCA resources used by guests
The resource tracker is used to track usage of HCA resources by the different
guests.
Virtual functions (VFs) are attached to guest operating systems but
resources are allocated from the same pool and are assigned to VFs. It is
essential that hostile/buggy guests not be able to affect the operation of
other VFs, possibly attached to other guest OSs since ConnectX firmware is not
tolerant to misuse of resources.
The resource tracker module associates each resource with a VF and maintains
state information for the allocated object. It also defines allowed state
transitions and enforces them.
Relationships between resources are also referred to. For example, CQs are
pointed to by QPs, so it is forbidden to destroy a CQ if a QP refers to it.
ICM memory is always accessible through the primary function and hence it is
allocated by the owner of the primary function.
When a guest dies, an FLR is generated for all the VFs it owns and all the
resources it used are freed.
The tracked resource types are: QPs, CQs, SRQs, MPTs, MTTs, MACs, RES_EQs,
and XRCDNs.
Signed-off-by: Eli Cohen <eli@mellanox.co.il>
Signed-off-by: Jack Morgenstein <jackm@dev.mellanox.co.il>
Signed-off-by: David S. Miller <davem@davemloft.net>
2011-12-13 04:15:24 +00:00
|
|
|
mr.o pd.o port.o profile.o qp.o reset.o sense.o srq.o resource_tracker.o
|
2008-10-22 22:47:49 +00:00
|
|
|
|
|
|
|
|
obj-$(CONFIG_MLX4_EN) += mlx4_en.o
|
|
|
|
|
|
2009-06-01 23:21:20 +00:00
|
|
|
mlx4_en-y := en_main.o en_tx.o en_rx.o en_ethtool.o en_port.o en_cq.o \
|
2010-08-24 03:46:18 +00:00
|
|
|
en_resources.o en_netdev.o en_selftest.o
|
2012-04-04 21:33:26 +00:00
|
|
|
mlx4_en-$(CONFIG_MLX4_EN_DCB) += en_dcb_nl.o
|
