[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiGhHk4u2RRZmJinA4Apb47pXXJPW9cOZ_2-yUqOvaC7Q@mail.gmail.com>
Date: Wed, 5 Apr 2023 09:23:09 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: david@...hat.com, patches@...ts.linux.dev,
linux-modules@...r.kernel.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, pmladek@...e.com,
petr.pavlu@...e.com, prarit@...hat.com, gregkh@...uxfoundation.org,
rafael@...nel.org, christophe.leroy@...roup.eu, tglx@...utronix.de,
peterz@...radead.org, song@...nel.org, rppt@...nel.org,
dave@...olabs.net, willy@...radead.org, vbabka@...e.cz,
mhocko@...e.com, dave.hansen@...ux.intel.com,
colin.i.king@...il.com, jim.cromie@...il.com,
catalin.marinas@....com, jbaron@...mai.com,
rick.p.edgecombe@...el.com
Subject: Re: [PATCH v2 5/6] debugfs: add debugfs_create_atomic64_t for atomic64_t
On Wed, Apr 5, 2023 at 9:11 AM Luis Chamberlain <mcgrof@...nel.org> wrote:
>
> Oh but I don't get the atomic incs, so we'd need debugfs_create_atomic_long_t().
No, you misunderstand what I meant.
Just use "atomic_long_t" in the module code.
But then the debugfs code should do
debugfs_create_ulong(... &val->counter ..);
to expose said atomic_long values.
No need for new debugfs interfaces.
Because "atomic_long" is just a regular "long" as far as plain
read/set operations are concerned - which is all that the debugfs code
does anyway.
So I think you can do something like
atomic_long_t total_mod_size;
...
debugfs_create_ulong("total_mod_size",
0400, mod_debugfs_root,
&total_mod_size.counter);
but I didn't actually try to compile that kind of version.
(I think "counter" is actually a _signed_ long, so maybe the types don't match).
Linus
Powered by blists - more mailing lists