WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

[XenPPC] [xenppc-unstable] [ppc] xencomm: print function names so we can

To: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Subject: [XenPPC] [xenppc-unstable] [ppc] xencomm: print function names so we can tell which one failed
From: Xen patchbot-xenppc-unstable <patchbot-xenppc-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 26 Jul 2006 18:40:42 +0000
Delivery-date: Wed, 26 Jul 2006 11:45:30 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id: Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post: <mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
# HG changeset patch
# User Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
# Node ID 518e1322992910df7f0fb29f51e54a4f4ef312ac
# Parent  b11a2c7b2989ddf71615d558494a8f29d52e6009
[ppc] xencomm: print function names so we can tell which one failed

Signed-off-by: Jimi Xenidis <jimix@xxxxxxxxxxxxxx>
---
 xen/arch/powerpc/usercopy.c |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diff -r b11a2c7b2989 -r 518e13229929 xen/arch/powerpc/usercopy.c
--- a/xen/arch/powerpc/usercopy.c       Fri Jul 07 13:57:26 2006 -0500
+++ b/xen/arch/powerpc/usercopy.c       Thu Jul 13 11:25:36 2006 -0400
@@ -86,7 +86,8 @@ xencomm_copy_from_guest(void *to, const 
     /* first we need to access the descriptor */
     desc = (struct xencomm_desc *)paddr_to_maddr((unsigned long)from);
     if (desc->magic != XENCOMM_MAGIC) {
-        printk("xencomm error: %p magic was 0x%x\n", desc, desc->magic);
+        printk("%s: error: %p magic was 0x%x\n",
+               __func__, desc, desc->magic);
         return n;
     }
 
@@ -153,7 +154,7 @@ xencomm_copy_to_guest(void *to, const vo
     /* first we need to access the descriptor */
     desc = (struct xencomm_desc *)paddr_to_maddr((unsigned long)to);
     if (desc->magic != XENCOMM_MAGIC) {
-        printk("xencomm error: %p magic was 0x%x\n", desc, desc->magic);
+        printk("%s error: %p magic was 0x%x\n", __func__, desc, desc->magic);
         return n;
     }
 
@@ -206,7 +207,7 @@ void xencomm_add_offset(void *handle, un
     /* first we need to access the descriptor */
     desc = (struct xencomm_desc *)paddr_to_maddr((unsigned long)handle);
     if (desc->magic != XENCOMM_MAGIC) {
-        printk("xencomm error: %p magic was 0x%x\n", desc, desc->magic);
+        printk("%s error: %p magic was 0x%x\n", __func__, desc, desc->magic);
         return;
     }
 

_______________________________________________
Xen-ppc-devel mailing list
Xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ppc-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [XenPPC] [xenppc-unstable] [ppc] xencomm: print function names so we can tell which one failed, Xen patchbot-xenppc-unstable <=