All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Richard Henderson <rth@twiddle.net>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH v3] tcg/ppc: Improve unaligned load/store handling on 64-bit backend
Date: Tue, 21 Jul 2015 14:04:18 +0200	[thread overview]
Message-ID: <55AE3542.5080300@suse.de> (raw)
In-Reply-To: <1437471990.5809.7.camel@kernel.crashing.org>

On 07/21/15 11:46, Benjamin Herrenschmidt wrote:
> On Tue, 2015-07-21 at 07:39 +0100, Richard Henderson wrote:
>> On 07/21/2015 07:33 AM, Benjamin Herrenschmidt wrote:
>>> On Tue, 2015-07-21 at 07:27 +0100, Richard Henderson wrote:
>>>> On 07/21/2015 06:19 AM, Benjamin Herrenschmidt wrote:
>>>>> +    /* Clear the non-page, non-alignment bits from the address */
>>>>>         if (TCG_TARGET_REG_BITS == 32 || TARGET_LONG_BITS == 32) {
>>>>> +        /* We don't support unaligned accesses on 32-bits, preserve
>>>>> +         * the bottom bits and thus trigger a comparison failure on
>>>>> +         * unaligned accesses
>>>>> +         */
>>>>>             tcg_out_rlw(s, RLWINM, TCG_REG_R0, addrlo, 0,
>>>>>                         (32 - s_bits) & 31, 31 - TARGET_PAGE_BITS);
>>>> Why don't you support this unaligned acess with 32-bit guests?
>>> No reason, I just didn't get to do it yet. It's possible, I was just
>>> lazy :-) It also adds one instruction. On 64-bit we always have 2
>>> instructions anyway so it wasn't adding any overhead really, on 32-bit
>>> we get away with a single rlwinm, while adding the unaligned support
>>> would make it an addi + rlwinm.
>> Ah, ok.  I wondered if some older 32-bit host ppc didn't allow it, and the
>> 32-bit guest paid the price.  Anyway,
> No, most implementations support unaligned accesses in common cases. I
> think the worst embedded variants might trap when crossing page
> boundaries but that's about it. I don't think we bother emulating
> this though.
>
>> Reviewed-by: Richard Henderson <rth@twiddle.net>
> Thanks.

So who can pick those up? PPC TCG is pretty much unmaintained since Malc 
disappeared, no?


Alex

  reply	other threads:[~2015-07-21 12:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-21  5:19 [Qemu-devel] [PATCH v3] tcg/ppc: Improve unaligned load/store handling on 64-bit backend Benjamin Herrenschmidt
2015-07-21  6:27 ` Richard Henderson
2015-07-21  6:33   ` Benjamin Herrenschmidt
2015-07-21  6:39     ` Richard Henderson
2015-07-21  9:46       ` Benjamin Herrenschmidt
2015-07-21 12:04         ` Alexander Graf [this message]
2015-07-21 12:26           ` Benjamin Herrenschmidt
2015-07-21 13:48             ` Paolo Bonzini
2015-07-21 14:18               ` Alexander Graf
2015-07-21 21:09                 ` Benjamin Herrenschmidt
2015-07-21 21:06               ` Benjamin Herrenschmidt
2015-07-21 15:30           ` Aurelien Jarno
2015-07-21 15:29 ` Aurelien Jarno
2015-07-24 12:34 ` Richard Henderson

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=55AE3542.5080300@suse.de \
    --to=agraf@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=benh@kernel.crashing.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=rth@twiddle.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.