From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 2/2] vga: Fix portio list conversion fallouts
Date: Sun, 18 Sep 2011 18:51:13 +0300 [thread overview]
Message-ID: <4E761371.3020007@redhat.com> (raw)
In-Reply-To: <4E75E7B0.9080104@web.de>
On 09/18/2011 03:44 PM, Jan Kiszka wrote:
> From: Jan Kiszka<jan.kiszka@siemens.com>
>
> Fix copy&paste errors and reduce duplications of the BOCHS VBE ranges.
>
> Signed-off-by: Jan Kiszka<jan.kiszka@siemens.com>
> ---
>
> #ifdef CONFIG_BOCHS_VBE
> static const MemoryRegionPortio vbe_portio_list[] = {
> -# ifdef TARGET_I386
> { 0, 1, 2, .read = vbe_ioport_read_index, .write = vbe_ioport_write_index },
> +# ifdef TARGET_I386
Strange how the card knows what target it's plugged into. Fixing this
is going to involve major pain - need to update the bios and need to
provide backwards compatibility. All this assuming guests don't
hardcode the address.
Anyway I find the deduplication makes the code harder to read.
> { 1, 1, 2, .read = vbe_ioport_read_data, .write = vbe_ioport_write_data },
> # else
> - { 0, 2, 2, .read = vbe_ioport_read_index, .write = vbe_ioport_write_index },
> - { 2, 2, 2, .read = vbe_ioport_read_data, .write = vbe_ioport_write_data },
> + { 2, 1, 2, .read = vbe_ioport_read_data, .write = vbe_ioport_write_data },
Is this correct? length 1 region with size 2?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-09-18 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 12:44 [Qemu-devel] [PATCH 2/2] vga: Fix portio list conversion fallouts Jan Kiszka
2011-09-18 15:51 ` Avi Kivity [this message]
2011-09-18 16:28 ` Jan Kiszka
2011-09-18 16:51 ` Avi Kivity
2011-09-18 19:07 ` Jan Kiszka
2011-09-19 12:22 ` Avi Kivity
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=4E761371.3020007@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).