[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zlw1_n20oqchAYxH@smile.fi.intel.com>
Date: Sun, 2 Jun 2024 12:06:06 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Chia-I Wu <olvaffe@...il.com>
Cc: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
amd-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
christian.koenig@....com, alexander.deucher@....com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alison Schofield <alison.schofield@...el.com>,
Dave Jiang <dave.jiang@...el.com>, Baoquan He <bhe@...hat.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kernel/resource: optimize find_next_iomem_res
On Fri, May 31, 2024 at 02:31:45PM -0700, Chia-I Wu wrote:
> On Fri, May 31, 2024 at 1:57 AM Andy Shevchenko <
> andriy.shevchenko@...ux.intel.com> wrote:
> > On Thu, May 30, 2024 at 10:36:57PM -0700, Chia-I Wu wrote:
...
> > P.S> I'm not so sure about this change. It needs a thoroughly testing, esp.
> > in PCI case. Cc'ing to Ilpo.
> What's special about PCI?
PCI, due to its nature, may rebuild resources either by shrinking or expanding
of the entire subtree after the PCI bridge in question. And this may happen at
run-time due to hotplug support. But I'm not a deep expert in this area, Ilpo
knows much more than me.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists