All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Jan Beulich <JBeulich@novell.com>, Michal Marek <mmarek@suse.cz>,
	Ingo Molnar <mingo@elte.hu>,
	tony.luck@intel.com, Thomas Gleixner <tglx@linutronix.de>,
	Rusty Russell <rusty@rustcorp.com.au>,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-modules@vger.kernel.org
Subject: Re: [PATCH] reduce export symbol CRC table size on 64-bit	 archs
Date: Tue, 14 Jul 2009 12:43:31 -0400	[thread overview]
Message-ID: <4A5CB5B3.2060002@zytor.com> (raw)
In-Reply-To: <1247567372.31188.229.camel@perihelion.bos.jonmasters.org>

Jon Masters wrote:
> On Mon, 2009-07-13 at 09:44 +0100, Jan Beulich wrote:
>>>>> Michal Marek <mmarek@suse.cz> 13.07.09 10:11 >>>
>>> Jan Beulich napsal(a):
>>>> Actually I meanwhile think that module-init-tools can easily detect the changed
>>>> layout without any further kernel side adjustments: Since it is known that a
>>>> CRC always is a 32-bit value, simply checking whether the so-far-used 64-bit
>>>> value has more than 32 significant bits should suffice: If so, the new layout
>>>> is being used (with the symbol name starting at offset 4), else the old one is
>>>> in effect (name at offset 8). This ought to be a pretty trivial change to that
>>>> code.
>>> But old module-init-tools will continue reading garbage in this case.
> 
> Most of the distros can fix that with a dependency on the kernel package
> in the absolute worst case, not that I love that idea, but it happens. I
> assume for now we are going with detecting the two possibilities because
> it doesn't really hurt in any case to have this support.
> 

It would seem to me that reading garbage is worse than reading nothing, 
unless I'm missing something fundamental.

	-hpa

      parent reply	other threads:[~2009-07-14 16:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 11:51 [PATCH] reduce export symbol CRC table size on 64-bit archs Jan Beulich
2009-06-30 11:51 ` Jan Beulich
2009-06-30 22:09 ` Ingo Molnar
2009-07-01  5:00 ` Rusty Russell
2009-07-01  7:00   ` Jan Beulich
2009-07-01  7:00     ` Jan Beulich
     [not found] ` <4A4A18780200007800008345-Qfbpwmsw6RoS3W1tAdPHOtBPR1lH4CV8@public.gmane.org>
2009-07-03 20:16   ` Michal Marek
2009-07-03 20:16     ` Michal Marek
2009-07-06  7:42     ` Jan Beulich
2009-07-06  7:42       ` Jan Beulich
     [not found]       ` <4A51C71B0200007800008EE2-Qfbpwmsw6RoS3W1tAdPHOtBPR1lH4CV8@public.gmane.org>
2009-07-09 11:14         ` Rusty Russell
2009-07-09 11:14           ` Rusty Russell
2009-07-10  7:23           ` Jan Beulich
2009-07-10  7:23             ` Jan Beulich
     [not found]             ` <4A57089B0200007800009C0E-Qfbpwmsw6RoS3W1tAdPHOtBPR1lH4CV8@public.gmane.org>
2009-07-10 14:36               ` H. Peter Anvin
2009-07-10 14:36                 ` H. Peter Anvin
2009-07-10 15:50               ` Jon Masters
2009-07-10 15:50                 ` Jon Masters
2009-07-13  8:11               ` Michal Marek
2009-07-13  8:11                 ` Michal Marek
2009-07-13  8:44                 ` Jan Beulich
2009-07-13  8:44                   ` Jan Beulich
     [not found]                   ` <4A5B101E020000780000A284-Qfbpwmsw6RoS3W1tAdPHOtBPR1lH4CV8@public.gmane.org>
2009-07-14 10:29                     ` Jon Masters
2009-07-14 10:29                       ` Jon Masters
     [not found]                       ` <1247567372.31188.229.camel-gHXTUq7nJ1kAgR79ElizB2+biTydnCM9ILAQCsJbaHk@public.gmane.org>
2009-07-14 10:44                         ` Marco d'Itri
2009-07-14 10:44                           ` Marco d'Itri
2009-07-14 16:43                       ` H. Peter Anvin [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=4A5CB5B3.2060002@zytor.com \
    --to=hpa@zytor.com \
    --cc=JBeulich@novell.com \
    --cc=jonathan@jonmasters.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mmarek@suse.cz \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    /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.