The VMADDR_CID_RESERVED (1) was used by VMCI, but now it is not used anymore, so we can reuse it for local communication (loopback) adding the new well-know CID: VMADDR_CID_LOCAL.
Showing the changes to include/uapi/linux (1 of 2 files). Show all
Unified · Split
| @@ -99,11 +99,13 @@ · 98 unmodified lines | |||
| 99 | 99 | ||
| 100 | #define VMADDR_CID_HYPERVISOR 0 | 100 | #define VMADDR_CID_HYPERVISOR 0 |
| 101 | 101 | ||
| 102 | /* This CID is specific to VMCI and can be considered reserved (even VMCI | 102 | /* Use this as the destination CID in an address when referring to the |
| 103 | * doesn't use it anymore, it's a legacy value from an older release). | 103 | * local communication (loopback). |
| 104 | * (This was VMADDR_CID_RESERVED, but even VMCI doesn't use it anymore, | ||
| 105 | * it was a legacy value from an older release). | ||
| 104 | */ | 106 | */ |
| 105 | 107 | ||
| 106 | #define VMADDR_CID_RESERVED 1 | 108 | #define VMADDR_CID_LOCAL 1 |
| 107 | 109 | ||
| 108 | /* Use this as the destination CID in an address when referring to the host | 110 | /* Use this as the destination CID in an address when referring to the host |
| 109 | * (any process other than the hypervisor). VMCI relies on it being 2, but | 111 | * (any process other than the hypervisor). VMCI relies on it being 2, but |