From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Laszlo Ersek <lersek@redhat.com>,
Shannon Zhao <shannon.zhao@linaro.org>,
qemu-arm <qemu-arm@nongnu.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Alexander Graf <agraf@suse.de>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-arm] [PATCH] target-arm: Declare virtio-mmio as dma-coherent in dt
Date: Thu, 9 Feb 2017 10:35:28 +0000 [thread overview]
Message-ID: <CAKv+Gu_HJ-MNZ+GPsroodWGNVm4z++CSWLUkPR6tro8jUh2zzA@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA8rjjzgvN-RuNPVHM53R9V9xry1Uj_ArmF1va-Y920eBQ@mail.gmail.com>
(+Leif, Graeme)
On 8 February 2017 at 18:23, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 8 February 2017 at 16:27, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>> The _CCA property is mandatory on arm64, and there is no default.
>
> Is there a tool that can check this kind of requirement
> and complain about issues in the ACPI tables (and
> ditto, device tree)? It's really easy to produce a
> dt or ACPI table that works with current kernels and
> then turns out to have a problem six or twelve
> months down the line :-(
>
Perhaps Graeme or Leif could shed some light on this? I know this is
on our roadmap, but I am not up to date with the latest status.
next prev parent reply other threads:[~2017-02-09 10:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 13:31 [Qemu-devel] [PATCH] target-arm: Declare virtio-mmio as dma-coherent in dt Alexander Graf
2017-02-08 15:29 ` Laszlo Ersek
2017-02-08 16:12 ` Alexander Graf
2017-02-08 16:17 ` Laszlo Ersek
2017-02-08 16:27 ` Ard Biesheuvel
2017-02-08 18:23 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2017-02-08 18:47 ` Laszlo Ersek
2017-02-09 12:04 ` Heyi Guo
2017-02-10 1:40 ` Alex Hung
2017-02-09 10:35 ` Ard Biesheuvel [this message]
2017-02-09 12:24 ` [Qemu-devel] " Alexander Graf
2017-02-09 12:30 ` Ard Biesheuvel
2017-02-09 12:43 ` Alexander Graf
2017-02-09 12:41 ` Andrew Jones
2017-02-09 12:29 ` Alexander Graf
2017-02-09 12:31 ` Ard Biesheuvel
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=CAKv+Gu_HJ-MNZ+GPsroodWGNVm4z++CSWLUkPR6tro8jUh2zzA@mail.gmail.com \
--to=ard.biesheuvel@linaro.org \
--cc=agraf@suse.de \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.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).