Changeset View

Standalone View

	Show First 20 Lines • Show All 45 Lines • ▼ Show 20 Lines
	};			};
	#define VM_MEMMAP_F_WIRED 0x01			#define VM_MEMMAP_F_WIRED 0x01
	#define VM_MEMMAP_F_IOMMU 0x02			#define VM_MEMMAP_F_IOMMU 0x02

	#define VM_MEMSEG_NAME(m) ((m)->name[0] != '\0' ? (m)->name : NULL)			#define VM_MEMSEG_NAME(m) ((m)->name[0] != '\0' ? (m)->name : NULL)
	struct vm_memseg {			struct vm_memseg {
	int segid;			int segid;
	size_t len;			size_t len;
	char name[SPECNAMELEN + 1];			char name[VM_MAX_SUFFIXLEN + 1];
				jhbUnsubmitted Not Done Inline Actions I think this is an ABI change (this structure is used by an ioctl), so it wouldn't be MFC'able without some compat shims. It doesn't hurt to just leave this as SPECNAMELEN though, at least for an MFC. I don't think we try to let bhyve binaries from older stable branches work, but we probably want them to work if it's within the same stable branch. jhb: I think this is an ABI change (this structure is used by an ioctl), so it wouldn't be MFC'able…
				scottlAuthorUnsubmitted Done Inline Actions It was always bogus to use SPECNAMELEN here, but it's fine if this part doesn't get MFC'd as-is. scottl: It was always bogus to use SPECNAMELEN here, but it's fine if this part doesn't get MFC'd as-is.
	};			};

	struct vm_register {			struct vm_register {
	int cpuid;			int cpuid;
	int regnum; /* enum vm_reg_name */			int regnum; /* enum vm_reg_name */
	uint64_t regval;			uint64_t regval;
	};			};

	▲ Show 20 Lines • Show All 363 Lines • Show Last 20 Lines