From: Stefan Weil <sw@weilnetz.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Fwd: [PATCH 1.0] eepro100: Fix alignment requirement for statistical counters
Date: Mon, 14 Nov 2011 20:09:54 +0100 [thread overview]
Message-ID: <4EC16782.304@weilnetz.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]
Sorry, I just noticed that I sent this patch to the wrong list address.
It's a patch for QEMU 1.0, so I hope it's not too late for 1.0-rc2.
Regards,
Stefan Weil
-------- Original-Nachricht --------
Betreff: [PATCH] eepro100: Fix alignment requirement for statistical
counters
Datum: Sat, 5 Nov 2011 12:50:30 +0100
Von: Stefan Weil <sw@weilnetz.de>
An: qemu-devel@non-gnu.org
CC: Michael S. Tsirkin <mst@redhat.com>, Stefan Weil <sw@weilnetz.de>
According to Intel's Open Source Software Developer Manual,
the dump counters address must be Dword aligned.
The new code enforces this alignment, so s->statsaddr may now
be used with stw_le_pci_dma() and stl_le_pci_dma().
Signed-off-by: Stefan Weil<sw@weilnetz.de>
---
hw/eepro100.c | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/hw/eepro100.c b/hw/eepro100.c
index 7d59e71..29ec5b4 100644
--- a/hw/eepro100.c
+++ b/hw/eepro100.c
@@ -976,7 +976,15 @@ static void eepro100_cu_command(EEPRO100State * s, uint8_t val)
case CU_STATSADDR:
/* Load dump counters address. */
s->statsaddr = e100_read_reg4(s, SCBPointer);
- TRACE(OTHER, logout("val=0x%02x (status address)\n", val));
+ TRACE(OTHER, logout("val=0x%02x (dump counters address)\n", val));
+ if (s->statsaddr& 3) {
+ /* Memory must be Dword aligned. */
+ logout("unaligned dump counters address\n");
+ /* Handling of misaligned addresses is undefined.
+ * Here we align the address by ignoring the lower bits. */
+ /* TODO: Test unaligned dump counter address on real hardware. */
+ s->statsaddr&= ~3;
+ }
break;
case CU_SHOWSTATS:
/* Dump statistical counters. */
--
1.7.0.4
[-- Attachment #2: Type: text/html, Size: 3025 bytes --]
reply other threads:[~2011-11-14 19:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4EC16782.304@weilnetz.de \
--to=sw@weilnetz.de \
--cc=aliguori@us.ibm.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).