linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_work@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [kbuild-devel] Needed help for UML kbuild.
Date: Thu, 8 Jan 2004 19:07:56 +0100	[thread overview]
Message-ID: <200401081907.56198.blaisorblade_work@yahoo.it> (raw)
In-Reply-To: <200401080019.i080JOtd008375@ccure.user-mode-linux.org>

Alle 01:19, giovedì 8 gennaio 2004, Jeff Dike ha scritto:
> blaisorblade_work@yahoo.it said:
> > some modules(i.e. hostaudio) are built from a "userspace" (needing the
> > special  treatment) file and a "kernel" (to be compiled as usual)
> > file. How will  kbuild link them together?
> >
> > I have three workarounds:

> > - split the module into 2 separate ones, with the kernel one requiring
> > the other. BUT a lot of EXPORT_SYMBOLS should be added (one for each
> > function inside the userspace file at least)

> So, rather than have a module consisting of a userspace chunk and a kernel
> chunk needing to be turned into a single .o, I would rather look at having
> two modules, with the userspace piece plugging into an interface in the
> kernel piece.

> This is what I've envisioned for hostfs for a long time.  You don't need to
> stick host files underneath hostfs files - you can stick other host
> resources under them, and the way to do that is to have multiple hostfs
> userspace modules which plug into an interface in the hostfs kernel piece,
> each of which provides access to a different sort of host resource.

No idea about this hostfs feature - apart the fact it can be something good to 
have (I don't yet see samples but this can be my fault; if you have any 
specific one I'd like it). However, I don't think this is needed for all 
modules. However, this can be delayed to after (or at least, I'd like to 
implement it, after having some other "host resource" to manage). For now, I 
would split the modules into two parts and add needed EXPORT_SYMBOL's. It's 
worth noting that while in 2.4 a module exports all symbols, in 2.6 symbols 
must be exported explicitly.

**So: would you merge this patch?**
If yes, can I be smart about files to just move? (Shipping a list of mv 
commands would be ok?)
Also, the *_user.c (+ the other user-objs) should go under under 
os-Linux/{drivers, kernel, kernel/tt, kernel/skas} ..., right?

The other modules I found in UML 2.6, for which I don't see an obvious reason 
to use a "register_xxx" thing, are:
-hostaudio
-the watchdogs (what are they?)
-hppfs
-cow (but why tristate? Maybe related to the standalone cow device, that I 
have not understood).
-Example IO memory driver.

-- 
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Kernel 2.4.23/2.6.0 on an i686; Linux registered user n. 292729
EOSIGN



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2004-01-08 18:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24 19:19 [uml-devel] Needed help for UML kbuild BlaisorBlade
2003-12-25 10:45 ` [uml-devel] Re: [kbuild-devel] " Christoph Hellwig
2003-12-27 17:35   ` BlaisorBlade
     [not found] ` <200401062038.37402.blaisorblade_work@yahoo.it>
     [not found]   ` <20040106202145.GA11953@mars.ravnborg.org>
2004-01-07 19:12     ` BlaisorBlade
2004-01-08  0:19       ` Jeff Dike
2004-01-08 18:07         ` BlaisorBlade [this message]
2004-01-09 23:46           ` Jeff Dike

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=200401081907.56198.blaisorblade_work@yahoo.it \
    --to=blaisorblade_work@yahoo.it \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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