All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] h8/300 support update
Date: Sun, 26 Oct 2003 23:27:42 +0900	[thread overview]
Message-ID: <m2ad7o8469.wl%ysato@users.sourceforge.jp> (raw)

[-- Attachment #1: Type: text/plain, Size: 89 bytes --]

- add 'sched_clock'
- delete smplock.h

-- 
Yoshinori Sato
<ysato@users.sourceforge.jp>


[-- Attachment #2: linux-2.6.0-test9.diff --]
[-- Type: application/octet-stream, Size: 1719 bytes --]

diff -Nru linux-2.6.0-test9/arch/h8300/kernel/time.c linux-2.6.0-test9-h8300/arch/h8300/kernel/time.c
--- linux-2.6.0-test9/arch/h8300/kernel/time.c	2003-10-17 00:07:45.000000000 +0900
+++ linux-2.6.0-test9-h8300/arch/h8300/kernel/time.c	2003-10-26 21:24:31.000000000 +0900
@@ -143,3 +143,10 @@
 }
 
 EXPORT_SYMBOL(do_settimeofday);
+
+unsigned long long sched_clock(void)
+{
+	return (unsigned long long)jiffies * (1000000000 / HZ);
+
+}
diff -Nru linux-2.6.0-test9/include/asm-h8300/smplock.h linux-2.6.0-test9-h8300/include/asm-h8300/smplock.h
--- linux-2.6.0-test9/include/asm-h8300/smplock.h	2003-08-23 09:00:15.000000000 +0900
+++ linux-2.6.0-test9-h8300/include/asm-h8300/smplock.h	1970-01-01 09:00:00.000000000 +0900
@@ -1,51 +0,0 @@
-/*
- * <asm/smplock.h>
- *
- * Default SMP lock implementation
- */
-#include <linux/interrupt.h>
-#include <linux/spinlock.h>
-
-extern spinlock_t kernel_flag;
-
-#define kernel_locked()		spin_is_locked(&kernel_flag)
-
-/*
- * Release global kernel lock and global interrupt lock
- */
-#define release_kernel_lock(task, cpu) \
-do { \
-	if (task->lock_depth >= 0) \
-		spin_unlock(&kernel_flag); \
-	release_irqlock(cpu); \
-	__sti(); \
-} while (0)
-
-/*
- * Re-acquire the kernel lock
- */
-#define reacquire_kernel_lock(task) \
-do { \
-	if (task->lock_depth >= 0) \
-		spin_lock(&kernel_flag); \
-} while (0)
-
-
-/*
- * Getting the big kernel lock.
- *
- * This cannot happen asynchronously,
- * so we only need to worry about other
- * CPU's.
- */
-extern __inline__ void lock_kernel(void)
-{
-	if (!++current->lock_depth)
-		spin_lock(&kernel_flag);
-}
-
-extern __inline__ void unlock_kernel(void)
-{
-	if (--current->lock_depth < 0)
-		spin_unlock(&kernel_flag);
-}

             reply	other threads:[~2003-10-26 14:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-26 14:27 Yoshinori Sato [this message]
2003-10-26 17:23 ` [PATCH] h8/300 support update Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2004-04-08 15:11 [PATCH] H8/300 " Yoshinori Sato
2003-10-19 15:53 Yoshinori Sato
2003-10-16 16:42 Yoshinori Sato

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=m2ad7o8469.wl%ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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.