From: "Michael S. Tsirkin" <mst@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [SeaBIOS] [PATCH v2 1/5] linker: utility to patch in-memory ROM files
Date: Mon, 15 Jul 2013 11:01:02 +0300 [thread overview]
Message-ID: <20130715080102.GA31638@redhat.com> (raw)
In-Reply-To: <20130714182452.GB7607@morn.localdomain>
On Sun, Jul 14, 2013 at 02:24:52PM -0400, Kevin O'Connor wrote:
> On Sun, Jul 07, 2013 at 06:42:35PM +0300, Michael S. Tsirkin wrote:
> > Add ability for a ROM file to point to
> > it's image in memory. When file is in memory,
> > add utility that can patch it, storing
> > pointers to one file within another file.
>
> Thanks. See my comments below.
>
> [...]
> > --- /dev/null
> > +++ b/src/linker.c
> [...]
> > +void linker_loader_execute(const char *name)
> > +{
> > + struct linker_loader_entry_s *entry;
> > + int size, offset = 0;
> > + void *data = romfile_loadfile(name, &size);
> > + if (!data)
> > + return;
> > +
> > + for (offset = 0; offset < size; offset += sizeof *entry) {
>
> For consistent style, please treat sizeof like a function (ie,
> sizeof(*entry) ).
>
> > + entry = data + offset;
> > + /* Check that entry fits in buffer. */
> > + if (offset + sizeof *entry > size) {
> > + warn_internalerror();
> > + break;
> > + }
> > + switch (le32_to_cpu(entry->command)) {
> > + case LINKER_LOADER_COMMAND_ALLOCATE:
> > + linker_loader_allocate(entry);
>
> SeaBIOS uses 4 spaces for indentation, and no tabs.
>
> [...]
> > --- a/src/util.h
> > +++ b/src/util.h
> > @@ -436,6 +436,7 @@ struct romfile_s {
> > char name[128];
> > u32 size;
> > int (*copy)(struct romfile_s *file, void *dest, u32 maxlen);
> > + void *data;
> > };
>
> I'd prefer to see this tracked within the "linker" code and not in the
> generic romfile struct.
A way to associate a romfile instance with a value seems generally
useful, no? Still, that's not too hard - it would only mean an extra
linked list of
struct linker {
char name[56]
void *data;
struct hlist_node node;
}
is this preferable?
> Also, is there another name besides "linker" that could be used?
> SeaBIOS has code to self-relocate and fixup code relocations. I think
> having code in the repo called "linker" could cause confusion.
>
> -Kevin
romfile_loader?
--
MST
next prev parent reply other threads:[~2013-07-15 7:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 15:42 [Qemu-devel] [PATCH v2 0/5] seabios: load acpi tables from qemu Michael S. Tsirkin
2013-07-07 15:42 ` [Qemu-devel] [PATCH v2 1/5] linker: utility to patch in-memory ROM files Michael S. Tsirkin
2013-07-14 18:24 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2013-07-15 8:01 ` Michael S. Tsirkin [this message]
2013-07-25 12:55 ` Michael S. Tsirkin
2013-07-26 0:06 ` Kevin O'Connor
2013-09-22 10:49 ` Michael S. Tsirkin
2013-09-22 11:18 ` Michael S. Tsirkin
2013-09-22 13:44 ` Michael S. Tsirkin
2013-07-07 15:42 ` [Qemu-devel] [PATCH v2 2/5] pmm: add a way to test whether memory is in FSEG Michael S. Tsirkin
2013-07-07 15:42 ` [Qemu-devel] [PATCH v2 3/5] acpi: pack rsdp Michael S. Tsirkin
2013-07-07 15:42 ` [Qemu-devel] [PATCH v2 4/5] acpi: load and link tables from /etc/acpi/ Michael S. Tsirkin
2013-07-14 18:27 ` [Qemu-devel] [SeaBIOS] " Kevin O'Connor
2013-07-15 8:11 ` Michael S. Tsirkin
2013-07-15 9:58 ` Michael S. Tsirkin
2013-07-07 15:42 ` [Qemu-devel] [PATCH v2 5/5] acpi: add an option to disable builtin tables Michael S. Tsirkin
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=20130715080102.GA31638@redhat.com \
--to=mst@redhat.com \
--cc=kevin@koconnor.net \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).