| .. | .. |
|---|
| 119 | 119 | |
|---|
| 120 | 120 | struct hv_fcopy_hdr { |
|---|
| 121 | 121 | __u32 operation; |
|---|
| 122 | | - uuid_le service_id0; /* currently unused */ |
|---|
| 123 | | - uuid_le service_id1; /* currently unused */ |
|---|
| 122 | + __u8 service_id0[16]; /* currently unused */ |
|---|
| 123 | + __u8 service_id1[16]; /* currently unused */ |
|---|
| 124 | 124 | } __attribute__((packed)); |
|---|
| 125 | 125 | |
|---|
| 126 | 126 | #define OVER_WRITE 0x1 |
|---|
| .. | .. |
|---|
| 219 | 219 | * kernel and user-level daemon communicate using a connector channel. |
|---|
| 220 | 220 | * |
|---|
| 221 | 221 | * The user mode component first registers with the |
|---|
| 222 | | - * the kernel component. Subsequently, the kernel component requests, data |
|---|
| 222 | + * kernel component. Subsequently, the kernel component requests, data |
|---|
| 223 | 223 | * for the specified keys. In response to this message the user mode component |
|---|
| 224 | 224 | * fills in the value corresponding to the specified key. We overload the |
|---|
| 225 | 225 | * sequence field in the cn_msg header to define our KVP message types. |
|---|