search for: ioresource_busy

...) Indeed. And I appreciate your help a lot. >> And your PCI-BAR adjustment doesn't change >> anything either, sorry. > > I simply tried another approach to pacify the resource checker. > > However, there is some difference. nvidiafb cannot access the > resources if IORESOURCE_BUSY is used. Are you sure this is related to IORESOURCE_BUSY? Or is it related to CONFIG_X86_SYSFB? Thanks David > It's not that it matters for me. nvidiafb fails on my hardware anyway > and I don't need it when I already have simplefb and nouveau. But I > think we should have a c...

...And your PCI-BAR adjustment doesn't change >> >> anything either, sorry. >> > >> > I simply tried another approach to pacify the resource checker. >> > >> > However, there is some difference. nvidiafb cannot access the >> > resources if IORESOURCE_BUSY is used. >> >> Are you sure this is related to IORESOURCE_BUSY? Or is it related to >> CONFIG_X86_SYSFB? > > CONFIG_X86_SYSFB is always defined. I doubt an x86 kernel would > compile without it. create_simplefb() is used in > arch/x86/kernel/sysfb.c that is compiled...

...t; wrote: > >> And your PCI-BAR adjustment doesn't change > >> anything either, sorry. > > > > I simply tried another approach to pacify the resource checker. > > > > However, there is some difference. nvidiafb cannot access the > > resources if IORESOURCE_BUSY is used. > > Are you sure this is related to IORESOURCE_BUSY? Or is it related to > CONFIG_X86_SYSFB? CONFIG_X86_SYSFB is always defined. I doubt an x86 kernel would compile without it. create_simplefb() is used in arch/x86/kernel/sysfb.c that is compiled unconditionally and that funct...

