From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/hvsi: Fix endianness issues in the HVSI driver
Date: Wed, 19 Aug 2015 23:53:45 +0200 [thread overview]
Message-ID: <55D4FAE9.7000504@linux.vnet.ibm.com> (raw)
In-Reply-To: <1438649494.9418.0.camel@ellerman.id.au>
On 04/08/2015 02:51, Michael Ellerman wrote:
> On Fri, 2015-07-31 at 11:29 +0200, Laurent Dufour wrote:
>> This patch fixes several endianness issues detected when running the HVSI
>> driver in little endian mode.
>>
>> These issues are raised in little endian mode because the data exchanged in
>> memory between the kernel and the hypervisor has to be in big endian
>> format.
>
> Can you include the sparse output before and after?
Hi Michael,
Here is the output message displayed on the console when the bug occurred:
[ 0.000517] irq: (null) didn't like hwirq-0x1000a00 to VIRQ16 mapping
(rc=-22)
[ 0.000578] hvsi_console_init: couldn't create irq mapping for 0x1000a00
With the patch is applied, the hvsi driver is initializing correctly and
no message is displayed, except the one saying the number of device the
hvsi driver has configured. For instance:
[ 1.535783] HVSI: registered 1 devices
Cheers,
Laurent.
next prev parent reply other threads:[~2015-08-19 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 9:29 [PATCH] powerpc/hvsi: Fix endianness issues in the HVSI driver Laurent Dufour
2015-08-03 11:00 ` David Laight
2015-08-19 21:37 ` Laurent Dufour
2015-08-19 21:50 ` Benjamin Herrenschmidt
2015-08-04 0:51 ` Michael Ellerman
2015-08-19 21:53 ` Laurent Dufour [this message]
2015-08-20 1:40 ` Michael Ellerman
2015-08-20 4:20 ` Michael Ellerman
2015-08-21 7:43 ` 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=55D4FAE9.7000504@linux.vnet.ibm.com \
--to=ldufour@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--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 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).