All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Move BSD and multiboot boot helper out of the kernel to their respective modules
Date: Wed, 04 Feb 2009 13:08:26 +0100	[thread overview]
Message-ID: <4989853A.2020700@gmail.com> (raw)
In-Reply-To: <4981D1D4.2080102@gmail.com>

Hello. On the IRC discussion it was said that removing call to 
grub_dl_unload_all_modules isn't a good thing. I would like to discuss 
this on the list
1) Call to this functon is present only on i386-pc
2) I would suggest an interface for preboot hooks if modules needs to do 
something before booting
3) If it's really needed to unload modules one could add a function 
grub_dl_unload_all_modules_except (grub_dl_t *mod)
Then the module before booting kernel would call this function and after 
it no external calls are allowed.
4) Not being able to add a new kernel type by module alone is IMHO a 
severe limitation to module infrastructure
Thanks
Vladimir 'phcoder' Serbinenko
phcoder wrote:
> Hello, I was looking through the code and have seen that bsd and
> multiboot code uses helpers in the kernel. In this patch I propose to
> move these function to their respective modules
> Thanks
> Vladimir 'phcoder' Serbinenko
> 




  reply	other threads:[~2009-02-04 12:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 15:57 Move BSD and multiboot boot helper out of the kernel to their respective modules phcoder
2009-02-04 12:08 ` phcoder [this message]
2009-02-07 22:20   ` Robert Millan
2009-02-07 23:12     ` phcoder
2009-02-07 22:14 ` Robert Millan
2009-02-07 23:05   ` phcoder

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=4989853A.2020700@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.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.