From: "Ayush Singh" <ayushdevel1325@gmail.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>,
"Gaibusab, Jabeena B" <jabeena.b.gaibusab@intel.com>,
"Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Capturing Stdio of an image loaded using EFI_BOOT_SERVICES.LoadImage()
Date: Wed, 20 Jul 2022 01:17:19 +0530 [thread overview]
Message-ID: <8f1daa8e-192c-4afd-8350-cebf41794936@gmail.com> (raw)
Hello everyone. So while trying to make Rust `remote-test-server`, I
found out that it also needs to be able to launch other UEFI
applications (which will be the tests themselves). The Stdout and Stderr
of these tests is supposed to be captured and sent back to the
`remote-test-client` over TCP. I can now launch the `remote-test-server`
under UEFI and get it to connect to the `remote-test-client`, however
the application launch stuff isn't implemented yet.
While I think I can implement the launching application portion using
the `EFI_BOOT_SERVICES.LoadImage()` and `EFI_BOOT_SERVICES.StartImage()`
functions, I do not know how to capture the input/output of these
applications. So is there a way to do it normally? I think UefiShell
must do this, but I am not sure how.
Currently I do have a way to capture output when specifically running
tests (basically writing the output and errors to a file and reading
from it). However, that seems more like a hack, and so I wanted to know
if there was a better way to do this.
Yours Sincerely
Ayush Singh
reply other threads:[~2022-07-19 19:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8f1daa8e-192c-4afd-8350-cebf41794936@gmail.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