All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jordan Niethe <jniethe5@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 3/3] powerpc/sstep: Always test lmw and stmw
Date: Tue, 6 Apr 2021 12:04:23 +1000	[thread overview]
Message-ID: <CACzsE9rcECYEBYpUCd=F0P3kNv5o7_2LqycFTsjFabTVgwxR5A@mail.gmail.com> (raw)
In-Reply-To: <87czve15v5.fsf@mpe.ellerman.id.au>

On Fri, Apr 2, 2021 at 12:39 AM Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> Hi Jordan,
>
> Jordan Niethe <jniethe5@gmail.com> writes:
> > Load Multiple Word (lmw) and Store Multiple Word (stmw) will raise an
> > Alignment Exception:
> >   - Little Endian mode: always
> >   - Big Endian mode: address not word aligned
> >
> > These conditions do not depend on cache inhibited memory. Test the
> > alignment handler emulation of these instructions regardless of if there
> > is cache inhibited memory available or not.
> >
> > Signed-off-by: Jordan Niethe <jniethe5@gmail.com>
> > ---
> >  .../powerpc/alignment/alignment_handler.c     | 96 ++++++++++++++++++-
> >  1 file changed, 94 insertions(+), 2 deletions(-)
>
> Because of dd3a44c06f7b ("selftests/powerpc: Only test lwm/stmw on big endian")
> this will need a respin sorry.
>
> You'll need to add macros to generate lmw/stmw using .long, to avoid the
> bug fixed in that commit.
Thanks, I will resend.
>
> cheers

  reply	other threads:[~2021-04-06  2:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25  3:21 [PATCH 1/3] powernv/memtrace: Allow mmaping trace buffers Jordan Niethe
2021-02-25  3:21 ` [PATCH 2/3] selftests/powerpc: Suggest memtrace instead of /dev/mem for ci memory Jordan Niethe
2021-02-25  3:21 ` [PATCH 3/3] powerpc/sstep: Always test lmw and stmw Jordan Niethe
2021-04-01 13:39   ` Michael Ellerman
2021-04-06  2:04     ` Jordan Niethe [this message]
2021-04-10 14:28 ` [PATCH 1/3] powernv/memtrace: Allow mmaping trace buffers Michael Ellerman

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='CACzsE9rcECYEBYpUCd=F0P3kNv5o7_2LqycFTsjFabTVgwxR5A@mail.gmail.com' \
    --to=jniethe5@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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.