From: Leo Yan <leo.yan@linaro.org>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: "Suzuki K. Poulose" <suzuki.poulose@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Coresight ML <coresight@lists.linaro.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Mike Leach <mike.leach@linaro.org>
Subject: Re: [PATCH V2 6/6] perf tools: Properly set the value of 'old' and 'head' in snapshot mode
Date: Tue, 21 May 2019 09:54:59 +0800 [thread overview]
Message-ID: <20190521015459.GC6329@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <CANLsYkyTKTQJhMJ-p-_z6AvE4UfmPJSt1pdDVvwRCBOrPK+B7Q@mail.gmail.com>
On Mon, May 20, 2019 at 01:53:29PM -0600, Mathieu Poirier wrote:
[...]
> > > +static bool cs_etm_buffer_has_wrapped(unsigned char *buffer,
> > > + size_t buffer_size, u64 head)
> > > +{
> > > + u64 i, watermark;
> > > + u64 *buf = (u64 *)buffer;
> > > + size_t buf_size = buffer_size;
> > > +
> > > + /*
> > > + * We want to look the very last 512 byte (chosen arbitrarily) in
> > > + * the ring buffer.
> > > + */
> > > + watermark = buf_size - 512;
> > > +
> > > + /*
> > > + * @head is continuously increasing - if its value is equal or greater
> > > + * than the size of the ring buffer, it has wrapped around.
> > > + */
> > > + if (head >= buffer_size)
> > > + return true;
> > > +
> > > + /*
> > > + * The value of @head is somewhere within the size of the ring buffer.
> > > + * This can be that there hasn't been enough data to fill the ring
> > > + * buffer yet or the trace time was so long that @head has numerically
> > > + * wrapped around. To find we need to check if we have data at the very
> > > + * end of the ring buffer. We can reliably do this because mmap'ed
> > > + * pages are zeroed out and there is a fresh mapping with every new
> > > + * session.
> > > + */
> > > +
> > > + /* @head is less than 512 byte from the end of the ring buffer */
> > > + if (head > watermark)
> > > + watermark = head;
> > > +
> > > + /*
> > > + * Speed things up by using 64 bit transactions (see "u64 *buf" above)
> > > + */
> > > + watermark >>= 3;
> > > + buf_size >>= 3;
> > > +
> > > + /*
> > > + * If we find trace data at the end of the ring buffer, @head has
> > > + * been there and has numerically wrapped around at least once.
> > > + */
> > > + for (i = watermark; i < buf_size; i++)
> > > + if (buf[i])
> >
> > I think here should be:
> > if (buf[i << 3])
> >
>
> It would be if buf[] was a char *, but it is a u64 *.
You are right, I missed that. Sorry for noise.
Thanks,
Leo Yan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-21 1:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 19:40 [PATCH V2 0/6] coresight: Fix snapshot mode Mathieu Poirier
2019-05-14 19:40 ` [PATCH V2 1/6] coresight: etb10: Properly set AUX buffer head in " Mathieu Poirier
2019-05-15 9:45 ` Suzuki K Poulose
2019-05-15 14:28 ` Mathieu Poirier
2019-05-16 9:41 ` Suzuki K Poulose
2019-05-14 19:40 ` [PATCH V2 2/6] coresight: tmc-etr: " Mathieu Poirier
2019-05-14 19:40 ` [PATCH V2 3/6] coresight: tmc-etf: " Mathieu Poirier
2019-05-14 19:40 ` [PATCH V2 4/6] coresight: tmc-etf: Fix snapshot mode update function Mathieu Poirier
2019-05-14 19:40 ` [PATCH V2 5/6] coresight: perf: Don't set the truncated flag in snapshot mode Mathieu Poirier
2019-05-16 15:22 ` Suzuki K Poulose
2019-05-14 19:40 ` [PATCH V2 6/6] perf tools: Properly set the value of 'old' and 'head' " Mathieu Poirier
2019-05-16 15:00 ` Leo Yan
2019-05-20 19:53 ` Mathieu Poirier
2019-05-21 1:54 ` Leo Yan [this message]
2019-05-16 15:09 ` [PATCH V2 0/6] coresight: Fix " Leo Yan
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=20190521015459.GC6329@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=suzuki.poulose@arm.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