Re: [patch] kernel events layer

[Deepak Saxena]

On Jul 26 2004, at 15:58, Perez-Gonzalez, Inaky was caught saying:
> Agreed -- I guess what I am looking for is a regular way to link the 
> instance of the object (if any) that caused the message, so it is easier 
> to take action.
> 
> For a silly example, IDE, I want to know which hard drive had a read 
> error; knowing that it came from drivers/ide/ide-disk.c is useful, but
> quite limited; it doesn't tell me which drive I need to babysit and 
> maybe swap. Certainly the message can print that information as part of
> the text, but chances up we'll end up with something like printk again
> if following that path.

I think that is what the ancillary data field is for atm. Looking
at Robert's original post, he is using "arch/kernel/cpu" as the
object name and stuffing "CPU 0" in the ancillary data.  I think
everyone's agreed that this is not the way to do it, so let's see
what Greg and Robert come up with.

/me goes back to hidding in embedded land

~Deepak

-- 
Deepak Saxena - dsaxena at plexity dot net - http://www.plexity.net/

"Unlike me, many of you have accepted the situation of your imprisonment and
 will die here like rotten cabbages." - Number 6
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/