From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753890Ab2GXMaz (ORCPT ); Tue, 24 Jul 2012 08:30:55 -0400 Received: from mail-lb0-f174.google.com ([209.85.217.174]:65212 "EHLO mail-lb0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753528Ab2GXMay (ORCPT ); Tue, 24 Jul 2012 08:30:54 -0400 Message-ID: <500E959D.70009@gmail.com> Date: Tue, 24 Jul 2012 14:31:25 +0200 From: Sasha Levin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120713 Thunderbird/13.0 MIME-Version: 1.0 To: Gleb Natapov CC: rusty@rustcorp.com.au, mst@redhat.com, penberg@kernel.org, asias.hejun@gmail.com, virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, avi@redhat.com, anthony@codemonkey.ws, wency@cn.fujitsu.com Subject: Re: [RFC 0/2] virtio: provide a way for host to monitor critical events in the device References: <1343075561-29316-1-git-send-email-levinsasha928@gmail.com> <20120724074434.GE26120@redhat.com> <500E9479.3050405@gmail.com> <20120724122824.GG26120@redhat.com> In-Reply-To: <20120724122824.GG26120@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 07/24/2012 02:28 PM, Gleb Natapov wrote: > On Tue, Jul 24, 2012 at 02:26:33PM +0200, Sasha Levin wrote: >> On 07/24/2012 09:44 AM, Gleb Natapov wrote: >>> On Mon, Jul 23, 2012 at 10:32:39PM +0200, Sasha Levin wrote: >>>> As it was discussed recently, there's currently no way for the guest to notify >>>> the host about panics. Further more, there's no reasonable way to notify the >>>> host of other critical events such as an OOM kill. >>>> >>>> This short patch series introduces a new device named virtio-notifier which >>>> does two simple things: >>>> >>>> 1. Provide a simple interface for the guest to notify the host of critical >>> To get early OOPSes virtio will have to be compiled into the kernel. If >>> your are so keen on using virtio for this though, why not just use >>> dedicated virtio serial channel? >> >> Let's separate between having log for these events and receiving notifications about them. >> >> For the log part, I can already run a simple serial console to dump everything somewhere. I'm more concerned about having notifications about something critical happening when the guest is already up and running. >> > I am talking about notifications. Run your notification protocol over > dedicated virtio-serial channel. Logs goes to virtio-console as you've > said. Ah, so just add another channel into virtio-serial to pass these notifications? Good idea - I'll look into it.