Searched refs:opregion (Results 1 – 2 of 2) sorted by relevance
414 struct passthru_mmio_mapping *opregion; in gvt_d_setup_opregion() local431 opregion = passthru_get_mmio(sc, GVT_D_MAP_OPREGION); in gvt_d_setup_opregion()432 if (opregion == NULL) { in gvt_d_setup_opregion()455 opregion->hpa = asls; in gvt_d_setup_opregion()456 opregion->len = header->size * KB; in gvt_d_setup_opregion()459 if (opregion->len != sizeof(struct igd_opregion)) { in gvt_d_setup_opregion()461 opregion->len); in gvt_d_setup_opregion()466 opregion->hva = mmap(NULL, opregion->len, PROT_READ, MAP_SHARED, memfd, in gvt_d_setup_opregion()467 opregion->hpa); in gvt_d_setup_opregion()468 if (opregion->hva == MAP_FAILED) { in gvt_d_setup_opregion()[all …]
445 well as the PCC channel index when the opregion handler is being executed 747 and has added the Cherry Trail specific UserDefined(0x93) opregion to its 801 Preserve memory opregion mappings. The ACPICA's strategy with respect to 810 For this reason, a one-page "window" is mapped for a given opregion on 812 address range accessed through that opregion subsequently, it is unmapped 814 not sufficient to access memory through the opregion in question in the 817 operations, for example if two fields in one opregion separated from each