All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: vincent Dupaquis <v.dupaquis@trusted-objects.com>
Cc: qemu-arm@nongnu.org
Subject: Re: Role of qemu-arm
Date: Mon, 22 Jun 2020 09:57:31 +0100	[thread overview]
Message-ID: <87o8pba35w.fsf@linaro.org> (raw)
In-Reply-To: <e0fc64ab-b36e-99d1-90ea-8877c00f8c0f@trusted-objects.com>


vincent Dupaquis <v.dupaquis@trusted-objects.com> writes:

> Hello,
>
>     I am using qemu for doing simulations of code, and currently find
> qemu-system-arm convienient.
>
>     But, I cannot understand how to use qemu-arm. In fact, what I am
> searching for is a way of simulating only the ARM core, not any
> peripherals.

There are two modes:

  - system emulation (CPU + board and peripherals)
  - linux-user (CPU but with a Linux syscall interface)

> I can work with qemu-system-arm, and could not find a way
> to use qemu-arm.

If you are installing via your distros package manager you probably want
a package called qemu-user. You can build the only the user-mode
packages by issuing --disable-system to the configure script.

The closest thing to being a "pure" just the CPU is probably a
standalone usermode binary that uses semihosting calls rather than a
libc/syscall interface.

>
>     Would anyone have any pointers to a documentation or a tutorial
> using this tool ?
>
>     Best regards,
>
>         Vincent.


-- 
Alex Bennée

  reply	other threads:[~2020-06-22  8:57 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 17:03 [PATCH] target/arm: Remove unnecessary gen_io_end() calls Peter Maydell
2020-06-19 17:03 ` Peter Maydell
2020-06-19 17:15 ` Alex Bennée
2020-06-19 17:15   ` Alex Bennée
2020-06-19 17:24 ` no-reply
2020-06-19 17:24   ` no-reply
2020-06-20  0:23 ` Richard Henderson
2020-06-20  0:23   ` Richard Henderson
2020-06-22  7:17 ` Pavel Dovgalyuk
2020-06-22  7:17   ` Pavel Dovgalyuk
2020-06-22  7:30   ` Role of qemu-arm vincent Dupaquis
2020-06-22  8:57     ` Alex Bennée [this message]
2020-06-22  9:29       ` Philippe Mathieu-Daudé
2020-06-22 11:27         ` vincent Dupaquis
2020-06-22 12:16           ` Peter Maydell
2020-06-22 13:03             ` vincent Dupaquis
2020-06-22 13:43               ` Peter Maydell
2020-06-24  8:45                 ` vincent Dupaquis
2020-06-24 10:14                   ` Alex Bennée
2020-06-25  6:52                     ` vincent Dupaquis
2020-06-25  8:46                       ` Peter Maydell
2020-06-25  9:23                       ` 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=87o8pba35w.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=v.dupaquis@trusted-objects.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.