lkml.org 
[lkml]   [2012]   [Nov]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 1/5] resources: Print resource ranges when expanding overlaps
    Date
    Resource names can be too generic to distinguish which resources
    overlap; eg.,
    kernel: Expanded resource reserved due to conflict with PCI Bus 0000:00
    kernel: Expanded resource reserved due to conflict with PCI Bus 0000:00

    Rather, print decoded resource info as well; eg.,
    kernel: resource: Expanding reserved [mem 0xcfe5ec00-0xcfffffff]; overlaps PCI Bus 0000:00 [mem 0xcff00000-0xdfffffff]
    kernel: resource: Expanding reserved [mem 0xfe000000-0xfeffffff]; overlaps PCI Bus 0000:00 [mem 0xf0000000-0xfe000000]

    Cc: Bjorn Helgaas <bhelgaas@google.com>
    Signed-off-by: Peter Hurley <peter@hurleysoftware.com>
    ---
    kernel/resource.c | 5 +++--
    1 file changed, 3 insertions(+), 2 deletions(-)

    diff --git a/kernel/resource.c b/kernel/resource.c
    index 73f35d4..461c2e0 100644
    --- a/kernel/resource.c
    +++ b/kernel/resource.c
    @@ -696,12 +696,13 @@ void insert_resource_expand_to_fit(struct resource *root, struct resource *new)
    break;

    /* Ok, expand resource to cover the conflict, then try again .. */
    + pr_warn("Expanding %s %pR; overlaps %s %pR\n",
    + new->name, new, conflict->name, conflict);
    +
    if (conflict->start < new->start)
    new->start = conflict->start;
    if (conflict->end > new->end)
    new->end = conflict->end;
    -
    - printk("Expanded resource %s due to conflict with %s\n", new->name, conflict->name);
    }
    write_unlock(&resource_lock);
    }
    --
    1.7.12.3


    \
     
     \ /
      Last update: 2012-11-08 04:42    [W:3.152 / U:0.012 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site