From: Stefan Weil <stefan.weil@weilnetz.de>
To: QEMU Developer <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] BIOS regression since v2.3.0 (misaligned longword i/o to address 0xffff)
Date: Mon, 27 Jul 2015 07:49:29 +0200 [thread overview]
Message-ID: <55B5C669.8090702@weilnetz.de> (raw)
In-Reply-To: <55B535BE.60806@weilnetz.de>
Am 26.07.2015 um 21:32 schrieb Stefan Weil:
> Hi,
>
> since commit 21f5826a04d38e19488f917e1eef22751490c769
> "seabios: update to 1.8.0 release" there is a misaligned i/o access
> caused by the PC BIOS.
>
> QEMU's PC emulation (qemu-system-i386, qemu-system-x86_64)
> with enabled trace backend reports the misaligned i/o access
> when running the BIOS code:
>
> Misaligned i/o to address 0x0000ffff with size 4 for memory region io
>
> ("to address 0x0000ffff" was added by my debug code)
>
> This issue was reported by users of QEMU for Windows,
> but it is not Windows specific.
>
> Regards
> Stefan
Sorry, I did not notice that the code which reports misaligned access is
not part of the official QEMU code.
Here is the patch for memory.c which adds it:
@@ -1073,6 +1119,9 @@ bool memory_region_access_valid(MemoryRegion *mr,
int access_size, i;
if (!mr->ops->valid.unaligned && (addr & (size - 1))) {
+ fprintf(stderr, "Misaligned i/o to address %08" HWADDR_PRIx
+ " with size %u for memory region %s\n",
+ addr, size, mr->name);
return false;
}
Is the misaligned i/o access done by the BIOS code a feature or a bug?
Regards
Stefan
next prev parent reply other threads:[~2015-07-27 5:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-26 19:32 [Qemu-devel] BIOS regression since v2.3.0 (misaligned longword i/o to address 0xffff) Stefan Weil
2015-07-27 5:49 ` Stefan Weil [this message]
2015-07-27 6:24 ` Stefan Weil
2015-07-27 6:36 ` Stefan Weil
2015-07-27 8:46 ` Paolo Bonzini
2015-07-27 9:32 ` Stefan Weil
2015-07-27 9:45 ` Stefan Weil
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=55B5C669.8090702@weilnetz.de \
--to=stefan.weil@weilnetz.de \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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).