Page MenuHomeFreeBSD
Differential D35769

Eliminate unroll_link from iommu_map_entry
ClosedPublic
Actions

Authored by alc on Jul 11 2022, 7:39 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Mar 7, 9:27 AM
Unknown Object (File)
Feb 10 2025, 7:25 AM
Unknown Object (File)
Feb 4 2025, 12:25 PM
Unknown Object (File)
Jan 29 2025, 12:14 AM
Unknown Object (File)
Jan 27 2025, 2:32 PM
Unknown Object (File)
Nov 19 2024, 1:41 AM
Unknown Object (File)
Nov 19 2024, 1:39 AM
Unknown Object (File)
Nov 18 2024, 11:41 PM
View All 32 Files
Subscribers
imp

Details

Reviewers
kib
Commits
rGf2453156ddfe: iommu: Shrink the iommu map entry structure
rGdb0110a536bf: iommu: Shrink the iommu map entry structure
Summary

iommu_bus_dmamap_load_something{,1}() can easily do without it, and domain_init_rmrr() can use dmamap_link.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Revision Contents
Changeset List

PathSize
sys/
dev/
iommu/
33 lines
2 lines
x86/
iommu/
4 lines
2 lines

Diff 108219

View Options

sys/dev/iommu/busdma_iommu.c

Show First 20 Lines • Show All 838 Lines • ▼ Show 20 Lines
.El .El
.Ss Netgraph Message Structure .Ss Netgraph Message Structure
Control messages have the following structure: Control messages have the following structure:
.Bd -literal .Bd -literal
#define NG_CMDSTRSIZ 32 /* Max command string (including null) */ #define NG_CMDSTRSIZ 32 /* Max command string (including null) */
struct ng_mesg { struct ng_mesg {
struct ng_msghdr { struct ng_msghdr {
u_char version; /* Must equal NG_VERSION */ u_char version; /* Must equal NGM_VERSION */
u_char spare; /* Pad to 4 bytes */ u_char spare; /* Pad to 4 bytes */
uint16_t spare2; uint16_t spare2;
uint32_t arglen; /* Length of cmd/resp data */ uint32_t arglen; /* Length of cmd/resp data */
uint32_t cmd; /* Command identifier */ uint32_t cmd; /* Command identifier */
uint32_t flags; /* Message status flags */ uint32_t flags; /* Message status flags */
uint32_t token; /* Reply should have the same token */ uint32_t token; /* Reply should have the same token */
uint32_t typecookie; /* Node type understanding this message */ uint32_t typecookie; /* Node type understanding this message */
u_char cmdstr[NG_CMDSTRSIZ]; /* cmd string + \0 */ u_char cmdstr[NG_CMDSTRSIZ]; /* cmd string + \0 */
} header; } header;
char data[]; /* placeholder for actual data */ char data[]; /* placeholder for actual data */
}; };
#define NG_ABI_VERSION 12 /* Netgraph kernel ABI version */ #define NG_ABI_VERSION 12 /* Netgraph kernel ABI version */
#define NG_VERSION 8 /* Netgraph message version */ #define NGM_VERSION 8 /* Netgraph message version */
#define NGF_ORIG 0x00000000 /* The msg is the original request */
#define NGF_RESP 0x00000001 /* The message is a response */ #define NGF_RESP 0x00000001 /* The message is a response */
.Ed .Ed
.Pp .Pp
Control messages have the fixed header shown above, followed by a Control messages have the fixed header shown above, followed by a
variable length data section which depends on the type cookie variable length data section which depends on the type cookie
and the command. and the command.
Each field is explained below: Each field is explained below:
.Bl -tag -width indent .Bl -tag -width indent
.It Va version .It Va version
Indicates the version of the Indicates the version of the
.Nm .Nm
message protocol itself. message protocol itself.
The current version is The current version is
.Dv NG_VERSION . .Dv NGM_VERSION .
.It Va arglen .It Va arglen
This is the length of any extra arguments, which begin at This is the length of any extra arguments, which begin at
.Va data . .Va data .
.It Va flags .It Va flags
Indicates whether this is a command or a response control message. Indicates whether this is a command or a response control message.
.It Va token .It Va token
The The
.Va token .Va token
▲ Show 20 Lines • Show All 600 Lines • Show Last 20 Lines
View Options

sys/dev/iommu/iommu.h

