search for: setup_data

...e. > --- 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_last_bus < 0) > pcibios_last_bus = 0xff; > > +#ifdef CONFIG_PCI_MMCONFIG > + if (setup_data.pci_mmconfig_base) { > + pci_mmconfig_add(0, 0, 0xff, setup_data.pci_mmconfig_base); Hmm... Shouldn't be pcibios_last_bus instead of 0xff? > + pci_mmcfg_arch_init(); > + } > +#endif -- With Best Regards, Andy Shevchenko

...ble [ 0.000000] e820: update [mem 0x03406018-0x03415857] usable ==> usable [ 0.000000] e820: update [mem 0x031be018-0x031c4a57] usable ==> usable [ 0.000000] e820: update [mem 0x03416018-0x03425857] usable ==> usable [ 0.000000] extended physical RAM map: [ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000009ffff] usable [ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x000000000319c017] usable [ 0.000000] reserve setup_data: [mem 0x000000000319c018-0x00000000031bde57] usable [ 0.000000] reserve setup_data: [mem 0x00000000031bde58-0x00000000031be0...

...0000000ffe9ffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000046f5fffff] usable [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] e820: update [mem 0x8944f190-0x89464dcf] usable ==> usable [ 0.000000] extended physical RAM map: [ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000008dfff] usable [ 0.000000] reserve setup_data: [mem 0x000000000008e000-0x000000000008ffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000000090000-0x000000000009ffff] usable [ 0.000000] reserve setup_data: [mem 0x00000000000a0000-0x00000000000b...

...x000000047f5fffff] usable [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] e820: update [mem 0x77d00190-0x77d167cf] usable ==> usable [ 0.000000] e820: update [mem 0x77cfe190-0x77cff04e] usable ==> usable [ 0.000000] extended physical RAM map: [ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x0000000000057fff] usable [ 0.000000] reserve setup_data: [mem 0x0000000000058000-0x0000000000058fff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000000059000-0x000000000008efff] usable [ 0.000000] reserve setup_data: [mem 0x000000000008f000-0x000000000008...

Hello, I am encountering a 30 second hang during boot, in the Xorg process just before the display manager comes up. I have bisected the problem to the following commit: commit 2b700825e7a7702fb862edba1262c98040dc1bf6 Author: Ben Skeggs <bskeggs at redhat.com> Date: Thu Aug 20 14:54:22 2015 +1000 drm/nouveau/mc: move device irq handling to platform-specific code The hang only

...arch/x86/kernel/jailhouse.c index b68fd895235a..7fe2a73da0b3 100644 --- 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_last_bus < 0) pcibios_last_bus = 0xff; +#ifdef CONFIG_PCI_MMCONFIG + if (setup_data.pci_mmconfig_base) { + pci_mmconfig_add(0, 0, 0xff, setup_data.pci_mmconfig_base); + pci_mmcfg_arch_init(); + } +#endif + return 0; } diff --git a/arch/x86/pci/mmconfig-shared.c b/arch/x86/pci/mmconfig-shared.c index 96684d0adcf9..0e590272366b 100644 --- a/arch/x86/pci/mmconfig-shared.c +++...

...arch/x86/kernel/jailhouse.c index b68fd895235a..7fe2a73da0b3 100644 --- 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_last_bus < 0) pcibios_last_bus = 0xff; +#ifdef CONFIG_PCI_MMCONFIG + if (setup_data.pci_mmconfig_base) { + pci_mmconfig_add(0, 0, 0xff, setup_data.pci_mmconfig_base); + pci_mmcfg_arch_init(); + } +#endif + return 0; } diff --git a/arch/x86/pci/mmconfig-shared.c b/arch/x86/pci/mmconfig-shared.c index 96684d0adcf9..0e590272366b 100644 --- a/arch/x86/pci/mmconfig-shared.c +++...

...arch/x86/kernel/jailhouse.c index b68fd895235a..7fe2a73da0b3 100644 --- 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_last_bus < 0) pcibios_last_bus = 0xff; +#ifdef CONFIG_PCI_MMCONFIG + if (setup_data.pci_mmconfig_base) { + pci_mmconfig_add(0, 0, 0xff, setup_data.pci_mmconfig_base); + pci_mmcfg_arch_init(); + } +#endif + return 0; } diff --git a/arch/x86/pci/mmconfig-shared.c b/arch/x86/pci/mmconfig-shared.c index 96684d0adcf9..0e590272366b 100644 --- a/arch/x86/pci/mmconfig-shared.c +++...

