From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH 00/21] Kemari for KVM 0.2 Date: Mon, 29 Nov 2010 15:56:18 +0000 Message-ID: <201011291556.18718.paul@codesourcery.com> References: <1290665220-26478-1-git-send-email-tamura.yoshiaki@lab.ntt.co.jp> <201011291456.16360.paul@codesourcery.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: ohmura.kei@lab.ntt.co.jp, mtosatti@redhat.com, stefanha@linux.vnet.ibm.com, kvm@vger.kernel.org, Stefan Hajnoczi , dlaor@redhat.com, qemu-devel@nongnu.org, vatsa@linux.vnet.ibm.com, Blue Swirl , aliguori@us.ibm.com, avi@redhat.com, psuriset@linux.vnet.ibm.com, ananth@in.ibm.com To: Yoshiaki Tamura Return-path: Received: from mail.codesourcery.com ([38.113.113.100]:48859 "EHLO mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751689Ab0K2P4i (ORCPT ); Mon, 29 Nov 2010 10:56:38 -0500 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: > >> Sorry, I didn't get what you're trying to tell me. My plan would > >> be to initially start from a subset of devices, and gradually > >> grow the number of devices that Kemari works with. While this > >> process, it'll include what you said above, file a but and/or fix > >> the code. Am I missing what you're saying? > > > > My point is that the whitelist shouldn't exist at all. Devices either > > support migration or they don't. Having some sort of separate whitelist > > is the wrong way to determine which devices support migration. > > Alright! > > Then if a user encounters a problem with Kemari, we'll fix Kemari > or the devices or both. Correct? Correct. Paul