qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH for-5.1 4/4] docs/system: Document the arm virt board
Date: Tue, 14 Jul 2020 16:00:22 +0100	[thread overview]
Message-ID: <CAFEAcA-qkx_AVrYAsc0K=DYBnX8VGBftihuXDbJN-3qsc6OzEQ@mail.gmail.com> (raw)
In-Reply-To: <871rleywhn.fsf@linaro.org>

On Tue, 14 Jul 2020 at 15:58, Alex Bennée <alex.bennee@linaro.org> wrote:
>
>
> Peter Maydell <peter.maydell@linaro.org> writes:
>
> > Document the arm 'virt' board, which has been undocumented
> > for far too long given that it is the main recommended board
> > type for arm guests.
> >
> > Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> > ---
> >  docs/system/arm/virt.rst   | 157 +++++++++++++++++++++++++++++++++++++
> >  docs/system/target-arm.rst |   1 +
> >  MAINTAINERS                |   1 +
> >  3 files changed, 159 insertions(+)
> >  create mode 100644 docs/system/arm/virt.rst
> >
> > diff --git a/docs/system/arm/virt.rst b/docs/system/arm/virt.rst
> > new file mode 100644
> > index 00000000000..6a7823d8bca
> > --- /dev/null
> > +++ b/docs/system/arm/virt.rst
> > @@ -0,0 +1,157 @@
> > +'virt' generic virtual platform (``virt``)
> > +==========================================
> > +
> > +The `virt` board is a platform which does not correspond to any
> > +real hardware; it is designed for use in virtual machines.
> > +It is the recommended board type if you simply want to run
> > +a guest such as Linux and do not care about reproducing the
> > +idiosyncrasies and limitations of a particular bit of real-world
> > +hardware.
> > +
> > +This is a "versioned" board model, so as well as the ``virt`` machine
> > +type itself (which may have improvements, bugfixes and other minor
> > +changes between QEMU versions) a version is provided that guarantees
> > +to have the same behaviour as that of previous QEMU releases, so
> > +that VM migration will work between QEMU versions. For instance the
> > +``virt-5.0`` machine type will behave like the ``virt`` machine from
> > +the QEMU 5.0 release, and migration should work between ``virt-5.0``
> > +of the 5.0 release and ``virt-5.0`` of the 5.1 release. Migration
> > +is not guaranteed to work between different QEMU releases for
> > +the non-versioned ``virt`` machine type.
> > +
> > +Supported devices
> > +"""""""""""""""""
> > +
> > +The virt board supports:
> > +
> > +- Flash memory
> > +- One PL011 UART
> > +- An RTC
> > +- The fw_cfg device that allows a guest to obtain data from QEMU
> > +- A PL061 GPIO controller
> > +- An optional SMMUv3 IOMMU
> > +- hotpluggable DIMMs
> > +- hotpluggable NVDIMs
> > +- 32 virtio-mmio transport devices
>
> We seem to miss out we also support the virtio-pci transports here.

That's just a special case of "PCI", which I did indeed somehow forget.

 + PCI devices

thanks
-- PMM


  reply	other threads:[~2020-07-14 15:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 17:57 [PATCH for-5.1 0/4] Document virt and a few other Arm boards Peter Maydell
2020-07-13 17:57 ` [PATCH for-5.1 1/4] docs/system: Briefly document canon-a1100 board Peter Maydell
2020-07-14 12:51   ` Philippe Mathieu-Daudé
2020-07-14 13:14   ` Alex Bennée
2020-07-13 17:57 ` [PATCH for-5.1 2/4] docs/system: Briefly document collie board Peter Maydell
2020-07-14 12:50   ` Philippe Mathieu-Daudé
2020-07-14 13:16   ` Alex Bennée
2020-07-13 17:57 ` [PATCH for-5.1 3/4] docs/system: Briefly document gumstix boards Peter Maydell
2020-07-13 18:49   ` Philippe Mathieu-Daudé
2020-07-14 14:47   ` Alex Bennée
2020-07-13 17:57 ` [PATCH for-5.1 4/4] docs/system: Document the arm virt board Peter Maydell
2020-07-14 14:58   ` Alex Bennée
2020-07-14 15:00     ` Peter Maydell [this message]
2020-07-15  9:47   ` Auger Eric
2020-07-20  9:38 ` [PATCH for-5.1 0/4] Document virt and a few other Arm boards Peter Maydell

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-qkx_AVrYAsc0K=DYBnX8VGBftihuXDbJN-3qsc6OzEQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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).