From: Frank Li <Frank.li@nxp.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Baoquan He <bhe@redhat.com>,
dmaengine@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
imx@lists.linux.dev, linux-kernel@vger.kernel.org,
kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
"Rafael J . Wysocki" <rafael@kernel.org>,
Vinod Koul <vkoul@kernel.org>
Subject: Re: [PATCH v2 1/1] fs: debugfs: fix build error at powerpc platform
Date: Mon, 2 Oct 2023 14:28:11 -0400 [thread overview]
Message-ID: <ZRsLu2IDJd2ueC6d@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <32cd13af-21fa-45bf-9250-b5f3ca132b9b@app.fastmail.com>
On Mon, Oct 02, 2023 at 08:14:47PM +0200, Arnd Bergmann wrote:
> On Mon, Oct 2, 2023, at 16:57, Frank Li wrote:
> > ld: fs/debugfs/file.o: in function `debugfs_print_regs':
> > file.c:(.text+0x95a): undefined reference to `ioread64be'
> >>> ld: file.c:(.text+0x9dd): undefined reference to `ioread64'
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes:
> > https://lore.kernel.org/oe-kbuild-all/202309291322.3pZiyosI-lkp@intel.com/
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
>
> I still think this is wrong, for the reasons I explained in
> https://lore.kernel.org/all/b795ed61-0174-487f-a263-8431e7c76af5@app.fastmail.com/
>
> The part that I had missed earlier is how this is
> related to GENERIC_IOMAP, since on those architectures,
> the ioread helpers are not just fixed-endian MMIO accessors
> like readl and readq but also multiplex to the PIO functions
> (inb/inw/inl) that do not have a 64-bit version because x86
> and PCI both only define those up to 32 bit width.
>
> The best workaround is probably to use readq() instead of
> ioread64(), or swab64(readl()) instead of ioread64_be().
>
> This should work on all 64-bit architectures, plus any 32-bit
> one that defines readq(), so you can just use an 'ifdef readq'
> around the call.
My previous patchs were dropped by vinod.
I think it'd better remove 64bit register at previous patch serise.
Let me create a seperate patch to enable 64bit register support for debug
fs.
Frank
>
> Arnd
prev parent reply other threads:[~2023-10-02 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 14:57 [PATCH v2 1/1] fs: debugfs: fix build error at powerpc platform Frank Li
2023-10-02 18:14 ` Arnd Bergmann
2023-10-02 18:28 ` Frank Li [this message]
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=ZRsLu2IDJd2ueC6d@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=arnd@arndb.de \
--cc=bhe@redhat.com \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=vkoul@kernel.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