linux-kernel - Re: [GIT PULL] Native Linux KVM tool for 3.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Jul 2011 12:48:33 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Alexander Graf <agraf@...e.de>, Pekka Enberg <penberg@...nel.org>,
	Jan Kiszka <jan.kiszka@....de>, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	kvm@...r.kernel.org, gorcunov@...il.com, levinsasha928@...il.com,
	asias.hejun@...il.com, prasadjoshi124@...il.com
Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1

On 07/25/2011 12:41 PM, Ingo Molnar wrote:
> Look at tools/kvm/ - i cannot do anything useful without a Linux
> kernel under it. It's as deeply bound to the Linux kernel as it gets.

The actual code that interacts with the kernel is pretty small, and will 
grow smaller (as a fraction) in time.

> Then look at the actual drivers and interfaces within tools/kvm/.
> It's using the same symbols and conventions for 'guest' and 'host'
> side.
>
> Check out tools/kvm/hw/i8042.c and match it up with
> include/linux/serio.h and drivers/input/serio/i8042.c - you can
> literally walk from one side to the other and understand how guest
> and host are tightly related not just functionality but also
> implementation wise.
>
> This is how Qemu should be doing it as well btw., to ease the
> debugging of host/guest interaction bugs and to ease development.

No.  That ties the guest and host interfaces together.  If you change 
the guest to use a feature you didn't implement previously in the host, 
it's suddenly broken when virtualized.

The right thing is to implement the hardware interface exactly per spec, 
and ignore the guest(s) completely except for testing and performance.


-- 
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/