From: malc <av1474@comtv.ru>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, agraf@suse.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] PPC64: Add support for ldbrx and stdbrx instructions
Date: Wed, 8 Feb 2012 10:54:21 +0400 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.00.1202081051290.6548@linmac> (raw)
In-Reply-To: <1328680437-31779-1-git-send-email-david@gibson.dropbear.id.au>
On Wed, 8 Feb 2012, David Gibson wrote:
> From: Thomas Huth <thuth@linux.vnet.ibm.com>
>
> These instructions for loading and storing byte-swapped 64-bit values have
> been introduced in PowerISA 2.06.
>
> Signed-off-by: Thomas Huth <thuth@linux.vnet.ibm.com>
> ---
> target-ppc/translate.c | 30 ++++++++++++++++++++++++++++++
> 1 files changed, 30 insertions(+), 0 deletions(-)
I seem to recall that POWER5 machine i had access to didn't have
ld/stdbrx while CBE did have it (or was it the other way around?)
so question is - is PPC_64B sufficient?
[..snip..]
> GEN_LDX(lhbr, ld16ur, 0x16, 0x18, PPC_INTEGER)
> GEN_LDX(lwbr, ld32ur, 0x16, 0x10, PPC_INTEGER)
> @@ -8878,6 +8907,7 @@ GEN_STS(stw, st32, 0x04, PPC_INTEGER)
> #if defined(TARGET_PPC64)
> GEN_STUX(std, st64, 0x15, 0x05, PPC_64B)
> GEN_STX(std, st64, 0x15, 0x04, PPC_64B)
> +GEN_STX(stdbr, st64r, 0x14, 0x14, PPC_64B)
> #endif
> GEN_STX(sthbr, st16r, 0x16, 0x1C, PPC_INTEGER)
> GEN_STX(stwbr, st32r, 0x16, 0x14, PPC_INTEGER)
>
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2012-02-08 6:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 5:53 [Qemu-devel] [PATCH] PPC64: Add support for ldbrx and stdbrx instructions David Gibson
2012-02-08 6:54 ` malc [this message]
2012-02-08 10:48 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-02-08 13:27 ` Thomas Huth
2012-02-09 0:26 ` David Gibson
2012-02-09 7:43 ` Thomas Huth
2012-02-09 13:49 ` Alexander Graf
-- strict thread matches above, loose matches on Subject: below --
2012-02-10 6:21 [Qemu-devel] " David Gibson
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=alpine.LNX.2.00.1202081051290.6548@linmac \
--to=av1474@comtv.ru \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).