From: Eric Blake <eblake@redhat.com>
To: "Gabriel L. Somlo" <gsomlo@gmail.com>,
"Richard W.M. Jones" <rjones@redhat.com>
Cc: matt.fleming@intel.com, mdroth@linux.vnet.ibm.com,
jordan.l.justen@intel.com, "Gabriel L. Somlo" <somlo@cmu.edu>,
qemu-devel@nongnu.org, gleb@cloudius-systems.com,
kraxel@redhat.com, pbonzini@redhat.com,
Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Qemu-devel] RFC: guest-side retrieval of fw_cfg file
Date: Thu, 16 Jul 2015 13:27:15 -0600 [thread overview]
Message-ID: <55A80593.60309@redhat.com> (raw)
In-Reply-To: <20150716004322.GA15850@GLSMBP.INI.CMU.EDU>
[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]
On 07/15/2015 06:43 PM, Gabriel L. Somlo wrote:
>
> OK, so I replaced my port i/o with mmio equivalents:
>
> -#define FW_CFG_PORT_CTL 0x510
> +#define FW_CFG_PORT_CTL (void *)0x09020008
>
> -#define FW_CFG_PORT_DATA 0x511
> +#define FW_CFG_PORT_DATA (void *)0x09020000
Under-parenthesized; you'll want:
#define FW_CFG_PORT_DATA ((void *)0x09020000)
to be useful in all possible locations where an identifier can appear in
an expression.
>
> - outw(select, FW_CFG_PORT_CTL);
> + writew(select, FW_CFG_PORT_CTL);
>
> - inb(FW_CFG_PORT_DATA);
> + readb(FW_CFG_PORT_DATA);
>
> - insb(FW_CFG_PORT_DATA, buf, count);
> + readsb(FW_CFG_PORT_DATA, buf, count);
But as it doesn't affect your usage here...
>
> I'm probably missing something that'll turn out to be really obvious
> in retrospect... :)
I probably didn't spot the really obvious problem.
So much for my drive-by noise :)
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-07-16 19:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 20:09 [Qemu-devel] RFC: guest-side retrieval of fw_cfg file Gabriel L. Somlo
2015-07-13 23:03 ` Eric Blake
2015-07-14 17:00 ` Gabriel L. Somlo
2015-07-15 11:06 ` Matt Fleming
2015-07-15 11:15 ` Laszlo Ersek
2015-07-14 9:43 ` Richard W.M. Jones
2015-07-14 18:23 ` Gabriel L. Somlo
2015-07-14 18:31 ` Gabriel L. Somlo
2015-07-14 18:48 ` Richard W.M. Jones
2015-07-14 18:51 ` Richard W.M. Jones
2015-07-14 19:16 ` Peter Maydell
2015-07-14 19:24 ` Gabriel L. Somlo
2015-07-14 19:24 ` Gerd Hoffmann
2015-07-16 0:43 ` Gabriel L. Somlo
2015-07-16 19:27 ` Eric Blake [this message]
2015-07-16 20:42 ` Gabriel L. Somlo
2015-07-14 11:38 ` Laszlo Ersek
2015-07-15 12:00 ` Matt Fleming
2015-07-20 21:19 ` Gabriel L. Somlo
2015-07-20 22:07 ` Laszlo Ersek
2015-07-25 23:21 ` Gabriel L. Somlo
2015-07-26 9:37 ` Laszlo Ersek
2015-07-15 14:08 ` Michael S. Tsirkin
2015-07-15 16:01 ` Igor Mammedov
2015-07-15 16:24 ` Michael S. Tsirkin
2015-07-16 1:21 ` Gabriel L. Somlo
2015-07-16 6:57 ` Igor Mammedov
2015-07-16 7:30 ` Michael S. Tsirkin
2015-07-16 9:50 ` Igor Mammedov
2015-07-16 10:25 ` Michael S. Tsirkin
2015-07-16 11:15 ` Igor Mammedov
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=55A80593.60309@redhat.com \
--to=eblake@redhat.com \
--cc=gleb@cloudius-systems.com \
--cc=gsomlo@gmail.com \
--cc=jordan.l.justen@intel.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=matt.fleming@intel.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=somlo@cmu.edu \
/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).