From: Peter Maydell <peter.maydell@linaro.org>
To: Yeqi Fu <fufuyqqqqqq@gmail.com>
Cc: alex.bennee@linaro.org, qemu-devel@nongnu.org
Subject: Re: [RFC] Native Library Calls
Date: Tue, 30 May 2023 16:20:16 +0100 [thread overview]
Message-ID: <CAFEAcA_42ZeQRVbLRxZBF17aL4PmLOC32RuEeDc65799W1zxMg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA9gb5rVKEQSZWHj3KZBP1Y27YiObFGdvnGj+JEDV2hHxQ@mail.gmail.com>
On Tue, 30 May 2023 at 15:46, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Tue, 30 May 2023 at 15:26, Yeqi Fu <fufuyqqqqqq@gmail.com> wrote:
> >
> > This patch introduces a set of feature instructions for native calls
> > and provides helpers to translate these instructions to corresponding
> > native functions. A shared library is also implemented, where native
> > functions are rewritten as feature instructions. At runtime, user
> > programs load the shared library, and feature instructions are
> > executed when native functions are called. This patch is applicable
> > to user programs with architectures x86, x86_64, arm, aarch64, mips,
> > and mips64. To build, compile libnative.c into a shared library for
> > the user program's architecture and run the
> > '../configure --enable-user-native-call && make' command.
>
> So it's essentially providing a QEMU-specific ABI that
> (somewhat similarly to semihosting) allows guest programs
> to use particular instructions/instruction patterns to
> say "do a memcpy/memset/memcmp" ?
>
> Is this an ABI that's implemented by anybody else?
Ah, I hadn't realised this was an Outreachy project. I'll
let Alex work with you on iterating on this...
thanks
-- PMM
next prev parent reply other threads:[~2023-05-30 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 14:24 [RFC] Native Library Calls Yeqi Fu
2023-05-30 14:46 ` Peter Maydell
2023-05-30 15:20 ` Peter Maydell [this message]
2023-05-31 2:08 ` LIU Zhiwei
2023-05-31 7:59 ` Alex Bennée
2023-05-31 8:53 ` LIU Zhiwei
2023-05-31 7:24 ` Alex Bennée
2023-05-31 8:02 ` Alex Bennée
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=CAFEAcA_42ZeQRVbLRxZBF17aL4PmLOC32RuEeDc65799W1zxMg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=fufuyqqqqqq@gmail.com \
--cc=qemu-devel@nongnu.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).