From mboxrd@z Thu Jan 1 00:00:00 1970 From: Boris Ostrovsky Subject: Re: [PATCH v2 1/6] xen: xensyms support Date: Tue, 10 Jun 2014 10:49:41 -0400 Message-ID: <53971B05.6020107@oracle.com> References: <1402076686-26586-1-git-send-email-boris.ostrovsky@oracle.com> <1402076686-26586-2-git-send-email-boris.ostrovsky@oracle.com> <539708A0.1020604@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <539708A0.1020604@citrix.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: David Vrabel Cc: kevin.tian@intel.com, xen-devel@lists.xen.org, dietmar.hahn@ts.fujitsu.com, JBeulich@suse.com List-Id: xen-devel@lists.xenproject.org On 06/10/2014 09:31 AM, David Vrabel wrote: > >> --- /dev/null >> +++ b/drivers/xen/xenfs/xensyms.c >> @@ -0,0 +1,124 @@ >> +#include >> +#include >> +#include >> +#include >> +#include >> +#include >> +#include >> +#include >> +#include >> +#include >> +#include "xenfs.h" >> + >> + >> +#define XEN_KSYM_NAME_LEN 127 /* Hypervisor may have different name length */ > Shouldn't this be exported in the hypervisor headers then? Jan objected to having this as part of the interface so now we pass this as a parameter to the hypervisor. I may return Xen's symbol length and, if it is larger than XEN_KSYM_NAME_LEN, do a WARN_ONCE() (in the next spin of the patch). -boris