From: Michael Ellerman <mpe@ellerman.id.au>
To: Cyril Bur <cyrilbur@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/pseries: fix endian problems with LE migration
Date: Wed, 21 Jan 2015 14:33:46 +1100 [thread overview]
Message-ID: <1421811226.4900.3.camel@ellerman.id.au> (raw)
In-Reply-To: <1421807520-12030-1-git-send-email-cyrilbur@gmail.com>
On Wed, 2015-01-21 at 13:32 +1100, Cyril Bur wrote:
> The need to handle ibm,suspend_me specially from within ppc_rtas has left an
> endian bug exposed as rtas_ibm_suspend_me actually performs HCALLs and should
> have its params in CPU endian.
That needs a much better explanation.
Key points:
- ppc_rtas() is a syscall, which takes arguments in BE
- ibm,suspend-me is not a real RTAS call and is handled specially in there
- ibm,suspend-me is actually implemented by an hcall
- there is currently a bug on LE, because rtas_ibm_suspend_me() takes the
ppc_rtas() args and feeds them directly to the hcall
> Have ppc_rtas send the params correctly and also interpret the result
> correctly.
That's a second bug which you should also mention above.
> Removed the convoluted use of the rtas_args struct to pass params to
> rtas_ibm_suspend_me in favour of passing what it needs directly.
>
> Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
> ---
> This patch has been tested with KVM both LE and BE and on PowerVM both LE and
> BE. Under QEMU/KVM the migration happens without touching the these code
> pathes.
> For PowerVM there is no obvious regression on BE and the LE code path now
> provides the correct parameters to the hypervisor
Fold that into the changelog, it's worth remembering.
cheers
next prev parent reply other threads:[~2015-01-21 3:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-21 2:32 [PATCH] powerpc/pseries: fix endian problems with LE migration Cyril Bur
2015-01-21 3:33 ` Michael Ellerman [this message]
2015-01-22 5:37 ` Cyril Bur
2015-01-23 2:47 ` 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=1421811226.4900.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=cyrilbur@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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).