From: lasse.collin@tukaani.org (Lasse Collin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] lib/decompress_unxz.c: removing all memory helper functions
Date: Fri, 25 May 2012 11:34:32 +0300 [thread overview]
Message-ID: <20120525113432.3beea6ed@tukaani.org> (raw)
In-Reply-To: <1337875436-27640-1-git-send-email-tmac@hp.com>
On 2012-05-24 T Makphaibulchoke wrote:
> The patch cleans up the file lib/decompress_unxz.c by removing all
> memory helper functions, e.g., memmove. By doing so, any
> architecture's preboot environment supporting the XZ decompression
> needs to define its own copy of any of the missing memory helper
> functions.
Is it best to copy these functions to each arch, or would it be better
to have a shared file from which these functions could be pulled for
multiple archs? I wasn't sure when I wrote decompress_unxz.c, which is
why I put the extra functions there as a temporary solution.
> Adding both the missing memmove and memcmp functions, required by the
> XZ decompressor, to the sh preboot environment.
>
> Adding the missing memmove function, required by XZ decompressor, to
> the x86 preboot environment.
These already have memcpy. It can save a few bytes if one reused
memmove as memcpy when using XZ compression. I got a difference of 48
bytes on x86_64.
Adding memmove to string.c on x86 means that memmove is included in the
kernel image even when memmove isn't needed. With gzip compression I
got 128 bytes bigger image on x86_64 after adding the unneeded memmove
to string.c.
I don't know if those size increases matter in practice.
> + * To support XZ-decompressed file in preboot environment, the
s/XZ-decompressed/XZ-compressed/ :-)
--
Lasse Collin | IRC: Larhzu @ IRCnet & Freenode
next prev parent reply other threads:[~2012-05-25 8:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 16:03 [PATCH] lib/decompress_unxz.c: removing all memory helper functions T Makphaibulchoke
2012-05-24 17:26 ` Joe Perches
2012-05-24 17:29 ` H. Peter Anvin
2012-05-24 17:40 ` Joe Perches
2012-05-24 17:41 ` H. Peter Anvin
2012-05-24 17:50 ` Joe Perches
2012-05-24 17:56 ` H. Peter Anvin
2012-05-25 8:34 ` Lasse Collin [this message]
2012-05-25 16:31 ` Thavatchai Makphaibulcboke
2012-05-25 17:05 ` Thavatchai Makphaibulcboke
2012-05-25 17:13 ` H. Peter Anvin
2012-05-25 19:35 ` Lasse Collin
2012-05-28 7:03 ` Jean-Christophe PLAGNIOL-VILLARD
2012-06-01 2:48 ` Thavatchai Makphaibulcboke
2012-06-01 2:54 ` Joe Perches
2012-06-01 3:38 ` H. Peter Anvin
2012-06-01 18:37 ` Thavatchai Makphaibulcboke
2012-06-01 18:46 ` H. Peter Anvin
2012-06-01 18:58 ` Thavatchai Makphaibulcboke
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=20120525113432.3beea6ed@tukaani.org \
--to=lasse.collin@tukaani.org \
--cc=linux-arm-kernel@lists.infradead.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).