From: "Igor Kovalenko" <igor.v.kovalenko@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] sparc64 reverse cas and casx arguments
Date: Mon, 22 Sep 2008 00:59:19 +0400 [thread overview]
Message-ID: <b2fa41d60809211359n71475d07q97bf9ff4518f7eff@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
Hi!
The following patch should fix a problem with sparc64 cas and casx
emulation where value to be stored and value to be compared are passed
in reverse order to helper function.
This also fixes a problem with booting linux iso where kernel tries to
clear memory bitmap bit with casx but fails to find any cleared bit
later.
Please apply.
PS: if anyone can send me a patch for gdb to load and use System.map
file while doing remote debugging that would be great :)
--
Kind regards,
Igor V. Kovalenko
[-- Attachment #2: qemu-cas-reverse-args-20080921.patch --]
[-- Type: application/octet-stream, Size: 878 bytes --]
Index: target-sparc/op_helper.c
===================================================================
--- target-sparc/op_helper.c (revision 5283)
+++ target-sparc/op_helper.c (working copy)
@@ -2194,8 +2226,8 @@
helper_st_asi(addr, val, asi, size);
}
-target_ulong helper_cas_asi(target_ulong addr, target_ulong val1,
- target_ulong val2, uint32_t asi)
+target_ulong helper_cas_asi(target_ulong addr, target_ulong val2,
+ target_ulong val1, uint32_t asi)
{
target_ulong ret;
@@ -2207,8 +2239,8 @@
return ret;
}
-target_ulong helper_casx_asi(target_ulong addr, target_ulong val1,
- target_ulong val2, uint32_t asi)
+target_ulong helper_casx_asi(target_ulong addr, target_ulong val2,
+ target_ulong val1, uint32_t asi)
{
target_ulong ret;
next reply other threads:[~2008-09-21 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 20:59 Igor Kovalenko [this message]
2008-09-22 16:20 ` [Qemu-devel] [PATCH] sparc64 reverse cas and casx arguments Blue Swirl
2008-09-22 20:13 ` Igor Kovalenko
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=b2fa41d60809211359n71475d07q97bf9ff4518f7eff@mail.gmail.com \
--to=igor.v.kovalenko@gmail.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).