Date: Fri, 16 Feb 2007 10:17:42 -0800
From: Andrew Morton <akpm@linux-foundation.org>
To: Michael Holzheu <holzheu2@linux.vnet.ibm.com>
Cc: johnpol@2ka.mipt.ru, mschwid2@de.ltcfwd.linux.ibm.com,
       heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: Using kevent for event logging?
Message-Id: <20070216101742.b3877aca.akpm@linux-foundation.org>
In-Reply-To: <20070216155708.589cd47a.holzheu2@linux.vnet.ibm.com>
References: <20070216155708.589cd47a.holzheu2@linux.vnet.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1055
Lines: 23

On Fri, 16 Feb 2007 15:57:08 +0100 Michael Holzheu <holzheu2@linux.vnet.ibm.com> wrote:

> Hallo Evgeniy,
> 
> On s390 we are looking for a good mechanism to notify userspace
> about kernel events. Currently such events are handled with printks
> in most cases. There are automation tools, which want to automatically
> react on kernel events. To get the event information, these tools are
> parsing printks, which is not a really good mechanism for that
> purpose.
> 
> When I read about kevents, I was wondering, if it could be used to solve
> this problem. E.g. it would be possible to put an event number into a
> kevent and provide another interface to get the complete event data.
> 

Wouldn't one simply transport the info across netlink, use kevent (or
select/poll/whatever) for readiness notification?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/