Show First 20 Lines • Show All 838 Lines • ▼ Show 20 Lines
.El .El
.Ss Netgraph Message Structure .Ss Netgraph Message Structure
Control messages have the following structure: Control messages have the following structure:
.Bd -literal .Bd -literal
#define NG_CMDSTRSIZ 32 /* Max command string (including null) */ #define NG_CMDSTRSIZ 32 /* Max command string (including null) */
struct ng_mesg { struct ng_mesg {
struct ng_msghdr { struct ng_msghdr {
u_char version; /* Must equal NG_VERSION */ u_char version; /* Must equal NGM_VERSION */
u_char spare; /* Pad to 4 bytes */ u_char spare; /* Pad to 4 bytes */
uint16_t spare2; uint16_t spare2;
uint32_t arglen; /* Length of cmd/resp data */ uint32_t arglen; /* Length of cmd/resp data */
uint32_t cmd; /* Command identifier */ uint32_t cmd; /* Command identifier */
uint32_t flags; /* Message status flags */ uint32_t flags; /* Message status flags */
uint32_t token; /* Reply should have the same token */ uint32_t token; /* Reply should have the same token */
uint32_t typecookie; /* Node type understanding this message */ uint32_t typecookie; /* Node type understanding this message */
u_char cmdstr[NG_CMDSTRSIZ]; /* cmd string + \0 */ u_char cmdstr[NG_CMDSTRSIZ]; /* cmd string + \0 */
} header; } header;
char data[]; /* placeholder for actual data */ char data[]; /* placeholder for actual data */
}; };
#define NG_ABI_VERSION 12 /* Netgraph kernel ABI version */ #define NG_ABI_VERSION 12 /* Netgraph kernel ABI version */
#define NG_VERSION 8 /* Netgraph message version */ #define NGM_VERSION 8 /* Netgraph message version */
#define NGF_ORIG 0x00000000 /* The msg is the original request */
#define NGF_RESP 0x00000001 /* The message is a response */ #define NGF_RESP 0x00000001 /* The message is a response */
.Ed .Ed
.Pp .Pp
Control messages have the fixed header shown above, followed by a Control messages have the fixed header shown above, followed by a
variable length data section which depends on the type cookie variable length data section which depends on the type cookie
and the command. and the command.
Each field is explained below: Each field is explained below:
.Bl -tag -width indent .Bl -tag -width indent
.It Va version .It Va version
Indicates the version of the Indicates the version of the
.Nm .Nm
message protocol itself. message protocol itself.
The current version is The current version is
.Dv NG_VERSION . .Dv NGM_VERSION .
.It Va arglen .It Va arglen
This is the length of any extra arguments, which begin at This is the length of any extra arguments, which begin at
.Va data . .Va data .
.It Va flags .It Va flags
Indicates whether this is a command or a response control message. Indicates whether this is a command or a response control message.
.It Va token .It Va token
The The
.Va token .Va token
▲ Show 20 Lines • Show All 600 Lines • Show Last 20 Lines
View Options

sys/x86/iommu/intel_ctx.c

Show First 20 Lines • Show All 838 Lines • ▼ Show 20 Lines
.El .El
.Ss Netgraph Message Structure .Ss Netgraph Message Structure
Control messages have the following structure: Control messages have the following structure:
.Bd -literal .Bd -literal
#define NG_CMDSTRSIZ 32 /* Max command string (including null) */ #define NG_CMDSTRSIZ 32 /* Max command string (including null) */
struct ng_mesg { struct ng_mesg {
struct ng_msghdr { struct ng_msghdr {
u_char version; /* Must equal NG_VERSION */ u_char version; /* Must equal NGM_VERSION */
u_char spare; /* Pad to 4 bytes */ u_char spare; /* Pad to 4 bytes */
uint16_t spare2; uint16_t spare2;
uint32_t arglen; /* Length of cmd/resp data */ uint32_t arglen; /* Length of cmd/resp data */
uint32_t cmd; /* Command identifier */ uint32_t cmd; /* Command identifier */
uint32_t flags; /* Message status flags */ uint32_t flags; /* Message status flags */
uint32_t token; /* Reply should have the same token */ uint32_t token; /* Reply should have the same token */
uint32_t typecookie; /* Node type understanding this message */ uint32_t typecookie; /* Node type understanding this message */
u_char cmdstr[NG_CMDSTRSIZ]; /* cmd string + \0 */ u_char cmdstr[NG_CMDSTRSIZ]; /* cmd string + \0 */
} header; } header;
char data[]; /* placeholder for actual data */ char data[]; /* placeholder for actual data */
}; };
#define NG_ABI_VERSION 12 /* Netgraph kernel ABI version */ #define NG_ABI_VERSION 12 /* Netgraph kernel ABI version */
#define NG_VERSION 8 /* Netgraph message version */ #define NGM_VERSION 8 /* Netgraph message version */
#define NGF_ORIG 0x00000000 /* The msg is the original request */
#define NGF_RESP 0x00000001 /* The message is a response */ #define NGF_RESP 0x00000001 /* The message is a response */
.Ed .Ed
.Pp .Pp
Control messages have the fixed header shown above, followed by a Control messages have the fixed header shown above, followed by a
variable length data section which depends on the type cookie variable length data section which depends on the type cookie
and the command. and the command.
Each field is explained below: Each field is explained below:
.Bl -tag -width indent .Bl -tag -width indent
.It Va version .It Va version
Indicates the version of the Indicates the version of the
.Nm .Nm
message protocol itself. message protocol itself.
The current version is The current version is
.Dv NG_VERSION . .Dv NGM_VERSION .
.It Va arglen .It Va arglen
This is the length of any extra arguments, which begin at This is the length of any extra arguments, which begin at
.Va data . .Va data .
.It Va flags .It Va flags
Indicates whether this is a command or a response control message. Indicates whether this is a command or a response control message.
.It Va token .It Va token
The The
.Va token .Va token
▲ Show 20 Lines • Show All 600 Lines • Show Last 20 Lines
View Options

