search for: mmcfg

Fixes made in version 2: 1) Use PML4[257] for ioremap of PCI mmcfg. As full 16-bit segment support would require 44-bits. Since each slot only has 39-bits, we support 2048 PCI segments for now. This can be easily expanded if deemed necessary in the future. 2) Integrated PCI mmcfg access with existing PCI config interface for x86_64. Use MMCFG interface if off...

Hi, First of all, thanks for your help. I have made some test with this results debian testing with xen 4.4 can run if we add mmcfg=0 as boot options to kernel boot parameters !!! Remember that with xen kernel <=4.0 works perfect without to add mmcfg=0 I have tried to install citrix xenserver 5.6 and works perfect (remember that this is xen 3 branch) Also we have tried to install xenserver 6.2 but during boot install using:...

On Fri, 2014-09-05 at 13:39 +0200, trenta wrote: > Additional information: > http://lists.xen.org/archives/html/xen-devel/2013-09/msg00584.html This thread suggests that mmconfig might be the issue, in which case does adding "mmcfg=0" to your hypervisor command line help? I'd recommend continuing to pursue this upstream, there are far more experts on the low level aspect of things there. Ian.

Forcibly enabling the MMCFG space on AMD Fam10 CPUs cannot be expected to work since with the firmware not being aware of the address range used it cannot possibly reserve the space in E820 or ACPI resources. Hence we need to manually insert the range into the E820 table, and enable the range only when the insertion actually...

Hi Allen, Hi All, I''m looking into SR-IOV on Xen and in particular getting the VFs of the Intel 82756 initialised in dom0. One problem that I am coming up against is that the SRIOV extended PCIe capability does not show up for the PF (physical PCI function). Actually, the extended PCIe capability space doesn''t show up at all for any device. This seems to be related to a

Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/x86_64/mmconfig_64.c +++ b/xen/arch/x86/x86_64/mmconfig_64.c @@ -23,7 +23,7 @@ struct mmcfg_virt { char __iomem *virt; }; static struct mmcfg_virt *pci_mmcfg_virt; -static int __initdata mmcfg_pci_segment_shift; +static unsigned int mmcfg_pci_segment_shift; static char __iomem *get_virt(unsigned int seg, unsigned int *bus) { _______________________________________________...

Package: xen-hypervisor-4.4-amd64 Version: 4.4.0-4 Severity: normal -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash

...si\_irqs @@ -306,7 +367,8 @@ This option is only useful for hosts wit ### mem > `= <size>` -Specifies the maximum address of physical RAM. Any RAM beyond this limit is ignored by Xen. +Specifies the maximum address of physical RAM. Any RAM beyond this +limit is ignored by Xen. ### mmcfg ### nmi @@ -314,29 +376,37 @@ Specifies the maximum address of physica > Default: `nmi=fatal` -Specify what Xen should do in the event of an NMI parity or I/O error. `ignore` discards the error; `dom0` causes Xen to report the error to dom0, while ''fatal'' causes Xen to p...