All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: levon@movementarian.org
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [PATCH] fixes for oprofile on ppc64
Date: Mon, 2 Dec 2002 19:16:45 +1100	[thread overview]
Message-ID: <20021202081645.GA12110@krispykreme> (raw)


Hi,

Here are a few fixes I needed when porting oprofile to ppc64:

- __PAGE_OFFSET isnt defined for all architectures, use PAGE_OFFSET
  instead
- include linux/cache.h everywhere we use ____cacheline_aligned etc. 
  Otherwise we end up with a structure called ____cacheline_aligned
  and no alignment :(

Anton


===== drivers/oprofile/buffer_sync.c 1.4 vs edited =====
--- 1.4/drivers/oprofile/buffer_sync.c	Tue Nov  5 08:01:22 2002
+++ edited/drivers/oprofile/buffer_sync.c	Fri Nov 29 14:31:07 2002
@@ -245,7 +245,7 @@
  
 static inline int is_kernel(unsigned long val)
 {
-	return val > __PAGE_OFFSET;
+	return val > PAGE_OFFSET;
 }
 
 
===== drivers/oprofile/cpu_buffer.c 1.2 vs edited =====
--- 1.2/drivers/oprofile/cpu_buffer.c	Wed Nov 27 06:38:46 2002
+++ edited/drivers/oprofile/cpu_buffer.c	Fri Nov 29 14:30:18 2002
@@ -21,6 +21,7 @@
 #include <linux/vmalloc.h>
 #include <linux/smp.h>
 #include <linux/errno.h>
+#include <linux/cache.h>
  
 #include "cpu_buffer.h"
 #include "oprof.h"
===== drivers/oprofile/cpu_buffer.h 1.1 vs edited =====
--- 1.1/drivers/oprofile/cpu_buffer.h	Wed Oct 16 07:45:51 2002
+++ edited/drivers/oprofile/cpu_buffer.h	Mon Dec  2 12:25:16 2002
@@ -12,6 +12,7 @@
 
 #include <linux/types.h>
 #include <linux/spinlock.h>
+#include <linux/cache.h>
  
 struct task_struct;
  


                 reply	other threads:[~2002-12-02  8:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20021202081645.GA12110@krispykreme \
    --to=anton@samba.org \
    --cc=levon@movementarian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.