From: Andrea Bolognani <abologna@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Andrew Jones <drjones@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 2/2] mach-virt: Provide sample configuration files
Date: Thu, 09 Feb 2017 11:51:13 +0100 [thread overview]
Message-ID: <1486637473.3641.36.camel@redhat.com> (raw)
In-Reply-To: <CAFEAcA8bRHuF_to0+whEhNF5oXp5_O63H8EV2JTXBngffufz9Q@mail.gmail.com>
On Thu, 2017-02-09 at 09:57 +0000, Peter Maydell wrote:
> > I see Peter and you are discussing what to document here. IMO,
> > we should simply state -nodefaults provides us a base mach-virt
> > board with no peripherals.
>
> The thing about saying that is that it's not actually
> correct -- you get the UART, etc etc peripherals whether
> you say -nodefaults or not. I agree that listing them
> in multiple places isn't a good idea though. Maybe
> there's some wording that will work here.
Agreed, we just have to find the right wording. Would
something like
Using -nodefaults is required to have full control over
the virtual hardware: when it's specified, QEMU will
only automatically add a small selection of core PCI
devices, and leave the user in charge of adding more as
they see fit. More specifically, the PCI devices that
will always be present are:
00:00.0 Host bridge
This configuration file adds a number of other...
work for you? Please keep in mind that I want to be able
to use the very same paragraph both for q35 and mach-virt.
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2017-02-09 10:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 17:35 [Qemu-devel] [PATCH v5 0/2] docs: Improve sample configuration files Andrea Bolognani
2017-02-08 17:35 ` [Qemu-devel] [PATCH v5 1/2] q35: " Andrea Bolognani
2017-02-08 17:35 ` [Qemu-devel] [PATCH v5 2/2] mach-virt: Provide " Andrea Bolognani
2017-02-08 18:11 ` Laszlo Ersek
2017-02-08 18:49 ` Andrea Bolognani
2017-02-08 19:34 ` Laszlo Ersek
2017-02-08 19:47 ` Andrea Bolognani
2017-02-09 9:49 ` Andrew Jones
2017-02-09 10:52 ` Andrea Bolognani
2017-02-08 18:32 ` Peter Maydell
2017-02-08 19:23 ` Laszlo Ersek
2017-02-08 19:40 ` Peter Maydell
2017-02-08 19:28 ` Andrea Bolognani
2017-02-08 19:36 ` Peter Maydell
2017-02-08 19:49 ` Laszlo Ersek
2017-02-09 13:53 ` Andrea Bolognani
2017-02-09 14:14 ` Andrew Jones
2017-02-08 19:36 ` Laszlo Ersek
2017-02-09 9:42 ` Andrew Jones
2017-02-09 9:57 ` Peter Maydell
2017-02-09 10:51 ` Andrea Bolognani [this message]
2017-02-09 12:28 ` Andrew Jones
2017-02-09 13:27 ` Andrea Bolognani
2017-02-09 14:08 ` Andrew Jones
2017-02-09 14:56 ` Andrea Bolognani
2017-02-09 15:26 ` Gerd Hoffmann
2017-02-09 15:10 ` Andrea Bolognani
2017-02-09 15:35 ` Andrew Jones
2017-02-09 16:11 ` Andrea Bolognani
2017-02-09 16:36 ` Andrew Jones
2017-02-09 17:06 ` Andrea Bolognani
2017-02-09 18:05 ` Andrew Jones
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=1486637473.3641.36.camel@redhat.com \
--to=abologna@redhat.com \
--cc=drjones@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel@redhat.com \
--cc=peter.maydell@linaro.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 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.