From mboxrd@z Thu Jan 1 00:00:00 1970 From: Don Slutz Subject: Re: [PATCH for-4.5 v6 05/16] tools: Add vmware_port support Date: Mon, 22 Sep 2014 12:42:35 -0400 Message-ID: <5420517B.9060602@terremark.com> References: <1411236447-7435-1-git-send-email-dslutz@verizon.com> <1411236447-7435-6-git-send-email-dslutz@verizon.com> <1411393315.18331.104.camel@kazak.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1411393315.18331.104.camel@kazak.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Don Slutz Cc: Tim Deegan , Kevin Tian , Keir Fraser , Jun Nakajima , Stefano Stabellini , George Dunlap , Ian Jackson , Eddie Dong , xen-devel@lists.xen.org, Aravind Gopalakrishnan , Jan Beulich , Andrew Cooper , Boris Ostrovsky , Suravee Suthikulpanit List-Id: xen-devel@lists.xenproject.org On 09/22/14 09:41, Ian Campbell wrote: > On Sat, 2014-09-20 at 14:07 -0400, Don Slutz wrote: >> This new libxl_domain_create_info field is used to set >> XEN_DOMCTL_CDF_vmware_port for the xc_domain_create() routine. > Does this really need to be a CDF, rather than a domctl/hvm param? It makes the setting up of v->arch.hvm_vmx.exception_bitmap happen at the right time. domctl/hvm param happen later in the start of a domain. > The latter would allow moving to buildinfo.u.hvm, which would be nicer > from the libxl PoV, I think. I could not find "buildinfo.u.hvm": dcs-xen-54:~/xen>git grep buildinfo.u.hvm dcs-xen-54:~/xen> So unable to comment. >> In xen it is is_vmware_port_enabled. >> >> If is_vmware_port_enabled then >> enable a limited support of VMware's hyper-call. >> >> VMware's hyper-call is also known as VMware Backdoor I/O Port. >> >> Signed-off-by: Don Slutz > Is it useful to be able to configure this independently of the vmware_hw > version? Yes. > If yes then I still think you would want to set the default based on > vmware-hw, wouldn't you? I guess so since this is a BOOLEAN. Currently I do not know of a way to say "set vmware_hw to 7 if vmware_port is true and vmware_hw is not specified". Which would be the inverse. I lean to not having the default of vmware_port based on vmware_hw. -Don Slutz > Ian. >