On Thu, Jan 11, 2018 at 09:26:28PM +, Liang, Kan wrote:
>
> > On Thu, Dec 21, 2017 at 10:08:44AM -0800, kan.li...@intel.com wrote:
> >
> > SNIP
> >
> > > +/*
> > > + * Report the start and end of the available data in ringbuffer
> > > + */
> > > +int perf_mmap__read_init(struct perf_mmap
On Thu, Jan 11, 2018 at 09:26:28PM +, Liang, Kan wrote:
>
> > On Thu, Dec 21, 2017 at 10:08:44AM -0800, kan.li...@intel.com wrote:
> >
> > SNIP
> >
> > > +/*
> > > + * Report the start and end of the available data in ringbuffer
> > > + */
> > > +int perf_mmap__read_init(struct perf_mmap
> On Thu, Dec 21, 2017 at 10:08:44AM -0800, kan.li...@intel.com wrote:
>
> SNIP
>
> > +/*
> > + * Report the start and end of the available data in ringbuffer
> > + */
> > +int perf_mmap__read_init(struct perf_mmap *map, bool overwrite,
> > +u64 *start, u64 *end)
> > {
> >
> On Thu, Dec 21, 2017 at 10:08:44AM -0800, kan.li...@intel.com wrote:
>
> SNIP
>
> > +/*
> > + * Report the start and end of the available data in ringbuffer
> > + */
> > +int perf_mmap__read_init(struct perf_mmap *map, bool overwrite,
> > +u64 *start, u64 *end)
> > {
> >
On Thu, Dec 21, 2017 at 10:08:44AM -0800, kan.li...@intel.com wrote:
SNIP
> +/*
> + * Report the start and end of the available data in ringbuffer
> + */
> +int perf_mmap__read_init(struct perf_mmap *map, bool overwrite,
> + u64 *start, u64 *end)
> {
> - u64 head =
On Thu, Dec 21, 2017 at 10:08:44AM -0800, kan.li...@intel.com wrote:
SNIP
> +/*
> + * Report the start and end of the available data in ringbuffer
> + */
> +int perf_mmap__read_init(struct perf_mmap *map, bool overwrite,
> + u64 *start, u64 *end)
> {
> - u64 head =
> On Thu, Dec 21, 2017 at 10:08:44AM -0800, kan.li...@intel.com wrote:
> > From: Kan Liang
> >
> > The perf record has specific codes to calculate the ringbuffer
> > position for both overwrite and non-overwrite mode.
> > The perf top will support both modes later.
> > It is
> On Thu, Dec 21, 2017 at 10:08:44AM -0800, kan.li...@intel.com wrote:
> > From: Kan Liang
> >
> > The perf record has specific codes to calculate the ringbuffer
> > position for both overwrite and non-overwrite mode.
> > The perf top will support both modes later.
> > It is useful to make the
On Thu, Dec 21, 2017 at 10:08:44AM -0800, kan.li...@intel.com wrote:
> From: Kan Liang
>
> The perf record has specific codes to calculate the ringbuffer position
> for both overwrite and non-overwrite mode.
> The perf top will support both modes later.
> It is useful to
On Thu, Dec 21, 2017 at 10:08:44AM -0800, kan.li...@intel.com wrote:
> From: Kan Liang
>
> The perf record has specific codes to calculate the ringbuffer position
> for both overwrite and non-overwrite mode.
> The perf top will support both modes later.
> It is useful to make the specific codes
10 matches
Mail list logo