search for: mmconfig

From: Otavio Pontes <otavio.pontes at intel.com> Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes <otavio.pontes at intel.com> [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG] Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> --- arch/x86/i...

From: Otavio Pontes <otavio.pontes at intel.com> Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes <otavio.pontes at intel.com> [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG] Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> --- arch/x86/i...

From: Otavio Pontes <otavio.pontes at intel.com> Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes <otavio.pontes at intel.com> [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG] Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> --- arch/x86/i...

From: Otavio Pontes <otavio.pontes at intel.com> Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes <otavio.pontes at intel.com> [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG, used pcibios_last_bus] Signed-off-by: Jan Kiszka <jan.kiszka at siemens....

Keir, Ian, With PCI mmconfig option on, and with the PCI express enabled BIOS, the dom0 kernel reads the PCI config from fix-mapped PCI mmconfig space. The PCI mmconfig space is of 256MB size, and it''s access is implemented differently on i386 & x86_64. On x86_64 the whole 256MB is mapped in the Kernel virtual...

...ing emulation mode by toggling the "#if 0" in arch/x86/mm.c ptwr_do_page_fault The other thing to try is modifying set_pte_pfn_ma to call xen_l1_update rather than set_pte. You could try set_pte_at too. This will help narrow down the issue. Thanks, Ian > Keir, Ian, > With PCI mmconfig option on, and with the PCI express > enabled BIOS, the dom0 kernel reads the PCI config from > fix-mapped PCI mmconfig space. > The PCI mmconfig space is of 256MB size, and it''s access > is implemented differently on i386 & x86_64. On x86_64 the > whole 256MB is...

On Thu, Mar 1, 2018 at 7:40 AM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > Use the PCI mmconfig base address exported by jailhouse in boot > parameters in order to access the memory mapped PCI configuration space. > --- a/arch/x86/kernel/jailhouse.c > +++ b/arch/x86/kernel/jailhouse.c > @@ -124,6 +124,13 @@ static int __init jailhouse_pci_arch_init(void) > if (pcibios...

...the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected - MMCONFIG support for x86 guests As most changes affect x86, I would suggest to route the series also via tip after the necessary acks are collected. Changes in v4: - slit up Kconfig changes - respect pcibios_last_bus during mmconfig setup - cosmetic changes requested by Andy Changes in v3: - avoided...

...the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected - MMCONFIG support for x86 guests As most changes affect x86, I would suggest to route the series also via tip after the necessary acks are collected. Changes in v5: - fix build breakage of patch 6 on i386 Changes in v4: - slit up Kconfig changes - respect pcibios_last_bus during mmconfig setup - cosme...

...the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected - MMCONFIG support for x86 guests As most changes affect x86, I would suggest to route the series also via tip after the necessary acks are collected. Changes in v2: - adjusted commit log and include ordering in patch 2 - rebased over Linus master Jan [1] https://lkml.org/lkml/2017/11/27/125 [2] http://...

...the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected - MMCONFIG support for x86 guests As most changes affect x86, I would suggest to route the series also via tip after the necessary acks are collected. Changes in v3: - avoided duplicate scans of PCI functions under Jailhouse - reformated PCI_MMCONFIG condition and rephrase related commit log Changes in v...

...the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected - MMCONFIG support for x86 guests As most changes affect x86, I would suggest to route the series also via tip after the necessary acks are collected. Changes in v3: - avoided duplicate scans of PCI functions under Jailhouse - reformated PCI_MMCONFIG condition and rephrase related commit log Changes in v...

...the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected - MMCONFIG support for x86 guests As most changes affect x86, I would suggest to route the series also via tip after the necessary acks are collected. Jan [1] https://lkml.org/lkml/2017/11/27/125 [2] http://jailhouse-project.org CC: Benedikt Spranger <b.spranger at linutronix.de> CC: Mark Rutland &l...

...the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection of Jailhouse via device tree hypervisor node - function-level PCI scan if Jailhouse is detected - MMCONFIG support for x86 guests As most changes affect x86, I would suggest to route the series also via tip after the necessary acks are collected. Jan [1] https://lkml.org/lkml/2017/11/27/125 [2] http://jailhouse-project.org CC: Benedikt Spranger <b.spranger at linutronix.de> CC: Mark Rutland &l...

...FC12 freshly installed. I am using DQ965GF intel mother board having intel VT-x enabled. I have installed everything properly, but xen boot gets stuck at this point, xenbus_probe_init ok ACPI: bus type pci registered PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 PCI: Not using MMCONFIG. I did few googlings and found few discussion at this point. http://lists.xensource.com/archives/html/xen-users/2009-11/msg00537.html So, I disabled ''pci=nommconf'' option from grub.conf and booted xen but again it stuck at this point, xenbus_probe_init ok ACPI: bus type pci re...

...FC12 freshly installed. I am using DQ965GF intel mother board having intel VT-x enabled. I have installed everything properly, but xen boot gets stuck at this point, xenbus_probe_init ok ACPI: bus type pci registered PCI: MCFG configuration 0: base e0000000 segment 0 buses 0 - 255 PCI: Not using MMCONFIG. I did few googlings and found few discussion at this point. http://lists.xensource.com/archives/html/xen-users/2009-11/msg00537.html So, I disabled ''pci=nommconf'' option from grub.conf and booted xen but again it stuck at this point, xenbus_probe_init ok ACPI: bus type pci re...

...ation space access from a com32 module. (ECAM, memory mapped, not CAM, which uses I/O port access). I know how to find the base address to the config space in Linux and use ECAM to access configuration registers. com32/lib/pci does not use ECAM. In Linux the region for ECAM is referred to as PCI MMCONFIG. (often shows up as e0000000-efffffff, see /proc/iomem) Any ideas as to how to get the ECAM base address from a COM32 module? Sincerely, Dwight Schauer Software Engineer Consumer & Computing Interface Texas Instruments Incorporated Email: dschauer at ti.com Phone: (214) 567-5695 Mobile: (90...

I thought I''d pass along a few tips for getting the Intel DQ35JO motherboard to play nice with Xen: 1. The dom0 kernel won''t boot with CONFIG_PCI_MMCONFIG enabled. If you get a hang during boot after seeing this message: ACPI: PCI Root Bridge [PCI0] (0000:00) ...then MMCONFIG is your problem. Some kernels seem to support a pci=nommconfig option, but my Gentoo 2.6.21 Xen kernel didn''t. The solution was to build the kernel without MMCO...

From: Jan Kiszka <jan.kiszka at siemens.com> Jailhouse does not use ACPI, but it does support MMCONFIG. Make sure the latter can be built without having to enable ACPI as well. Primarily, we need to make the AMD mmconf-fam10h_64 depend upon MMCONFIG and ACPI, instead of just the former. Saves some bytes in the Jailhouse non-root kernel. Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> -...

From: Jan Kiszka <jan.kiszka at siemens.com> Jailhouse does not use ACPI, but it does support MMCONFIG. Make sure the latter can be built without having to enable ACPI as well. Primarily, we need to make the AMD mmconf-fam10h_64 depend upon MMCONFIG and ACPI, instead of just the former. Saves some bytes in the Jailhouse non-root kernel. Signed-off-by: Jan Kiszka <jan.kiszka at siemens.com> -...