...arch/x86/kernel/jailhouse.c index b68fd895235a..fa183a131edc 100644 --- a/arch/x86/kernel/jailhouse.c +++ b/arch/x86/kernel/jailhouse.c @@ -124,6 +124,14 @@ static int __init jailhouse_pci_arch_init(void) if (pcibios_last_bus < 0) pcibios_last_bus = 0xff; +#ifdef CONFIG_PCI_MMCONFIG + if (setup_data.pci_mmconfig_base) { + pci_mmconfig_add(0, 0, pcibios_last_bus, + setup_data.pci_mmconfig_base); + pci_mmcfg_arch_init(); + } +#endif + return 0; } diff --git a/arch/x86/pci/mmconfig-shared.c b/arch/x86/pci/mmconfig-shared.c index 96684d0adcf9..0e590272366b 100644 --- a/arch/x86/pci/mmco...

...the kernel boot paths. > > -- > Matt Fleming, Intel Open Source Technology Center > I tried it with pre11, same problem. I modified the debug append line to the one above. I get the following output: efi_boot_linux: kernel_start 0x1000000 kernel_size 0x472390 initramfs 0x7e3dc998 setup_data 0x0 cmdline 0x9f000 efi_boot_linux: setup_sects 32 kernel_size 4662160 Hope this helps Regards Michael

...ive [ 0.000000] e820: update [mem 0xc0aad018-0xc0abd057] usable ==> usable [ 0.000000] e820: update [mem 0xc0a9c018-0xc0aac657] usable ==> usable [ 0.000000] e820: update [mem 0xc0a7c018-0xc0a9bc57] usable ==> usable [ 0.000000] extended physical RAM map: [ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000009bfff] usable [ 0.000000] reserve setup_data: [mem 0x000000000009c000-0x000000000009cfff] reserved [ 0.000000] reserve setup_data: [mem 0x000000000009d000-0x000000000009dfff] usable [ 0.000000] reserve setup_data: [mem 0x000000000009e000-0x00000000000b...

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in 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 -

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in 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 -

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in 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 -

On Thu, 25 Jul, at 09:18:30AM, Michael Szerencsits wrote: > I tried it with pre11, same problem. > > I modified the debug append line to the one above. > > I get the following output: > efi_boot_linux: kernel_start 0x1000000 kernel_size 0x472390 initramfs 0x7e3dc998 setup_data 0x0 cmdline 0x9f000 > efi_boot_linux: setup_sects 32 kernel_size 4662160 > > Hope this helps > Regards Michael Thanks, that does help. At least we know it's taking the 32-bit entry path. I opened the following bug report to track this issue, http://bugzilla.syslinux.org/show_b...

> Actually, can you grab the version I built from, > > ftp://syslinux.org/pub/syslinux/tests/syslinux-6.02-pre2.tar.gz > > And see whether things work for you? I'm just trying to rule out any > kind of distribution error on the Syslinux build machine. > > -- > Matt Fleming, Intel Open Source Technology Center > _______________________________________________

...whdr; - size_t real_mode_size, prot_mode_size, base; - addr_t real_mode_base, prot_mode_base, prot_mode_max; + size_t real_mode_size, prot_mode_size; + addr_t real_mode_base, prot_mode_base, prot_mode_max, base; addr_t irf_size; size_t cmdline_size, cmdline_offset; struct setup_data *sdp; -- 2.3.0-rc2

...oot parameters. */ mem_avoid[MEM_AVOID_BOOTPARAMS].start = (unsigned long)boot_params; mem_avoid[MEM_AVOID_BOOTPARAMS].size = sizeof(*boot_params); - add_identity_map(mem_avoid[MEM_AVOID_BOOTPARAMS].start, - mem_avoid[MEM_AVOID_BOOTPARAMS].size); /* We don't need to set a mapping for setup_data. */ @@ -436,11 +430,6 @@ static void mem_avoid_init(unsigned long input, unsigned long input_size, /* Enumerate the immovable memory regions */ num_immovable_mem = count_immovable_mem_regions(); - -#ifdef CONFIG_X86_VERBOSE_BOOTUP - /* Make sure video RAM can be used. */ - add_identity_map(...

...ernel_buf, size_t kernel_size, { struct linux_header hdr, *whdr; size_t real_mode_size, prot_mode_size, base; - addr_t real_mode_base, prot_mode_base; + addr_t real_mode_base, prot_mode_base, prot_mode_max; addr_t irf_size; size_t cmdline_size, cmdline_offset; struct setup_data *sdp; @@ -243,9 +240,19 @@ int bios_boot_linux(void *kernel_buf, size_t kernel_size, real_mode_size = (hdr.setup_sects + 1) << 9; real_mode_base = (hdr.loadflags & LOAD_HIGH) ? 0x10000 : 0x90000; prot_mode_base = (hdr.loadflags & LOAD_HIGH) ? 0x100000 : 0x10000; + pr...