Thanks for the feedback Michael.
Michael Raymond wrote:
> Karim, three comments:
> - CPU ID needs be bigger than 8-bits, else you can only support up to 256p
I don't mind. uint16_t?
> - Are 8-bit event IDs big enough? A comment explainig that sub-IDs should
> be placed within the log record would help avoid the issue of the 8-bit
> space disappearing too quickly
.... uint16_t?
> - To avoid the problem of RelayFS non-reenterancy I think ltt_log_event() will
> need a hook at its end so that whatever mechanism was used to avoid the
> situation can be disabled.
I think this one needs more thinking ... I did think about adding such a
hook, but I didn't like the idea of it, it just seems unclean. After all
the problem is limited to a very small subset of events, namely NMIs and
page fault traps. One thing I was thinking about is that in both these
cases there's always an entry event and an exit event. ltt_mux could then
coordinate using these events. IOW, if it just got an NMI entry, it
doesn't allow any other event to get logged until it sees the NMI exit
go by ... same for page faults. By doing this, we can just keep just one
hook: ltt_mux. Right?
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || [email protected] || 1-866-677-4546
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |