All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Zide" <zide.chen@intel.com>
To: Daniel Kiper <dkiper@net-space.pl>
Cc: "grub-devel@gnu.org" <grub-devel@gnu.org>
Subject: RE: [PATCH V4] multiboot2: Implement quirk-modules-after-kernel
Date: Thu, 16 Apr 2020 21:18:55 +0000	[thread overview]
Message-ID: <636297D5EBADD745BF4BDD83AA58243931FE1FED@ORSMSX102.amr.corp.intel.com> (raw)
In-Reply-To: <636297D5EBADD745BF4BDD83AA58243931FE1CF8@ORSMSX102.amr.corp.intel.com>

Hi Daniel,

> -----Original Message-----
> From: Chen, Zide
> Sent: Thursday, April 16, 2020 10:41 AM
> To: 'Daniel Kiper' <dkiper@net-space.pl>
> Cc: grub-devel@gnu.org
> Subject: RE: [PATCH V4] multiboot2: Implement quirk-modules-after-kernel
> 
> > >             +------------------+
> > > u16     | type = 22       |
> > > u16     | flags               |
> > > u32     | size = 20        |
> > > u32     | min_addr      |
> >
> > s/u32/u64/
> 
> Currently modules are loaded at 32bit address only. But yes, I agree that 'u64' would
> make it more flexible.
> 
> > > u32     | max_addr     |
> >
> > s/u32/u64/
> >
> > > u32     | preference   |
> >
> > Please put preference immediately behind the size.
> Sure, will do.

Just noticed that if we change min/max_addr to u64, and move preference right after size,
it could have struct packing issue. For example:

struct multiboot_header_tag_module_relocatable
{
  multiboot_uint16_t type;
  multiboot_uint16_t flags;
  multiboot_uint32_t size;
  multiboot_uint32_t preference; 
  multiboot_uint64_t min_addr;  // address is compiler dependent
  multiboot_uint64_t max_addr;
};

So I still propose to put preference after max_addr. I wrote the code based on this proposed new tag,
and will send out the doc change and implementation for review shortly.

-Zide


      reply	other threads:[~2020-04-16 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 21:08 [PATCH V4] multiboot2: Implement quirk-modules-after-kernel Zide Chen
2020-04-14 20:09 ` Daniel Kiper
2020-04-14 21:39   ` Chen, Zide
2020-04-16 13:28     ` Daniel Kiper
2020-04-16 17:42       ` Chen, Zide
2020-04-16 21:18         ` Chen, Zide [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=636297D5EBADD745BF4BDD83AA58243931FE1FED@ORSMSX102.amr.corp.intel.com \
    --to=zide.chen@intel.com \
    --cc=dkiper@net-space.pl \
    --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.