public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dwmw2@infradead.org (David Woodhouse),
	vojtech@suse.cz (Vojtech Pavlik), alan@redhat.com (Alan Cox),
	torvalds@transmeta.com (Linus Torvalds),
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make agpsupport work with modversions
Date: Sat, 28 Oct 2000 21:08:30 +1100	[thread overview]
Message-ID: <7404.972727710@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sat, 28 Oct 2000 11:02:04 BST." <E13pSoP-0005Et-00@the-village.bc.nu>

On Sat, 28 Oct 2000 11:02:04 +0100 (BST), 
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> of get_module_symbol this weekend.  The inter-object registration code
>> will allow two objects to pass data to each other, it will not matter
>> whether the objects are both modules, one module and one built in (in
>> either order) or both built in.  When modules are involved there will
>> be full module locking.
>
>Dont forget that one of the objects may not even be present, or may be
>loaded later.

How could I forget it?  You have defined the heart of the problem,
either object might be built into the kernel, might be a module or
might not even be there, in any case the load order is undefined.  That
is why existing code is kludging things by using get_module_symbol().
inter_module_register, unregister, get, put will solve the inter object
problem but using a clean interface that works with symbol versions.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-10-28 10:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20001019102722.B9057@suse.cz>
2000-10-26 22:21 ` [PATCH] Make agpsupport work with modversions Alan Cox
2000-10-26 22:55   ` Vojtech Pavlik
2000-10-27 13:25   ` David Woodhouse
2000-10-28  2:18     ` Keith Owens
2000-10-28  6:58       ` Andrew Morton
2000-10-28  9:40       ` Alan Cox
2000-10-28  9:55         ` Keith Owens
2000-10-28 10:07           ` Alan Cox
2000-10-28 10:02       ` Alan Cox
2000-10-28 10:08         ` Keith Owens [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=7404.972727710@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=alan@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=vojtech@suse.cz \
    /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