From: Gerd Hoffmann <kraxel@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Drew <drjones@redhat.com>, "Stefan Hajnoczi" <stefanha@gmail.com>,
"Gabriel L. Somlo" <somlo@cmu.edu>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Kevin O'Connor" <kevin@koconnor.net>,
"Marc Marí" <markmb@redhat.com>, Laszlo <lersek@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/5] fw_cfg: document fw_cfg_modify_iXX() update functions
Date: Wed, 02 Sep 2015 10:08:49 +0200 [thread overview]
Message-ID: <1441181329.10161.8.camel@redhat.com> (raw)
In-Reply-To: <CAFEAcA-3bpw0hnk6W-F6jZTfXxKU1gExn18BOoj+iUoVYpo2uw@mail.gmail.com>
On Di, 2015-09-01 at 21:10 +0100, Peter Maydell wrote:
> On 1 September 2015 at 20:13, Gabriel L. Somlo <somlo@cmu.edu> wrote:
> > Also, since I'll be tinkering with fw_cfg again, and you mentioned
> > using DT on arm and ACPI on x86 to auto-detect the presence (and location)
> > of fw_cfg from the guest-side in a related thread:
>
> I meant DT or ACPI on ARM, actually. I don't know what the x86
> approach is for fw_cfg but I think it's just "known address".
Yes, "known address". And given that the firmware actually loads the
acpi tables via fw_cfg that is very unlikely to change. Adding it to
the acpi tables might be useful nevertheless so the guest os knows the
ioports are in use.
I think on arm the acpi situation is the same, but I think firmware
detecting the location via DT should work without chicken&egg problems.
cheers,
Gerd
next prev parent reply other threads:[~2015-09-02 8:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 9:08 [Qemu-devel] QEMU fw_cfg DMA interface Marc Marí
2015-08-31 9:10 ` [Qemu-devel] [PATCH v2 0/5] " Marc Marí
2015-08-31 9:10 ` [Qemu-devel] [PATCH v2 1/5] fw_cfg: document fw_cfg_modify_iXX() update functions Marc Marí
2015-09-01 17:33 ` Peter Maydell
2015-09-01 17:45 ` Gabriel L. Somlo
2015-09-01 18:45 ` Peter Maydell
2015-09-01 19:13 ` Gabriel L. Somlo
2015-09-01 20:10 ` Peter Maydell
2015-09-01 20:27 ` Gabriel L. Somlo
2015-09-01 20:30 ` Peter Maydell
2015-09-02 8:08 ` Gerd Hoffmann [this message]
2015-09-02 9:21 ` Laszlo Ersek
2015-08-31 9:10 ` [Qemu-devel] [PATCH v2 2/5] fw_cfg DMA interface documentation Marc Marí
2015-08-31 15:36 ` Kevin O'Connor
2015-09-01 17:47 ` Peter Maydell
2015-09-01 17:56 ` Peter Maydell
2015-08-31 9:10 ` [Qemu-devel] [PATCH v2 3/5] Implement fw_cfg DMA interface Marc Marí
2015-08-31 15:58 ` Kevin O'Connor
2015-09-01 18:35 ` Peter Maydell
2015-08-31 9:10 ` [Qemu-devel] [PATCH v2 4/5] Enable fw_cfg DMA interface for ARM Marc Marí
2015-09-01 18:02 ` Peter Maydell
2015-08-31 9:10 ` [Qemu-devel] [PATCH v2 5/5] Enable fw_cfg DMA interface for x86 Marc Marí
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=1441181329.10161.8.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=drjones@redhat.com \
--cc=kevin@koconnor.net \
--cc=lersek@redhat.com \
--cc=markmb@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=somlo@cmu.edu \
--cc=stefanha@gmail.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).