From: Mark Brown <broonie@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, driver-core@lists.linux.dev,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>
Subject: Re: [PATCH v3 1/3] regcache: Move HW readback after cache initialisation
Date: Sat, 28 Feb 2026 13:09:09 +0000 [thread overview]
Message-ID: <aaLo9QdbtR7u6y3c@sirena.co.uk> (raw)
In-Reply-To: <aaEvH2dk9yTwaUc8@smile.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
On Fri, Feb 27, 2026 at 07:43:59AM +0200, Andy Shevchenko wrote:
> Is it possible to allocate something, then count, then reallocate
> in the existing caches and in the potential future ones?
> I think it's the patter that we first count the size of the allocation,
> do the allocation, and only then fill up the allocated area with data.
> Otherwise we came back to the chicken-egg issue this patch tries to solve.
The main worry there would be transiently consuming huge amounts of
memory if there's a very sparse regsiter map, though we'd also be
burning lots of CPU time checking all those registers so perhaps it's
not a real concern, and the whole thing is kind of an edge case anyway.
Though now I look again we are careful to bypass the cache during the
hw_init() so we should be safe anyway I think.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-02-28 13:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 13:57 [PATCH v3 0/3] regcache: Avoid accessing non-initialised cache Andy Shevchenko
2026-02-26 13:57 ` [PATCH v3 1/3] regcache: Move HW readback after cache initialisation Andy Shevchenko
2026-02-26 22:14 ` Mark Brown
2026-02-27 5:43 ` Andy Shevchenko
2026-02-28 13:09 ` Mark Brown [this message]
2026-02-28 13:55 ` Andy Shevchenko
2026-02-26 13:57 ` [PATCH v3 2/3] regcache: Define iterator inside for-loop and align their types Andy Shevchenko
2026-02-26 13:57 ` [PATCH v3 3/3] regcache: Amend printf() specifiers when printing registers Andy Shevchenko
2026-03-03 11:20 ` [PATCH v3 0/3] regcache: Avoid accessing non-initialised cache Mark Brown
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=aaLo9QdbtR7u6y3c@sirena.co.uk \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
/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