Searched refs:opregion (Results 1 – 2 of 2) sorted by relevance
184 struct passthru_mmio_mapping *opregion; in gvt_d_setup_opregion() local197 opregion = passthru_get_mmio(sc, GVT_D_MAP_OPREGION); in gvt_d_setup_opregion()198 if (opregion == NULL) { in gvt_d_setup_opregion()221 opregion->hpa = asls; in gvt_d_setup_opregion()222 opregion->len = header->size * KB; in gvt_d_setup_opregion()225 if (opregion->len != sizeof(struct igd_opregion)) { in gvt_d_setup_opregion()227 opregion->len); in gvt_d_setup_opregion()232 opregion->hva = mmap(NULL, opregion->len, PROT_READ, MAP_SHARED, memfd, in gvt_d_setup_opregion()233 opregion->hpa); in gvt_d_setup_opregion()234 if (opregion->hva == MAP_FAILED) { in gvt_d_setup_opregion()[all …]
313 well as the PCC channel index when the opregion handler is being executed 615 and has added the Cherry Trail specific UserDefined(0x93) opregion to its 669 Preserve memory opregion mappings. The ACPICA's strategy with respect to 678 For this reason, a one-page "window" is mapped for a given opregion on 680 address range accessed through that opregion subsequently, it is unmapped 682 not sufficient to access memory through the opregion in question in the 685 operations, for example if two fields in one opregion separated from each