...nel/paravirt.c Tue Jun 05 18:17:29 2007 -0700 @@ -227,6 +227,39 @@ static int __init print_banner(void) return 0; } core_initcall(print_banner); + +static struct resource reserve_ioports = { + .start = 0, + .end = IO_SPACE_LIMIT, + .name = "paravirt-ioport", + .flags = IORESOURCE_IO | IORESOURCE_BUSY, +}; + +static struct resource reserve_iomem = { + .start = 0, + .end = -1, + .name = "paravirt-iomem", + .flags = IORESOURCE_MEM | IORESOURCE_BUSY, +}; + +/* + * Reserve the whole legacy IO space to prevent any legacy drivers + * from wasting time probing for their hardware. This is a f...

Hello! I'm getting this backtrace every time I boot: resource map sanity check conflict: 0xf0000000 0xf1ffffff 0xf1000000 0xf112bfff BOOTFB ------------[ cut here ]------------ WARNING: CPU: 6 PID: 1 at /home/proskin/src/linux/arch/x86/mm/ioremap.c:171 __ioremap_caller+0x372/0x380() Info: mapping multiple BARs. Your kernel is fine. Modules linked in: CPU: 6 PID: 1 Comm: swapper/0 Not tainted

...des the existing resource without being equivalent to it. Nouveau correctly calls remove_conflicting_framebuffers() before trying to map that resource. However, sysfb_simplefb is not a real framebuffer, so it doesn't free its resources. iomem_map_sanity_check() doesn't check regions with IORESOURCE_BUSY set. That's the comment from the code: /* * if a resource is "BUSY", it's not a hardware resource * but a driver mapping of such a resource; we don't want * to warn for those; some drivers legitimately map only * partial hardware resources. (example:...

Hi Pavel On Fri, Sep 27, 2013 at 9:40 PM, Pavel Roskin <proski at gnu.org> wrote: > Quoting David Herrmann <dh.herrmann at gmail.com>: > >> I am aware of this and there is already a fix pending from 2 weeks >> ago. Unfortunately, I have been in the US for the last 2 weeks and >> haven't really been able to push on that. Anyhow, it should really be >>

...that is only > > compiled if CONFIG_X86_SYSFB is defined. > > You can set CONFIG_X86_SYSFB=n and everything works fine. It's the > default and is what pre-3.12 kernels always did. Of course, you are right, I missed sysfb.h. > > I tried four combinations: with and without IORESOURCE_BUSY and with > > and without the PCI resource adjustment. The only combination when > > nvidiafb probes the hardware is when IORESOURCE_BUSY is not used and > > the BOOTFP resource is adjusted to match the PCI BAR. > > A dmesg log would be nice, but I assume nvidiafb fails bec...

...gt; being equivalent to it. > > Nouveau correctly calls remove_conflicting_framebuffers() before trying > to map that resource. However, sysfb_simplefb is not a real > framebuffer, so it doesn't free its resources. > > iomem_map_sanity_check() doesn't check regions with IORESOURCE_BUSY > set. That's the comment from the code: > > /* > * if a resource is "BUSY", it's not a hardware resource > * but a driver mapping of such a resource; we don't want > * to warn for those; some drivers legitimately map only > * par...

...the >> + * parent (besides during boot). >> + * - release_mem_region_adjustable() will split on demand on memory hotunplug >> + */ >> +void merge_system_ram_resources(struct resource *parent) >> +{ >> + const unsigned long flags = IORESOURCE_SYSTEM_RAM | IORESOURCE_BUSY; >> + struct resource *cur, *next; >> + >> + write_lock(&resource_lock); >> + >> + cur = parent->child; >> + while (cur && cur->sibling) { >> + next = cur->sibling; >> + if ((cur...

...omem resource */ > -static struct resource *register_memory_resource(u64 start, u64 size) > +static struct resource *register_memory_resource(u64 start, u64 size, > + const char *resource_name) > { > struct resource *res; > unsigned long flags = IORESOURCE_SYSTEM_RAM | IORESOURCE_BUSY; > - char *resource_name = "System RAM"; > > /* > * Make sure value parsed from 'mem=' only restricts memory adding > @@ -1058,7 +1058,8 @@ int __ref add_memory_resource(int nid, struct resource *res, > BUG_ON(ret); > > /* create new memmap ent...

...omem resource */ > -static struct resource *register_memory_resource(u64 start, u64 size) > +static struct resource *register_memory_resource(u64 start, u64 size, > + const char *resource_name) > { > struct resource *res; > unsigned long flags = IORESOURCE_SYSTEM_RAM | IORESOURCE_BUSY; > - char *resource_name = "System RAM"; > > /* > * Make sure value parsed from 'mem=' only restricts memory adding > @@ -1058,7 +1058,8 @@ int __ref add_memory_resource(int nid, struct resource *res, > BUG_ON(ret); > > /* create new memmap ent...

...el/paravirt.c @@ -207,25 +207,6 @@ static u64 native_steal_clock(int cpu) extern void native_iret(void); extern void native_usergs_sysret64(void); -static struct resource reserve_ioports = { - .start = 0, - .end = IO_SPACE_LIMIT, - .name = "paravirt-ioport", - .flags = IORESOURCE_IO | IORESOURCE_BUSY, -}; - -/* - * Reserve the whole legacy IO space to prevent any legacy drivers - * from wasting time probing for their hardware. This is a fairly - * brute-force approach to disabling all non-virtual drivers. - * - * Note that this must be called very early to have any effect. - */ -int paravirt_d...

...tches don't have unexpected effects even if the effects are positive :) > And your PCI-BAR adjustment doesn't change > anything either, sorry. I simply tried another approach to pacify the resource checker. However, there is some difference. nvidiafb cannot access the resources if IORESOURCE_BUSY is used. It's not that it matters for me. nvidiafb fails on my hardware anyway and I don't need it when I already have simplefb and nouveau. But I think we should have a closer look why it fails and what other drivers may fail. -- Regards, Pavel Roskin

...->memsz) diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c index 4c47b68a9f4b5..8e1cd18b5cf14 100644 --- a/mm/memory_hotplug.c +++ b/mm/memory_hotplug.c @@ -105,7 +105,7 @@ static struct resource *register_memory_resource(u64 start, u64 size, unsigned long flags = IORESOURCE_SYSTEM_RAM | IORESOURCE_BUSY; if (strcmp(resource_name, "System RAM")) - flags |= IORESOURCE_MEM_DRIVER_MANAGED; + flags |= IORESOURCE_SYSRAM_DRIVER_MANAGED; /* * Make sure value parsed from 'mem=' only restricts memory adding @@ -1160,7 +1160,7 @@ EXPORT_SYMBOL_GPL(add_memory); * * For this...

Hi folks, With this series, the bulk of the work of pvops64 is done. Here, I integrate most of the paravirt.c and paravirt.h files, making them applicable to both architectures. CONFIG_PARAVIRT is _not_ present yet. Basically, this code is missing page table integration (patches currently being worked on by Jeremy). Enjoy

Hi folks, With this series, the bulk of the work of pvops64 is done. Here, I integrate most of the paravirt.c and paravirt.h files, making them applicable to both architectures. CONFIG_PARAVIRT is _not_ present yet. Basically, this code is missing page table integration (patches currently being worked on by Jeremy). Enjoy

Move header includes for the nopud / nopmd types to the location of the actual pte / pgd type definitions. This allows generic 4-level page type code to be written before the split 2/3 level page table headers are included. Signed-off-by: Zachary Amsden <zach@vmware.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

Move header includes for the nopud / nopmd types to the location of the actual pte / pgd type definitions. This allows generic 4-level page type code to be written before the split 2/3 level page table headers are included. Signed-off-by: Zachary Amsden <zach@vmware.com> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>

...AX; /* add this memory to iomem resource */ -static struct resource *register_memory_resource(u64 start, u64 size) +static struct resource *register_memory_resource(u64 start, u64 size, + const char *resource_name) { struct resource *res; unsigned long flags = IORESOURCE_SYSTEM_RAM | IORESOURCE_BUSY; - char *resource_name = "System RAM"; /* * Make sure value parsed from 'mem=' only restricts memory adding @@ -1058,7 +1058,8 @@ int __ref add_memory_resource(int nid, struct resource *res, BUG_ON(ret); /* create new memmap entry */ - firmware_map_add_hotplug(start,...