It looks like oprofile takes an approach similar to gprof: It tries to show you how much time is spent in each function.
The new trace command, on the other hand, traces kernel events: page faults, system calls, fork/exec commands, and so on. Obviously, there's some overlap between the two activities (particularly as both tools mature), but for now, it looks like the 'trace' command records rather different data than oprofile. Of course, I don't know anything about oprofile beyond what's on their introductory web pages, so maybe I'm overlooking something.
The new trace command, on the other hand, traces kernel events: page faults, system calls, fork/exec commands, and so on. Obviously, there's some overlap between the two activities (particularly as both tools mature), but for now, it looks like the 'trace' command records rather different data than oprofile. Of course, I don't know anything about oprofile beyond what's on their introductory web pages, so maybe I'm overlooking something.