Linux PARISC architecture development
 help / color / mirror / Atom feed
From: willy@thepuffingroup.com
To: Grant Grundler <grundler@cup.hp.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] ld: Unsatisfied symbols
Date: Wed, 9 Feb 2000 10:59:06 -0500	[thread overview]
Message-ID: <20000209105906.M7236@thepuffingroup.com> (raw)
In-Reply-To: <200002090605.WAA12699@milano.cup.hp.com>; from Grant Grundler on Tue, Feb 08, 2000 at 10:05:07PM -0800

On Tue, Feb 08, 2000 at 10:05:07PM -0800, Grant Grundler wrote:
> uts_sem (data)
> 	include/linux/utsname.h: extern struct rw_semaphore uts_sem;
> 	kernel/ksyms.c: EXPORT_SYMBOL(uts_sem);          /* UTS semaphore */
> 	kernel/sys.c:  DECLARE_RWSEM(uts_sem);
> 
> 	Seems like another SOM kluge is needed.
> 	Or "DECLARE_RWSEM()" needs to be hacked for SOM.
> 	If someone knows where such "data" kluges are collected,
> 	please either fix it or let me know so we can keep such kluges
> 	all in one place.

nono, this isn't linker magic (for once :-).  It's how to declare a
read-write semaphore (C doesn't have constructors, so you do it manually).
I'll do a silly-C version for now and someone can work on an efficient
assembler version of it later.

> up_read
> up_write
> down_read
> down_write
> 	We seem to need them in asm-parisc/semaphore.h.
> 	I gather this is some form of R/W semaphore.
> 	Anyone who knows more is encouraged to make it happen.

exactly.

thanks for fixing the pci stuff.

      reply	other threads:[~2000-02-09 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-09  6:05 [parisc-linux] ld: Unsatisfied symbols Grant Grundler
2000-02-09 15:59 ` willy [this message]

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=20000209105906.M7236@thepuffingroup.com \
    --to=willy@thepuffingroup.com \
    --cc=grundler@cup.hp.com \
    --cc=parisc-linux@thepuffingroup.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox