ok googled a bit around and found this: https://communities.intel.com/thread/28389
another one with a P6T Board :D he's using xen with a better(?) logging i've checked aw's post about reserving memory and tried it, but its already reserved? [ 0.000000] e820: BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000000e4c00-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bf77ffff] usable [ 0.000000] BIOS-e820: [mem 0x00000000bf780000-0x00000000bf797fff] ACPI data [ 0.000000] BIOS-e820: [mem 0x00000000bf798000-0x00000000bf7dbfff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x00000000bf7dc000-0x00000000bfffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000063fffffff] usable [ 0.000000] debug: ignoring loglevel setting. [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] e820: user-defined physical RAM map: [ 0.000000] user: [mem 0x0000000000000000-0x000000000009d3ff] usable [ 0.000000] user: [mem 0x000000000009d400-0x000000000009ffff] reserved [ 0.000000] user: [mem 0x00000000000e4c00-0x00000000000fffff] reserved [ 0.000000] user: [mem 0x0000000000100000-0x00000000bf77ffff] usable [ 0.000000] user: [mem 0x00000000bf780000-0x00000000bf797fff] ACPI data [ 0.000000] user: [mem 0x00000000bf798000-0x00000000bf7dbfff] ACPI NVS [ 0.000000] user: [mem 0x00000000bf7dc000-0x00000000bfffffff] reserved [ 0.000000] user: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] user: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved [ 0.000000] user: [mem 0x0000000100000000-0x000000063fffffff] usable btw i've tested if something appear in dmesg if i disable vt-d from the chipset( i thought maybe the cpu will use the built-in feature) buuuuuut no ;( maybe aw have some more ideas? :) 2016-09-02 20:34 GMT+02:00 Marco Stagge <spiritblackdiam...@gmail.com>: > Hey, > > thanks for your answer, atm im checking my dmesg for that entry .. i've > found this so far^^ > > [ 0.000000] e820: BIOS-provided physical RAM map: > [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] > usable > [ 0.000000] BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000000e4c00-0x00000000000fffff] > reserved > [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bf77ffff] > usable > [ 0.000000] BIOS-e820: [mem 0x00000000bf780000-0x00000000bf797fff] > ACPI data > [ 0.000000] BIOS-e820: [mem 0x00000000bf798000-0x00000000bf7dbfff] > ACPI NVS > [ 0.000000] BIOS-e820: [mem 0x00000000bf7dc000-0x00000000bfffffff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] > reserved > [ 0.000000] BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] > reserved > [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000063fffffff] > usable > [ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved > [ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable > [ 0.000000] e820: last_pfn = 0x640000 max_arch_pfn = 0x400000000 > [ 0.000000] e820: update [mem 0xbf800000-0xffffffff] usable ==> reserved > [ 0.000000] e820: last_pfn = 0xbf780 max_arch_pfn = 0x400000000 > [ 0.000000] e820: [mem 0xc0000000-0xfedfffff] available for PCI devices > [ 0.554189] e820: reserve RAM buffer [mem 0x0009d400-0x0009ffff] > [ 0.554190] e820: reserve RAM buffer [mem 0xbf780000-0xbfffffff] > > the interesting part(for me) is that "available for PCI devices" mem ... > so at this point all infos about pcidevices are stored in this mem area? > > if i grep around for "mem" there is a lot infos ... hmm .... well, i'll > attach my dmesg in this mail(hope thats possible) > maybe there is someone who figure some areas out, i'll test it and report > back then :) > > ...and i found something new lol :D > > ACPI: DMAR 0x00000000BF7980C0 000138 (v01 AMI OEMDMAR 00000001 MSFT > 00000097) > > but, i dont know what this output should tell me?^^ > > > hmmm maybe this could help > > [ 0.090460] dmar: Host address width 39 > [ 0.090509] dmar: DRHD base: 0x000000fbfff000 flags: 0x0 > [ 0.090566] dmar: IOMMU 0: reg_base_addr fbfff000 ver 1:0 cap > c9008010e60262 ecap f0207a > [ 0.090629] dmar: DRHD base: 0x000000fbffe000 flags: 0x1 > [ 0.090680] dmar: IOMMU 1: reg_base_addr fbffe000 ver 1:0 cap > c90780106f0462 ecap f020fe > [ 0.090742] dmar: RMRR base: 0x000000000ec000 end: 0x000000000effff > [ 0.090790] dmar: RMRR base: 0x000000bf7dc000 end: 0x000000bf7dbfff > [ 0.090838] dmar: ATSR flags: 0x0 > > > > btw i wonder why, the xeon(vt-d supported) is not able to override the > vt-d tables from the motherboard or something like that > > maybe its blocked by bios? > > > > > 2016-09-02 15:36 GMT+02:00 rob e <redger...@yahoo.com.au>: > >> On 31/08/16 02:00, vfio-users-requ...@redhat.com wrote: >> >> Date: Tue, 30 Aug 2016 11:52:18 +0200 >> From: Marco Stagge <spiritblackdiam...@gmail.com> >> <spiritblackdiam...@gmail.com> >> To: vfio-users@redhat.com >> Subject: [vfio-users] Asus P6T Deluxe unofficial BIOS >> Message-ID: >> <cadkdhyex84arcoctnerak0sed0hpscgj5tef3ujsz+01ylg...@mail.gmail.com> >> <cadkdhyex84arcoctnerak0sed0hpscgj5tef3ujsz+01ylg...@mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> Hey there, >> >> i've got two Boards, Asus P6T Deluxe and non-Deluxe Version. Ive running a >> Xeon X5650 on it, but >> VT-d is routed through bios(dmesg told me), and the DMAR-Table is broken. >> On the xen page i've found this "ASUS P6T Deluxe (Intel X58 chipset) >> requires (currently non-public) BIOS update to correct DMAR-table issue". >> >> Does anyone know if there is a unofficial bios with corrected DMAR-Table? >> google is not my friend^^ >> didnt find anything useful :( >> >> greet Spirit >> >> >> I have the same motherboard and also sought that bios, without success. >> There is however someone else who may have tried it >> https://bbs.archlinux.org/viewtopic.php?pid=1487138#p1487138 >> See Alex's response suggesting use of >> >> memmap=nn[KMG]$ss[KMG] >> [KNL,ACPI] Mark specific memory as reserved. >> Region of memory to be reserved is from ss to ss+nn. >> Example: Exclude memory from 0x18690000-0x1869ffff >> memmap=64K$0x18690000 >> or >> memmap=0x10000$0x18690000 >> >> I haven't tried this myself so would be interested in your feedback :) >> > >
_______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
