search for: hpas

Just a slight poke regarding the MEMDISK and MDISKCHK.COM possibilities available here[1]. Review by non-hpas is welcome, too. Thanks! - Shao [1] http://git.zytor.com/?p=users/sha0/syslinux.git;a=shortlog;h=refs/heads/ mdiskchk_enh2

...observation). Does the VMD controller code then use these bases addresses to program the bridges/endpoint within the domain? What does the same /proc/iomem or lspci look like inside the guest then? It seems like we'd see the VMD endpoint with GPA BARs, but the devices within the domain using HPAs. If that's remotely true, and we're not forcing an identity mapping of this HPA range into the GPA, does the vmd controller driver impose a TRA function on these MMIO addresses in the guest? Sorry if I'm way off, I'm piecing things together from scant information here. Please Cc...

...ode then use these bases addresses to program > > the bridges/endpoint within the domain? What does the same /proc/iomem > > or lspci look like inside the guest then? It seems like we'd see the > > VMD endpoint with GPA BARs, but the devices within the domain using > > HPAs. If that's remotely true, and we're not forcing an identity > > mapping of this HPA range into the GPA, does the vmd controller driver > > impose a TRA function on these MMIO addresses in the guest? > > This is the guest with the guest addresses: > f8000000-fbffff...

...;_STA.....OS 2a20: 59 53 0b d1 07 a0 08 48 50 41 45 a4 0a 0f a1 0a YS.....HPAE..... 2a30: a0 08 48 50 41 45 a4 0a 0b a4 00 14 46 05 5f 43 ..HPAE......F._C 2a40: 52 53 08 a0 49 04 48 50 41 45 8a 42 55 46 30 0a RS..I.HPAE.BUF0. 2a50: 04 48 50 54 30 a0 11 93 48 50 41 53 01 70 0c 00 .HPT0...HPAS.p.. 2a60: 10 d0 fe 48 50 54 30 a0 12 93 48 50 41 53 0a 02 ...HPT0...HPAS.. 2a70: 70 0c 00 20 d0 fe 48 50 54 30 a0 12 93 48 50 41 p.. ..HPT0...HPA 2a80: 53 0a 03 70 0c 00 30 d0 fe 48 50 54 30 a4 42 55 S..p..0..HPT0.BU 2a90: 46 30 5b 82 45 0a 49 50 49 43 08 5f 48 49 44 0b F0[.E.IPIC._HID....