|
From: | Paul Brook |
Subject: | Re: [Qemu-devel] [PATCH 00/21] Kemari for KVM 0.2 |
Date: | Mon, 29 Nov 2010 13:00:42 +0000 |
User-agent: | KMail/1.13.5 (Linux/2.6.36-trunk-amd64; KDE/4.4.5; x86_64; ; ) |
> >> Could you formulate the constraints so developers are aware of them in > >> the future and can protect the codebase. How about expanding the > >> Kemari wiki pages? > > > > If you like the idea above, I'm happy to make the list also on > > the wiki page. > > Here's a different question: what requirements must an emulated device > meet in order to be added to the Kemari supported whitelist? That's > what I want to know so that I don't break existing devices and can add > new devices that work with Kemari :). Why isn't it completely device agnostic? i.e. if a device has to care about Kemari at all (of vice-versa) then IMO you're doing it wrong. The whole point of the internal block/net APIs is that they isolate the host implementation details from the device emulation. Paul
[Prev in Thread] | Current Thread | [Next in Thread] |