[lkml]   [2012]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/2 v3] kvm: notify host when guest panicked
On 03/14/2012 01:11 PM, Wen Congyang wrote:
> >
> > I don't think we want to use the driver. Instead, have a small piece of
> > code that resets the device and pushes out a string (the panic message?)
> > without any interrupts etc.
> >
> > It's still going to be less reliable than a hypercall, I agree.
> Do you still want to use complicated and less reliable way?

Are you willing to try it out and see how complicated it really is?

While it's more complicated, it's also more flexible. You can
communicate the panic message, whether the guest is attempting a kdump
and its own recovery or whether it wants the host to do it, etc., you
can communicate less severe failures like oopses.

> I think the other ones prefer to touch the hypervisor.

I understand the sentiment. Your patches are simple and easy. But my
feeling is that the kernel has become too complicated already and I'm
looking for ways to limit changes.

error compiling committee.c: too many arguments to function

 \ /
  Last update: 2012-03-14 14:11    [W:0.106 / U:4.216 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site