From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Sendkey patch
Date: Wed, 03 Sep 2008 19:23:32 +0200 [thread overview]
Message-ID: <1220462612.23879.103.camel@localhost> (raw)
In-Reply-To: <48BEC43A.1000309@nic.fi>
[-- Attachment #1: Type: text/plain, Size: 1566 bytes --]
El mié, 03-09-2008 a las 20:07 +0300, Vesa Jääskeläinen escribió:
> Hi,
>
> How about following (may not be syntaxically correct):
>
> In kernel:
>
> /* Variable holding pointer to preboot hook function. */
> preboot_hook:
> .long 0
>
> ...
> /* Check if there is preboot hook installed. */
> movl preboot_hook, %eax
> testl %eax, %eax
> jne 1f
> call %eax
> 1:
> /* Continue boot. */
>
>
> Then in module code:
>
> void grub_preboot_hook_handler(void)
> {
> /* Process list of registered preboot hooks. */
> }
>
> void grub_preboot_register_hook(...);
> void grub_preboot_unregister_hook(...);
>
> GRUB_MOD_INIT(preboot)
> {
> preboot_hook = grub_preboot_hook_handler;
> }
>
> GRUB_MOD_FINI(preboot)
> {
> preboot_hook = 0;
> }
>
> If preboot.mod gets loaded then it goes and registers preboot handler to
> kernel to do its tricks. Other modules then would use preboot.mod to
> register their own handlers.
This is certainly a good solution, and would probably add less than 10
bytes to the kernel. I only have to add two things:
* This is not as elegant as it could be, as it forces us to expose
preboot_hook in the kernel, thus breaking encapsulation a bit. But it is
a price that I'm more than willing to pay.
* I doubt: is the current DL system in GRUB able to hand dependencies
directly? In other words, is our "insmod" more like modprobe or Linux
insmod? This affects the handling of "insmod drivemap" or "insmod
sendkey" if preboot.mod is not loaded beforehand.
-Habbit
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next prev parent reply other threads:[~2008-09-03 17:20 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 14:23 Sendkey patch phcoder
2008-09-02 14:54 ` Javier Martín
2008-09-02 15:58 ` phcoder
2008-09-02 16:12 ` phcoder
2008-09-02 16:19 ` Vesa Jääskeläinen
2008-09-02 19:01 ` phcoder
2008-09-02 19:29 ` Vesa Jääskeläinen
2008-09-02 16:30 ` Javier Martín
2008-09-02 18:39 ` phcoder
2008-09-02 20:10 ` Javier Martín
2008-09-02 22:22 ` phcoder
2008-09-02 23:38 ` Javier Martín
2008-09-03 0:08 ` phcoder
2008-09-03 0:54 ` Javier Martín
2008-09-03 9:10 ` phcoder
2008-09-03 11:19 ` Javier Martín
2008-09-03 10:37 ` bitbucket
2008-09-03 7:07 ` Felix Zielcke
2008-09-03 17:07 ` Vesa Jääskeläinen
2008-09-03 17:23 ` Javier Martín [this message]
2008-09-03 17:25 ` Felix Zielcke
2008-09-03 17:48 ` phcoder
2008-09-03 17:53 ` Vesa Jääskeläinen
2008-09-03 18:11 ` phcoder
2008-09-04 22:16 ` Javier Martín
2008-09-05 16:13 ` [PATCH] Move kern/loader.c to boot.mod and add preboot_support (was Re: Sendkey patch) phcoder
2008-09-05 16:47 ` Javier Martín
2008-09-08 19:48 ` Vesa Jääskeläinen
2008-09-08 20:11 ` Javier Martín
2008-09-08 20:25 ` Vesa Jääskeläinen
2008-09-08 20:59 ` Javier Martín
2008-12-15 13:54 ` phcoder
2008-12-15 16:41 ` Vesa Jääskeläinen
2008-12-16 14:34 ` phcoder
2009-02-07 19:26 ` Robert Millan
2009-02-07 19:30 ` Robert Millan
2009-02-07 23:02 ` 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=1220462612.23879.103.camel@localhost \
--to=lordhabbit@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.