sys/x86/iommu/intel_drv.c

Show First 20 Lines • Show All 838 Lines • ▼ Show 20 Lines
.El .El
.Ss Netgraph Message Structure .Ss Netgraph Message Structure
Control messages have the following structure: Control messages have the following structure:
.Bd -literal .Bd -literal
#define NG_CMDSTRSIZ 32 /* Max command string (including null) */ #define NG_CMDSTRSIZ 32 /* Max command string (including null) */
struct ng_mesg { struct ng_mesg {
struct ng_msghdr { struct ng_msghdr {
u_char version; /* Must equal NG_VERSION */ u_char version; /* Must equal NGM_VERSION */
u_char spare; /* Pad to 4 bytes */ u_char spare; /* Pad to 4 bytes */
uint16_t spare2; uint16_t spare2;
uint32_t arglen; /* Length of cmd/resp data */ uint32_t arglen; /* Length of cmd/resp data */
uint32_t cmd; /* Command identifier */ uint32_t cmd; /* Command identifier */
uint32_t flags; /* Message status flags */ uint32_t flags; /* Message status flags */
uint32_t token; /* Reply should have the same token */ uint32_t token; /* Reply should have the same token */
uint32_t typecookie; /* Node type understanding this message */ uint32_t typecookie; /* Node type understanding this message */
u_char cmdstr[NG_CMDSTRSIZ]; /* cmd string + \0 */ u_char cmdstr[NG_CMDSTRSIZ]; /* cmd string + \0 */
} header; } header;
char data[]; /* placeholder for actual data */ char data[]; /* placeholder for actual data */
}; };
#define NG_ABI_VERSION 12 /* Netgraph kernel ABI version */ #define NG_ABI_VERSION 12 /* Netgraph kernel ABI version */
#define NG_VERSION 8 /* Netgraph message version */ #define NGM_VERSION 8 /* Netgraph message version */
#define NGF_ORIG 0x00000000 /* The msg is the original request */
#define NGF_RESP 0x00000001 /* The message is a response */ #define NGF_RESP 0x00000001 /* The message is a response */
.Ed .Ed
.Pp .Pp
Control messages have the fixed header shown above, followed by a Control messages have the fixed header shown above, followed by a
variable length data section which depends on the type cookie variable length data section which depends on the type cookie
and the command. and the command.
Each field is explained below: Each field is explained below:
.Bl -tag -width indent .Bl -tag -width indent
.It Va version .It Va version
Indicates the version of the Indicates the version of the
.Nm .Nm
message protocol itself. message protocol itself.
The current version is The current version is
.Dv NG_VERSION . .Dv NGM_VERSION .
.It Va arglen .It Va arglen
This is the length of any extra arguments, which begin at This is the length of any extra arguments, which begin at
.Va data . .Va data .
.It Va flags .It Va flags
Indicates whether this is a command or a response control message. Indicates whether this is a command or a response control message.
.It Va token .It Va token
The The
.Va token .Va token
▲ Show 20 Lines • Show All 600 Lines • Show Last 20 Lines