From: Peter Maydell <peter.maydell@linaro.org>
To: Anthony Liguori <aliguori@amazon.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 4/6] target-arm: sort TCG cpreg list by KVM-style 64 bit ID number
Date: Fri, 25 Oct 2013 19:07:27 +0100 [thread overview]
Message-ID: <1382724449-11944-5-git-send-email-peter.maydell@linaro.org> (raw)
In-Reply-To: <1382724449-11944-1-git-send-email-peter.maydell@linaro.org>
From: Alvise Rigo <a.rigo@virtualopensystems.com>
Both KVM and TCG populate the cpreg_list with 64 bit register IDs,
but in the TCG side the cpreg_list is sorted using the 32 bit ID
version while in the kvm side the 64 bit ID version is used. This
patch makes the sorting of the cpreg_list consistent between KVM and
TCG.
Signed-off-by: Alvise Rigo <a.rigo@virtualopensystems.com>
Message-id: 1381513125-26802-1-git-send-email-a.rigo@virtualopensystems.com
[PMM: fixed indent, coding style and commit message formatting]
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
target-arm/helper.c | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/target-arm/helper.c b/target-arm/helper.c
index 73476ed..3445813 100644
--- a/target-arm/helper.c
+++ b/target-arm/helper.c
@@ -225,10 +225,16 @@ static void count_cpreg(gpointer key, gpointer opaque)
static gint cpreg_key_compare(gconstpointer a, gconstpointer b)
{
- uint32_t aidx = *(uint32_t *)a;
- uint32_t bidx = *(uint32_t *)b;
+ uint64_t aidx = cpreg_to_kvm_id(*(uint32_t *)a);
+ uint64_t bidx = cpreg_to_kvm_id(*(uint32_t *)b);
- return aidx - bidx;
+ if (aidx > bidx) {
+ return 1;
+ }
+ if (aidx < bidx) {
+ return -1;
+ }
+ return 0;
}
static void cpreg_make_keylist(gpointer key, gpointer value, gpointer udata)
--
1.7.9.5
next prev parent reply other threads:[~2013-10-25 18:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 18:07 [Qemu-devel] [PULL 0/6] target-arm queue Peter Maydell
2013-10-25 18:07 ` [Qemu-devel] [PULL 1/6] hw/arm/boot: Make user not specifying a kernel not an error Peter Maydell
2013-10-25 18:07 ` [Qemu-devel] [PULL 2/6] hw/arm: Tidy up conditional calls to arm_load_kernel Peter Maydell
2013-10-25 18:07 ` [Qemu-devel] [PULL 3/6] target-arm: Add CP15 VBAR support Peter Maydell
2013-10-25 18:07 ` Peter Maydell [this message]
2013-10-25 18:07 ` [Qemu-devel] [PULL 5/6] target-arm: fix sorting issue of KVM cpreg list Peter Maydell
2013-10-25 18:07 ` [Qemu-devel] [PULL 6/6] integrator: fix Linux boot failure by emulating dbg region Peter Maydell
2013-10-31 14:02 ` [Qemu-devel] [PULL 0/6] target-arm queue Edgar E. Iglesias
2013-10-31 14:18 ` Andreas Färber
2013-10-31 14:21 ` Anthony Liguori
2013-10-31 14:31 ` Peter Maydell
2013-10-31 14:36 ` Andreas Färber
2013-10-31 14:39 ` Anthony Liguori
2013-10-31 14:45 ` Andreas Färber
2013-10-31 14:54 ` Anthony Liguori
2013-10-31 15:04 ` Anthony Liguori
2013-10-31 16:52 ` Andreas Färber
2013-10-31 16:54 ` Anthony Liguori
2013-10-31 17:10 ` Andreas Färber
2013-10-31 17:02 ` Peter Maydell
2013-10-31 17:15 ` Peter Maydell
2013-10-31 18:55 ` Anthony Liguori
2013-10-31 15:16 ` Peter Maydell
2013-10-31 17:14 ` Andreas Färber
2013-10-31 17:18 ` Peter Maydell
2013-10-31 17:27 ` Andreas Färber
2013-10-31 17:51 ` Peter Maydell
2013-10-31 18:58 ` Anthony Liguori
2013-10-31 22:13 ` Edgar E. Iglesias
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=1382724449-11944-5-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=aliguori@amazon.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).