[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1451930260.19330.21.camel@hpe.com>
Date: Mon, 04 Jan 2016 10:57:40 -0700
From: Toshi Kani <toshi.kani@....com>
To: Borislav Petkov <bp@...en8.de>, Dave Young <dyoung@...hat.com>
Cc: Minfei Huang <mhuang@...hat.com>, linux-arch@...r.kernel.org,
linux-nvdimm@...1.01.org, x86@...nel.org,
kexec@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, akpm@...ux-foundation.org,
Dan Williams <dan.j.williams@...el.com>
Subject: Re: [PATCH v2 14/16] x86, nvdimm, kexec: Use walk_iomem_res_desc()
for iomem search
On Mon, 2016-01-04 at 13:26 +0100, Borislav Petkov wrote:
> On Mon, Jan 04, 2016 at 05:29:37PM +0800, Dave Young wrote:
> > Replied to Toshi old kernel will export the "GART" region for amd
> > cards.
> > So for old kernel and new kexec-tools we will have problem.
> >
> > I think add the GART desc for compitibility purpose is doable, no?
>
> Just read your other mails too. If I see it correctly, there's only one
> place which has "GART":
>
> $ git grep -e \"GART\"
> arch/x86/kernel/crash.c:235: walk_iomem_res("GART", IORESOURCE_MEM, 0,
> -1,
>
> So crash.c only excludes this region but the kernel doesn't create it.
> Right?
>
> So we can kill that walk_iomem_res(), as you say. Which would be even
> nicer...
Agreed. As Dave suggested in the other thread, we can simply remove the
walk_iomem_res("GART",) call in crash.c.
With this change, there will be no caller to walk_iomem_res(). Should we
remove walk_iomem_res() altogether, or keep it for now as a deprecated func
with the checkpatch check?
Thanks,
-Toshi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists