From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH v2 11/12] xenctx: Dump registers via hvm
 info if available.
Date: Fri, 8 Nov 2013 10:29:42 +0000
Message-ID: <527CBD16.5060903@citrix.com>
References: <1383768500-4245-1-git-send-email-dslutz@terremark.com>
	<1383768500-4245-12-git-send-email-dslutz@terremark.com>
	<527AA7F7.7010901@citrix.com> <527BE250.50804@terremark.com>
	<1383905597.3189.68.camel@kazak.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1383905597.3189.68.camel@kazak.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>, George Dunlap <george.dunlap@eu.citrix.com>, Don Slutz <Don@CloudSwitch.com>, Ian Jackson <ian.jackson@eu.citrix.com>, Don Slutz <dslutz@verizon.com>, xen-devel@lists.xen.org, Jan Beulich <JBeulich@suse.com>
List-Id: xen-devel@lists.xenproject.org

On 08/11/13 10:13, Ian Campbell wrote:
> On Thu, 2013-11-07 at 13:56 -0500, Don Slutz wrote:
>> On 11/06/13 15:35, Andrew Cooper wrote:
>>> I would certainly not object if someone were to merge these two tools
>>> into one.  It is particularly awkward as xen-hvmctx ends up being
>>> installed into /usr/sbin/ and is therefore on the $PATH, while xenctx
>>> ends up off the $PATH in /usr/lib/xen/bin/
>> The way I would do this is to make 1 source file, delete the 2nd, and
>> install the same code as both xenctx and xen-hvmctx.  argv[0] can be
>> decoded and the default action adjusted based on the name. In this
>> case there would be command line options to get the current old output
>> for each tool.
> Personally I don't think we need to retain any kind of CLI compatibility
> for such developer focused tools. I'd be perfectly happy for the
> (sensible) functionality of hvmctx to be merged into xenctx and to then
> disappear.
>
> Ian.
>

Agreed - I would much prefer one single tool with a useful set of
options rather than keeping around something which vaguely looks like an
older tool for the sake of it.

This is strictly a dev tool rather than production tool.

~Andrew