From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v4 0/2] Basic nested VMX test suite Date: Wed, 17 Jul 2013 12:54:24 +0200 Message-ID: <51E677E0.8070403@redhat.com> References: <1374041153-32235-1-git-send-email-yzt356@gmail.com> <20130717062151.GJ8981@redhat.com> <51E64D59.5050307@redhat.com> <20130717090320.GS11772@redhat.com> <51E66FB4.9080100@redhat.com> <20130717103153.GA19599@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Arthur Chunqi Li , kvm , Jan Kiszka To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:36218 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752848Ab3GQKyf (ORCPT ); Wed, 17 Jul 2013 06:54:35 -0400 In-Reply-To: <20130717103153.GA19599@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Il 17/07/2013 12:31, Gleb Natapov ha scritto: > On Wed, Jul 17, 2013 at 12:19:32PM +0200, Paolo Bonzini wrote: >> Il 17/07/2013 11:03, Gleb Natapov ha scritto: >>> This is not about taste, this is about hackability of the code. I will maintain it >>> and I want it to be as simple as possible given task it does. Looking similar to KVM >>> is additional bonus because the code will naturally look familiar to KVM maintainer. >> >> Then you may just as well write it yourself, no? > > What the point of the question? That may apply to any comment of any > reviewer if it does not point to a bug. So if it compiles - apply it? "Looking similar to KVM" is not an interesting property when writing a completely separate body of code. If we want to optimize for familiarity to the KVM maintainer, the best way to do that is to only have the KVM maintainer write code. > If you do it right there will be _not point in doing_ global jumps. The > control flow will be linear, the code will be much more readable. Ok, let's see what Arthur comes up with. Paolo