From: Yury Norov <yury.norov@gmail.com>
To: Alexander Potapenko <glider@google.com>
Cc: catalin.marinas@arm.com, will@kernel.org, pcc@google.com,
andreyknvl@gmail.com, andriy.shevchenko@linux.intel.com,
aleksander.lobakin@intel.com, linux@rasmusvillemoes.dk,
alexandru.elisei@arm.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, eugenis@google.com,
syednwaris@gmail.com, william.gray@linaro.org
Subject: Re: [PATCH v10-mte 4/7] arm64: mte: implement CONFIG_ARM64_MTE_COMP
Date: Fri, 15 Dec 2023 08:35:40 -0800 [thread overview]
Message-ID: <ZXyAXPxlmq11rp2Y@yury-ThinkPad> (raw)
In-Reply-To: <CAG_fn=WcrNqV4burBRPZZwoBLwgia7kerZ8g2vV5spzWF=houQ@mail.gmail.com>
On Fri, Dec 15, 2023 at 04:19:27PM +0100, Alexander Potapenko wrote:
> >
> > That looks weird... You're casting address of a 'data' to a bitmap
> > instead of 'data'. At the 1st glance it makes little sense because
> > 'data' is passed as parameter. Moreover, in mte_is_compressed()
> > you pass 'data', not '&data'. Can you please comment on your
> > intention?
>
> Although `data` is a void*, it actually contains 64 bits of compressed
> data, so we pass &data to mte_bitmap_read() to read its contents.
> Perhaps I'd better make `data` an unsigned long to avoid confusion.
Still don't understand. Let's consider this example:
yury:linux$ cat tst.c
#include <stdio.h>
unsigned long data[1] = {0xabc};
void foo(unsigned long *data)
{
printf("foo: *data\t%lx\n", (unsigned long)*data);
printf("foo: data\t%lx\n", (unsigned long)data);
printf("foo: &data\t%lx\n", (unsigned long)&data);
}
void bar(unsigned long *data)
{
volatile unsigned long x[100];
printf("bar: *data\t%lx\n", (unsigned long)*data);
printf("bar: data\t%lx\n", (unsigned long)data);
printf("bar: &data\t%lx\n", (unsigned long)&data);
}
int main(int argc, char *argv[])
{
foo(data);
bar(data);
printf("main: *data\t%lx\n", (unsigned long)*data);
printf("main: data\t%lx\n", (unsigned long)data);
printf("main: &data\t%lx\n", (unsigned long)&data);
return 0;
}
yury:linux$ gcc tst.c -O0
yury:linux$ ./a.out
foo: *data abc
foo: data 555b2cef9010
foo: &data 7fff39d6e5f8
bar: *data abc
bar: data 555b2cef9010
bar: &data 7fff39d6e2c8
main: *data abc
main: data 555b2cef9010
main: &data 555b2cef9010
Data and *data have their meaning across scope boundary: a pointer and
a content. The &data is pretty much a random number - a pointer to
somewhere on a function's stack. Isn't?
> > > + max_ranges = MTE_MAX_RANGES;
> > > + /* Skip the leading bit indicating the inline case. */
> > > + mte_bitmap_read(bitmap, &bit_pos, 1);
> > > + largest_idx =
> > > + mte_bitmap_read(bitmap, &bit_pos, MTE_BITS_PER_LARGEST_IDX);
> >
> > Nit: really no need to split the line - we're OK with 100-chars per
> > line now.
>
> That's true, but I am relying on clang-format here (maybe we should
> extend the limit in .clang-format?)
If clang-format hurts readability, don't use it.
Thanks,
Yury
next prev parent reply other threads:[~2023-12-15 16:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 11:06 [PATCH v10-mte 0/7] Implement MTE tag compression for swapped pages Alexander Potapenko
2023-12-14 11:06 ` [PATCH v10-mte 1/7] lib/bitmap: add bitmap_{read,write}() Alexander Potapenko
2023-12-14 19:48 ` Yury Norov
2023-12-14 11:06 ` [PATCH v10-mte 2/7] lib/test_bitmap: add tests for bitmap_{read,write}() Alexander Potapenko
2023-12-14 19:50 ` Yury Norov
2023-12-14 11:06 ` [PATCH v10-mte 3/7] lib/test_bitmap: use pr_info() for non-error messages Alexander Potapenko
2023-12-14 19:51 ` Yury Norov
2023-12-14 11:06 ` [PATCH v10-mte 4/7] arm64: mte: implement CONFIG_ARM64_MTE_COMP Alexander Potapenko
2023-12-14 20:16 ` Yury Norov
2023-12-15 15:19 ` Alexander Potapenko
2023-12-15 16:35 ` Yury Norov [this message]
2023-12-15 17:01 ` Yury Norov
2023-12-18 11:42 ` Alexander Potapenko
2023-12-18 11:45 ` Alexander Potapenko
2023-12-14 11:06 ` [PATCH v10-mte 5/7] arm64: mte: add a test for MTE tags compression Alexander Potapenko
2023-12-14 11:06 ` [PATCH v10-mte 6/7] arm64: mte: add compression support to mteswap.c Alexander Potapenko
2023-12-14 11:06 ` [PATCH v10-mte 7/7] arm64: mte: implement CONFIG_ARM64_MTE_SWAP_STATS Alexander Potapenko
2023-12-14 20:21 ` Yury Norov
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=ZXyAXPxlmq11rp2Y@yury-ThinkPad \
--to=yury.norov@gmail.com \
--cc=aleksander.lobakin@intel.com \
--cc=alexandru.elisei@arm.com \
--cc=andreyknvl@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=eugenis@google.com \
--cc=glider@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=pcc@google.com \
--cc=syednwaris@gmail.com \
--cc=will@kernel.org \
--cc=william.gray@linaro.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