Re: [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c

Hello.

On Monday 13 November 2006 00:23, Sergei Shtylyov wrote:
> In addition to clock wrap check being falsely triggered with 32-bit
> cycles_t, as noticed to Kevin Hilman, there's another issue: using %Lx
> format to print 32-bit values warrants erroneous values on 32-bit machines
> like ARM and PPC32.

   There's many more warnings with other options turned on, so I'll post an updated patch soon...

WBR, Sergei

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c
    • From: Sergei Shtylyov <[email protected]>

• Prev by Date: [PATCH 3/4] SELinux: ensure keys constant in hashtab_search
• Next by Date: [PATCH 4/4] SELinux: validate kernel object classes and permissions
• Previous by thread: [PATCH] 2.6.18-rt7: fix more issues with 32-bit cycles_t in latency_trace.c
• Next by thread: 2.6.19-rc4-mm1: writev() _functional_ regression
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]