From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [1/2] powerpc/pseries: Fix DTL buffer registration
Date: Thu, 4 Oct 2018 16:14:43 +1000 (AEST) [thread overview]
Message-ID: <42QjKJ4SDWz9sB7@ozlabs.org> (raw)
In-Reply-To: <d0f92a8bcbf03087c7aa7a98d9865d5ab91a9b39.1538035689.git.naveen.n.rao@linux.vnet.ibm.com>
On Thu, 2018-09-27 at 08:10:57 UTC, "Naveen N. Rao" wrote:
> When CONFIG_VIRT_CPU_ACCOUNTING_NATIVE is not set, we register the DTL
> buffer for a cpu when the associated file under powerpc/dtl in debugfs
> is opened. When doing so, we need to set the size of the buffer being
> registered in the second u32 word of the buffer. This needs to be in big
> endian, but we are not doing the conversion resulting in the below error
> showing up in dmesg:
>
> dtl_start: DTL registration for cpu 0 (hw 0) failed with -4
>
> Fix this in the obvious manner.
>
> Fixes: 7c105b63bd98 ("powerpc: Add CONFIG_CPU_LITTLE_ENDIAN kernel config option.")
> Signed-off-by: Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/db787af1b8a6b4be428ee2ea7d409d
cheers
next prev parent reply other threads:[~2018-10-04 6:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 8:10 [PATCH 0/2] A few fixes to DTL buffer access over debugfs Naveen N. Rao
2018-09-27 8:10 ` [PATCH 1/2] powerpc/pseries: Fix DTL buffer registration Naveen N. Rao
2018-10-04 6:14 ` Michael Ellerman [this message]
2018-09-27 8:10 ` [PATCH 2/2] powerpc/pseries: Fix how we iterate over the DTL entries Naveen N. Rao
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=42QjKJ4SDWz9sB7@ozlabs.org \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
/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).