From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Warnings in kern/dl.c
Date: Fri, 18 Jul 2008 11:20:17 -0400 [thread overview]
Message-ID: <1216394417.18320.4.camel@dv> (raw)
In-Reply-To: <18089483.3400681216390485746.JavaMail.chaac@nic.fi>
On Fri, 2008-07-18 at 17:14 +0300, chaac@nic.fi wrote:
> I think that using grub-emu might be a good idea for testing. I think
> there should be grub-emu architecture that could be compiled and in
> example there would be grub-emu specific disk layer, input layer and
> so on. So we could use grub-emu almost as same way we can do in real
> runtime environment. I know Marco will be using grub-emu like this on
> his GSoC project and I think it is a good thing too. But it needs some
> work of course.
Yes, that would be a different grub-emu. Maybe it will be compiled with
the target flags. Maybe it will need to be disabled if cross-compiling.
> We could do some special testing framework using this method. Eg. we
> could drive user input from special user input module that can be
> controlled from outside.
I'd rather use qemu for testing, as it emulated the whole system.
Anyway, we'll see.
> So please, do not at least remove support for using 64bit modules on
> 64bit systems :) (or otherwise make it harder to be supported later
> on)
OK, let's keep it. I just don't want to force loading foreign
architecture modules into the executable memory.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-07-18 15:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 14:14 Warnings in kern/dl.c chaac
2008-07-18 15:20 ` Pavel Roskin [this message]
2008-07-18 15:35 ` Bean
2008-07-18 16:12 ` Pavel Roskin
-- strict thread matches above, loose matches on Subject: below --
2008-07-18 5:38 Pavel Roskin
2008-07-18 6:18 ` Bean
2008-07-18 6:22 ` Bean
2008-07-18 9:36 ` Bean
2008-07-18 13:21 ` Bean
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=1216394417.18320.4.camel@dv \
--to=proski@gnu.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.