From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: CPUID module
Date: Fri, 18 May 2007 20:35:35 +0200 [thread overview]
Message-ID: <200705182035.35955.okuji@enbug.org> (raw)
In-Reply-To: <20070518155009.GC16167@aragorn>
On Friday 18 May 2007 17:50, Robert Millan wrote:
> Here's a patch to implement cpuid.mod.
Great.
> This module checks for CPU features
> (currently only the long_mode flag, but more could be added if needed)
> using cpuid. The idea behind this is that grub.cfg scripts can use it to
> decide wether a 64-bit or 32-bit Linux image should be boot (e.g. like
> Debian multiarch CDs do). I haven't investigated what the syntax for that
> hack would be, although I assume it's possible.
Personally, I think it would be cleaner to just return true or false (like
test) rather than setting an environment variable. For instance:
if cpuid --long-mode; then ...; else ...; fi
> Cpuid detection code has been borrowed from gcc and is FSF-copyrighted.
>
> I'm not sure where would the file go. I noticed that other utility modules
> (e.g. hello/hello.c) add themselves in the top dir, so I suppose
> i386/cpuid.c would be ok?
>
> Or perhaps we could have an "util" dir for modules?
No. Please use commands/i386/. "util" is strictly for utilities for an host
operating system.
Okuji
next prev parent reply other threads:[~2007-05-18 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 15:50 CPUID module Robert Millan
2007-05-18 18:35 ` Yoshinori K. Okuji [this message]
2007-05-19 10:55 ` Robert Millan
2007-05-19 17:32 ` Yoshinori K. Okuji
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=200705182035.35955.okuji@enbug.org \
--to=okuji@enbug.org \
--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.