From: Auger Eric <eric.auger@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: eric.auger.pro@gmail.com,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
prem.mallappa@gmail.com, Andrew Jones <drjones@redhat.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
Radha.Chintakuntla@cavium.com, Sunil.Goutham@cavium.com,
Radha Mohan <mohun106@gmail.com>,
Trey Cain <tcain@qti.qualcomm.com>
Subject: Re: [Qemu-devel] [RFC v4 4/5] hw/arm/virt: Add 2.10 machine type
Date: Wed, 31 May 2017 09:15:12 +0200 [thread overview]
Message-ID: <2c81529b-6916-8dd6-eee9-45e5768d82ca@redhat.com> (raw)
In-Reply-To: <CAFEAcA-GCKfxEpy9p=k7NzoY2zez-KVXNMuAx-ruW5t27ZMgQQ@mail.gmail.com>
Hi Peter,
On 30/05/2017 18:04, Peter Maydell wrote:
> On 13 May 2017 at 18:43, Eric Auger <eric.auger@redhat.com> wrote:
>> The new machine type allows smmuv3 instantiation. A new option
>> is introduced to turn the feature on/off (off by default).
>
> Should we go for default-on, or would that break guests?
> For other things added to the virt board I think the
> approach we've taken has been:
> * if this is just an extra device, simply provide it in the
> new virt-n.nn machine by default
> * if this is something that changes how the machine behaves
> even for code that doesn't care about that feature (eg
> EL2, EL3, since they change what mode you start in on boot)
> then default it to off
> * if the feature only works with TCG and not KVM then
> maybe default it to off
OK thanks for the guidelines. I put it off by default since it can
largely degrade the performance in some use cases. Also instantiating
the smmu can also induce some option changes at other levels: for
instance virtio-pci devices may be used along with iommu_platform option
for the guest to use dma ops.
Thanks
Eric
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2017-05-31 7:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 17:43 [Qemu-devel] [RFC v4 0/5] ARM SMMUv3 Emulation Support Eric Auger
2017-05-13 17:43 ` [Qemu-devel] [RFC v4 1/5] hw/arm/smmu-common: smmu base class Eric Auger
2017-05-30 15:56 ` Peter Maydell
2017-05-31 7:04 ` Auger Eric
2017-05-13 17:43 ` [Qemu-devel] [RFC v4 2/5] hw/arm/smmuv3: smmuv3 emulation model Eric Auger
2017-05-30 16:01 ` Peter Maydell
2017-05-31 7:07 ` Auger Eric
2017-05-13 17:43 ` [Qemu-devel] [RFC v4 3/5] hw/arm/virt: Add SMMUv3 to the virt board Eric Auger
2017-05-13 17:43 ` [Qemu-devel] [RFC v4 4/5] hw/arm/virt: Add 2.10 machine type Eric Auger
2017-05-30 16:04 ` Peter Maydell
2017-05-31 7:15 ` Auger Eric [this message]
2017-05-13 17:43 ` [Qemu-devel] [RFC v4 5/5] hw/arm/virt-acpi-build: add smmuv3 node in IORT table Eric Auger
2017-05-30 16:09 ` [Qemu-devel] [RFC v4 0/5] ARM SMMUv3 Emulation Support Peter Maydell
2017-05-31 7:21 ` Auger Eric
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=2c81529b-6916-8dd6-eee9-45e5768d82ca@redhat.com \
--to=eric.auger@redhat.com \
--cc=Radha.Chintakuntla@cavium.com \
--cc=Sunil.Goutham@cavium.com \
--cc=christoffer.dall@linaro.org \
--cc=drjones@redhat.com \
--cc=edgar.iglesias@gmail.com \
--cc=eric.auger.pro@gmail.com \
--cc=mohun106@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=prem.mallappa@gmail.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=tcain@qti.qualcomm.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 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).