From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH v4 0/9] add xenalyze to staging Date: Tue, 9 Jun 2015 07:31:39 -0400 Message-ID: <5576CE9B.4050101@citrix.com> References: <1432369458-7587-1-git-send-email-olaf@aepfle.de> <1433326259.7108.53.camel@citrix.com> <556ED87F.50204@citrix.com> <20150609101859.GA10083@aepfle.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20150609101859.GA10083@aepfle.de> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Olaf Hering Cc: George Dunlap , Ian Campbell , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Hi Olaf, On 09/06/2015 06:18, Olaf Hering wrote: > On Wed, Jun 03, Julien Grall wrote: > >> xentrace is not working as we don't have the infrastructure for ARM in Xen. > > Why is that? After a very quick look __trace_var is available > unconditionally. Multiple reasons, the shared page for trace is not correctly exposed, __trace_var/__trace_hypercall is not even used on ARM. I may miss some other bugs that I didn't spot while looking to the code. So I don't think we should build a non-working binary until someone fixes the various problem of the trace system on ARM. Regards, -- Julien Grall