From: "Ni, Ruiyu" <ruiyu.ni@Intel.com>
To: Rafael Machado <rafaelrodrigues.machado@gmail.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: UEFI App embedded on another uefi app
Date: Mon, 18 Dec 2017 13:13:10 +0800 [thread overview]
Message-ID: <82e7b859-9184-bb1c-828f-ecde7772231d@Intel.com> (raw)
In-Reply-To: <CACgnt7-a6KOiqU0d-yGYiDKKMH60FT_Vd4Poc0vDvEu-q0dU5Q@mail.gmail.com>
On 12/15/2017 7:45 PM, Rafael Machado wrote:
> Hi Everyone.
>
> I have a limited space problem at a project.
> To solve this we had an idea, but would like to ask to you before expending
> time on trying to do it, due to some tight schedule. (We know that the best
> is to try before ask, but we do not have time for that now. Sorry for that.)
>
> The idea is to create a kind of DecompressorApp.efi, that
> uses EFI_DECOMPRESS_PROTOCOL
>
> During the compilation process of the application the tasks would be:
>
> - Compile App.efi
> - Compress App.efi, generating the App.efi.compressed (using
> tianoCompress.exe)
> - Compile the Decompressor.efi app (with the App.efi.compressed embedded)
> - The idea to do this is to add the compressed app as a Binary at
> the DecompressorApp.efi .inf file using the [Binaries] tag
>
>
> So during the entrypoint of the Decompressor.efi app, the application will
> need to copy the compressed part of the app (App.efi.compressed), to a
> buffer, and after that this buffer will be decompressed using the
> EFI_DECOMPRESS_PROTOCOL. Finally the execution control is passed to the
> App.efi decompressed (not sure how to do that yet).
>
> So the questions we have for know are:
>
> - How to detect the App.efi.compressed insyde the loaded app, so we can
> have an address to decompress
Is your usage case similar to the upx?
If the App.efi is compressed and embedded as binary in the application,
the application itself should know that the binary should be
decompressed and executed.
> - How to pass the application executions control to another app, that is in
> a buffer (not sure if this can be done with the EFI Boot Service
> LoadImage(), since this buffer does not have a valid file device path)
Yes you could use LoadImage(). The API also accepts a PE buffer to load.
Then you could use StartImage() to execute the PE buffer.
Make sure you use the correct entrypoint prototype for the PE buffer.
typedef
EFI_STATUS
(EFIAPI *EFI_IMAGE_ENTRY_POINT)(
IN EFI_HANDLE ImageHandle,
IN EFI_SYSTEM_TABLE *SystemTable
);
>
> Could you help us on understanding if this is possible?
>
> Thanks and Regards
> Rafael R. Machado
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
>
--
Thanks,
Ray
next prev parent reply other threads:[~2017-12-18 5:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 11:45 UEFI App embedded on another uefi app Rafael Machado
2017-12-18 5:13 ` Ni, Ruiyu [this message]
2017-12-20 17:31 ` Rafael Machado
2017-12-21 3:15 ` Ni, Ruiyu
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-list 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=82e7b859-9184-bb1c-828f-ecde7772231d@Intel.com \
--to=devel@edk2.groups.io \
/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