From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aravind Gopalakrishnan Subject: Re: Xen 4.6 Development Update (two months reminder) Date: Thu, 12 Mar 2015 09:15:01 -0500 Message-ID: <55019F65.2070803@amd.com> References: <55018C770200007800068F44@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YW3tI-0002iL-9C for xen-devel@lists.xenproject.org; Thu, 12 Mar 2015 14:15:12 +0000 In-Reply-To: <55018C770200007800068F44@mail.emea.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 , Wei.Liu2@citrix.com, konrad.wilk@oracle.com Cc: elena.ufimtseva@oracle.com, artem.mygaiev@globallogic.com, quan.xu@intel.com, ian.jackson@eu.citrix.com, oleksandr.dmytryshyn@globallogic.com, chegger@amazon.de, Chun Yan Liu , edmund.h.white@intel.com, fabio.fantoni@m2r.biz, chao.p.peng@linux.intel.com, edgar.iglesias@gmail.com, zhigang.x.wang@oracle.com, parth.dixit@linaro.org, dgolomb@seas.upenn.edu, manishjaggi.oss@gmail.com, kai.huang@linux.intel.com, tamas.lengyel@zentific.com, Paul.Skentzos@dornerworks.com, jtweaver@hawaii.edu, vijay.kilari@gmail.com, oleksandr.tyshchenko@globallogic.com, guijianfeng@cn.fujitsu.com, Vijaya.Kumar@caviumnetworks.com, josh.whitehead@dornerworks.com, anthony.perard@citrix.com, xen-devel@lists.xenproject.org, eshelton@pobox.com, olaf@aepfle.de, ian.campbell@citrix.com, wency@cn.fujitsu.com, julien.grall@linaro.org, robert.vanvossen@dornerworks.com, frediano.ziglio@hua List-Id: xen-devel@lists.xenproject.org On 3/12/2015 6:54 AM, Jan Beulich wrote: >> * amd_ucode cleanups, verify patch size(enhancement) (mostly in master >> except one patch) > Which one? This is in reference to the patches to microcode_amd and it's all 'done' in 4.5 itself. I think when we were tracking this, commit 8b24b07e was not in master branch. Hence the status. We can remove this from the current list of features to be tracked for 4.6 IMO. >> * Feature masking MSR support (enhancement) (in master) > What is this about? Or what status does "in master" actually > refer to? > > This is in reference to commit e74de9c0. And this is also complete, and can be removed from the list. Before I knew what status values to apply to a feature, I had used 'in master' to convey that patches are in master branch. The feature tracking list has maintained this remnant. In fact, all these patches in the list are 'done' as of 4.5 itself and can be removed IMO. *Data breakpoint Extension support (new-feat) (in master) *Support BRCM TruManage chip (Serial over LAN support) (new-feat) (in master) *fix vmce_amd* functions, unify mce_amd mcheck initialization (fixes/cleanups) *multiple AMD container files appended together in initrd (early initramfs) -Aravind and Suravee Thanks, -Aravind.