Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1609954

Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe

From Steven Rostedt <rostedt@goodmis.org>
Newsgroups linux.kernel
Subject Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe
Date 2017-03-27 17:40 +0200
Message-ID <tpEUp-1P8-13@gated-at.bofh.it> (permalink)
References (1 earlier) <toBYD-5oX-19@gated-at.bofh.it> <toCrE-5z0-13@gated-at.bofh.it> <toTVw-1li-3@gated-at.bofh.it> <tpDEZ-QR-17@gated-at.bofh.it> <tpEhH-17e-15@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Mon, 27 Mar 2017 16:53:09 +0200
Arnd Bergmann <arnd@arndb.de> wrote:


> > Actually, I believe that "%zd" will work. It's made to work with size_t
> > which is long long on 32 and long on 64.  
> 
> size_t is always 'long', not 'long long'. We have %pad for dma_addr_t
> which may be 'long' or 'long long', but it is configuration dependent
> which one it is on 32-bit.

Ah your right. It was that it was defined as "int" on 32 and "long" on
64, and that caused problems with warnings when using "%d" when it was
defined as long.

> 
> We could probably introduce a %pts format string for timespec64
> and have that pretty-printed.

Hmm, probably don't want a %p as that suggests its a pointer, which it
should not be. Unless we pass in the address of the number.

-- Steve

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH] trace: Make trace_hwlat timestamp y2038 safe Deepa Dinamani <deepa.kernel@gmail.com> - 2017-03-26 23:00 +0200
  Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe kbuild test robot <lkp@intel.com> - 2017-03-27 11:30 +0200
    Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe Arnd Bergmann <arnd@arndb.de> - 2017-03-27 12:00 +0200
      Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe Steven Rostedt <rostedt@goodmis.org> - 2017-03-27 16:40 +0200
        Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe Arnd Bergmann <arnd@arndb.de> - 2017-03-27 17:00 +0200
          Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe Arnd Bergmann <arnd@arndb.de> - 2017-03-27 17:40 +0200
            Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe Steven Rostedt <rostedt@goodmis.org> - 2017-03-27 18:20 +0200
          Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe Steven Rostedt <rostedt@goodmis.org> - 2017-03-27 17:40 +0200
          Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe Deepa Dinamani <deepa.kernel@gmail.com> - 2017-03-27 23:10 +0200
            Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe Arnd Bergmann <arnd@arndb.de> - 2017-03-28 09:30 +0200
  Re: [PATCH] trace: Make trace_hwlat timestamp y2038 safe kbuild test robot <lkp@intel.com> - 2017-03-27 12:10 +0200

csiph-web