From mboxrd@z Thu Jan 1 00:00:00 1970 From: Don Slutz Subject: Re: [PATCH v13 5/8] xen: Add vmware_port support Date: Sun, 20 Dec 2015 13:15:03 -0500 Message-ID: <5676F027.6030101@Gmail.com> References: <1448747105-19966-1-git-send-email-Don.Slutz@Gmail.com> <1448747105-19966-6-git-send-email-Don.Slutz@Gmail.com> <56718D6702000078000C04D2@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <56718D6702000078000C04D2@prv-mh.provo.novell.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: Jan Beulich Cc: Jun Nakajima , Tim Deegan , Kevin Tian , Wei Liu , Ian Campbell , Stefano Stabellini , George Dunlap , Andrew Cooper , Ian Jackson , xen-devel@lists.xen.org, Aravind Gopalakrishnan , Suravee Suthikulpanit , Keir Fraser , Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org On 12/16/15 10:12, Jan Beulich wrote: >>>> On 28.11.15 at 22:45, wrote: >> --- >> v13: >> Changed to uint32_t arch_flags, since the emulation_flags is this. > > I don't really understand this sentence, and I also don't understand > why you couldn't just use another XEN_X86_EMU_ flag, e.g. > XEN_X86_EMU_VMWARE_PORT (which would be the first one outside > the current all-or-nothing model). > Next attempt at that sentence: During re-base of the patch, changed uint64_t arch_flags to uint32_t arch_flags. This appeared to be ok because the added emulation_flags was a unit32_t. I have no reason not to use another XEN_X86_EMU_ flag. It was not clear when I was re-baseing that it would be ok to do so. Will drop arch_flags and use XEN_X86_EMU_VMWARE_PORT which will not be added to "all". -Don Slutz > Jan >