From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Chia-I Wu <olvaffe@gmail.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
christian.koenig@amd.com, alexander.deucher@amd.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alison Schofield <alison.schofield@intel.com>,
Dave Jiang <dave.jiang@intel.com>, Baoquan He <bhe@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel/resource: optimize find_next_iomem_res
Date: Mon, 3 Jun 2024 10:24:39 +0300 (EEST) [thread overview]
Message-ID: <783e9d9a-e408-c6f0-9a4b-050e1979b919@linux.intel.com> (raw)
In-Reply-To: <Zlw1_n20oqchAYxH@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
On Sun, 2 Jun 2024, Andy Shevchenko wrote:
> 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@linux.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.
There is code which clearly tries to do expanding resource but that
usually fails to work as intended because of a parent resource whose size
is fixed because it's already assigned.
Some other code might block shrinking too under certain conditions.
This area would need to be reworked in PCI core but it's massive and
scary looking change.
--
i.
next prev parent reply other threads:[~2024-06-03 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 5:36 [PATCH] kernel/resource: optimize find_next_iomem_res Chia-I Wu
2024-05-31 8:57 ` Andy Shevchenko
[not found] ` <CAPaKu7SsD+X7KAO=3vEYU_7YGM_f+7k1fdC9nEK=-NaJw8oYaA@mail.gmail.com>
2024-06-02 9:06 ` Andy Shevchenko
2024-06-03 7:24 ` Ilpo Järvinen [this message]
2024-06-04 5:04 ` Chia-I Wu
2024-06-03 7:28 ` Ilpo Järvinen
2024-05-31 15:32 ` Andy Shevchenko
2024-06-04 15:31 ` Greg Kroah-Hartman
2024-06-04 21:37 ` Chia-I Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=783e9d9a-e408-c6f0-9a4b-050e1979b919@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=alexander.deucher@amd.com \
--cc=alison.schofield@intel.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bhe@redhat.com \
--cc=christian.koenig@amd.com \
--cc=dave.jiang@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olvaffe@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox