[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 12:26 PM, Wen Congyang wrote:
> >> If so, is this channel visible to guest userspace? If the channle is visible to guest
> >> userspace, the program running in userspace may write the same message to the channel.
> >>
> >
> > Surely there's some kind of access control on channels.
> The virtio-serial depends on more things than touching the hypervisor. So I think touching
> the hypervisor is more reliable than using virtio-serial device, and it is very simple and
> easy to use.
> If we pass something from guest userspace to host, we can use virtio-serial. But If we pass
> something from guest kernelspace to host, I still prefer to touch the hypervisor.

There's no argument that it's easier. My concern is different, we're
adding more and more stuff to the hypervisor because it's easier, which
bloats it. Every time we do it we add to compatibility and security

The panic notification is *really* simple, so I don't expect it to cause
a lot of problems. But still, if it's possible not to change the
hypervisor, we must make an effort in that direction.

error compiling committee.c: too many arguments to function

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