[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151227021257.GA13560@dhcp-128-25.nay.redhat.com>
Date: Sun, 27 Dec 2015 10:12:57 +0800
From: Minfei Huang <mhuang@...hat.com>
To: Toshi Kani <toshi.kani@....com>
Cc: Borislav Petkov <bp@...en8.de>, 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,
Dave Young <dyoung@...hat.com>,
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 12/26/15 at 05:31pm, Toshi Kani wrote:
> + cc: kexec list
>
> On 12/26/2015 3:38 AM, Borislav Petkov wrote:
> >On Fri, Dec 25, 2015 at 03:09:23PM -0700, Toshi Kani wrote:
> >>Change to call walk_iomem_res_desc() for searching resource entries
> >>with the following names:
> >> "ACPI Tables"
> >> "ACPI Non-volatile Storage"
> >> "Persistent Memory (legacy)"
> >> "Crash kernel"
> >>
> >>Note, the caller of walk_iomem_res() with "GART" is left unchanged
> >>because this entry may be initialized by out-of-tree drivers, which
> >>do not have 'desc' set to IORES_DESC_GART.
> >
> >There's this out-of-tree bogus argument again. :\
> >
> >Why do we care about out-of-tree drivers?
> >
> >You can just as well fix the "GART" case too and kill walk_iomem_res()
> >altogether...
>
> Right, but I do not see any "GART" case in the upstream code, so I
> cannot change it...
Hi, Toshi.
You can refer the below link that you may get a clue about GART. This is
the fisrt time kexec-tools tried to support to ignore GART region in 2nd
kernel.
http://lists.infradead.org/pipermail/kexec/2008-December/003096.html
Thanks
Minfei
--
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