From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: Design doc of adding ACPI support for arm64 on Xen - version 4 Date: Wed, 19 Aug 2015 11:37:07 -0700 Message-ID: <55D4CCD3.4050103@citrix.com> References: <55D472D4.9010007@huawei.com> <55D4A95C020000780009BF99@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <55D4A95C020000780009BF99@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 , Shannon Zhao Cc: Hangaohuai , Ian Campbell , Stefano Stabellini , andrew@fubar.geek.nz, "Huangpeng (Peter)" , Stefano Stabellini , David Vrabel , Boris Ostrovsky , xen-devel , Parth Dixit , Christoffer Dall , Shannon Zhao List-Id: xen-devel@lists.xenproject.org Hi Jan, On 19/08/2015 07:05, Jan Beulich wrote: > ... wouldn't it make more sense to leave the generation of these > Linux-specific tags to Linux (and allow them to continue to be Linux > specific), by the same or a second, parallel (Xen) stub? This would > then also move at least some of the awkward table creation (and > ideally also copying) to that stub. We don't want to use a specific Xen entry path. So having a Xen stub is has to be rule out. Anyway as said multiple time, there is no issue to drop the "linux," in the properties. They are only used internally between the stub and the kernel (both are built in the same image). It would be pointless to create a stub just for renaming the properties... Regards, -- Julien Grall