[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] framework for building modules externally

From: Robert Millan
Subject: Re: [PATCH] framework for building modules externally
Date: Wed, 5 Nov 2008 10:42:40 +0100
User-agent: Mutt/1.5.13 (2006-08-11)

On Wed, Nov 05, 2008 at 07:57:38AM +0100, Christian Franke wrote:
> Alternative: Export a symbol describing the ABI version in kernel 
> ("grub_abi_3_14").

That requires more bytes than a 32-bit integer.

> Access this symbol in each module (this can be hidden 

And this adds code in every module, but for non-external modules we already
have reassurance that their abi is consistent (users should never bypass
grub-install;  if they do, it's likely going to break for them anyway).

I understand there's a minor benefit for programmers of external modules,
but both things are at the expense of extra size to kernel and core.img
modules.  External modules will only provide non-essential functionality, so
it's not a problem they have to check the ABI IMHO.

Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]