From: Gleb Natapov <gleb@redhat.com> To: Sasha Levin <levinsasha928@gmail.com> 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 Date: Tue, 24 Jul 2012 10:44:34 +0300 [thread overview] Message-ID: <20120724074434.GE26120@redhat.com> (raw) In-Reply-To: <1343075561-29316-1-git-send-email-levinsasha928@gmail.com> 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? > events. This is easily expandible to add support for any events we may find > interesting for the host to know about. > > 2. Provide an "echo" interface for the host to ping the guest. This allows > the host to ping the guest at intervals chosen by the host, and act > accordingly if no response has been received. > > Sasha Levin (2): > virtio: Introduce virtio-notifier > kvm tools: support virtio-notifier > > drivers/virtio/Kconfig | 11 ++ > drivers/virtio/Makefile | 1 + > drivers/virtio/virtio_notifier.c | 135 ++++++++++++++++++++ > include/linux/virtio_ids.h | 1 + > include/linux/virtio_notifier.h | 15 +++ > tools/kvm/Makefile | 1 + > tools/kvm/builtin-run.c | 6 + > tools/kvm/include/kvm/virtio-notifier.h | 9 ++ > tools/kvm/include/kvm/virtio-pci-dev.h | 1 + > tools/kvm/virtio/notifier.c | 203 +++++++++++++++++++++++++++++++ > 10 files changed, 383 insertions(+), 0 deletions(-) > create mode 100644 drivers/virtio/virtio_notifier.c > create mode 100644 include/linux/virtio_notifier.h > create mode 100644 tools/kvm/include/kvm/virtio-notifier.h > create mode 100644 tools/kvm/virtio/notifier.c > > -- > 1.7.8.6 > > -- > 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/ -- Gleb.
WARNING: multiple messages have this Message-ID (diff)
From: Gleb Natapov <gleb@redhat.com> To: Sasha Levin <levinsasha928@gmail.com> Cc: wency@cn.fujitsu.com, kvm@vger.kernel.org, mst@redhat.com, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, penberg@kernel.org, avi@redhat.com, anthony@codemonkey.ws Subject: Re: [RFC 0/2] virtio: provide a way for host to monitor critical events in the device Date: Tue, 24 Jul 2012 10:44:34 +0300 [thread overview] Message-ID: <20120724074434.GE26120@redhat.com> (raw) In-Reply-To: <1343075561-29316-1-git-send-email-levinsasha928@gmail.com> 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? > events. This is easily expandible to add support for any events we may find > interesting for the host to know about. > > 2. Provide an "echo" interface for the host to ping the guest. This allows > the host to ping the guest at intervals chosen by the host, and act > accordingly if no response has been received. > > Sasha Levin (2): > virtio: Introduce virtio-notifier > kvm tools: support virtio-notifier > > drivers/virtio/Kconfig | 11 ++ > drivers/virtio/Makefile | 1 + > drivers/virtio/virtio_notifier.c | 135 ++++++++++++++++++++ > include/linux/virtio_ids.h | 1 + > include/linux/virtio_notifier.h | 15 +++ > tools/kvm/Makefile | 1 + > tools/kvm/builtin-run.c | 6 + > tools/kvm/include/kvm/virtio-notifier.h | 9 ++ > tools/kvm/include/kvm/virtio-pci-dev.h | 1 + > tools/kvm/virtio/notifier.c | 203 +++++++++++++++++++++++++++++++ > 10 files changed, 383 insertions(+), 0 deletions(-) > create mode 100644 drivers/virtio/virtio_notifier.c > create mode 100644 include/linux/virtio_notifier.h > create mode 100644 tools/kvm/include/kvm/virtio-notifier.h > create mode 100644 tools/kvm/virtio/notifier.c > > -- > 1.7.8.6 > > -- > 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/ -- Gleb.
next prev parent reply other threads:[~2012-07-24 7:44 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-07-23 20:32 [RFC 0/2] virtio: provide a way for host to monitor critical events in the device Sasha Levin 2012-07-23 20:32 ` Sasha Levin 2012-07-23 20:32 ` [RFC 1/2] virtio: Introduce virtio-notifier Sasha Levin 2012-07-23 20:32 ` Sasha Levin 2012-07-23 20:32 ` [RFC 2/2] kvm tools: support virtio-notifier Sasha Levin 2012-07-23 20:32 ` Sasha Levin 2012-07-24 4:55 ` [RFC 0/2] virtio: provide a way for host to monitor critical events in the device Rusty Russell 2012-07-24 4:55 ` Rusty Russell 2012-07-24 4:55 ` Rusty Russell 2012-07-24 8:26 ` Dor Laor 2012-07-24 8:26 ` Dor Laor 2012-07-24 12:30 ` Sasha Levin 2012-07-24 12:30 ` Sasha Levin 2012-07-24 12:46 ` Dor Laor 2012-07-24 12:46 ` Dor Laor 2012-07-24 13:01 ` Sasha Levin 2012-07-24 13:01 ` Sasha Levin 2012-07-25 0:36 ` Rusty Russell 2012-07-25 0:36 ` Rusty Russell 2012-07-25 8:46 ` Amit Shah 2012-07-25 8:46 ` Amit Shah 2012-07-24 12:23 ` Sasha Levin 2012-07-24 12:23 ` Sasha Levin 2012-07-24 7:44 ` Gleb Natapov [this message] 2012-07-24 7:44 ` Gleb Natapov 2012-07-24 12:26 ` Sasha Levin 2012-07-24 12:28 ` Gleb Natapov 2012-07-24 12:28 ` Gleb Natapov 2012-07-24 12:31 ` Sasha Levin 2012-07-24 12:31 ` Sasha Levin 2012-07-24 12:33 ` Gleb Natapov 2012-07-24 12:33 ` Gleb Natapov 2012-07-24 12:26 ` Sasha Levin
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20120724074434.GE26120@redhat.com \ --to=gleb@redhat.com \ --cc=anthony@codemonkey.ws \ --cc=asias.hejun@gmail.com \ --cc=avi@redhat.com \ --cc=kvm@vger.kernel.org \ --cc=levinsasha928@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=mst@redhat.com \ --cc=penberg@kernel.org \ --cc=rusty@rustcorp.com.au \ --cc=virtualization@lists.linux-foundation.org \ --cc=wency@cn.fujitsu.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.