[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6a41d1f8-4be6-40d6-e30d-71abf70f4468@deltatee.com>
Date: Fri, 29 Mar 2019 15:43:23 -0600
From: Logan Gunthorpe <logang@...tatee.com>
To: Jann Horn <jannh@...gle.com>
Cc: Mukesh Ojha <mojha@...eaurora.org>,
Horia Geantă <horia.geanta@....com>,
Muli Ben-Yehuda <mulix@...ix.org>,
Jon Mason <jdmason@...zu.us>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
the arch/x86 maintainers <x86@...nel.org>,
iommu@...ts.linux-foundation.org,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/calgary: fix bitcast type warnings
On 2019-03-29 3:40 p.m., Jann Horn wrote:
> So what is the right thing to do in the context of
> arch/x86/kernel/pci-calgary_64.c? That code wants to perform MMIO with
> endianness conversion, and these accesses are always performed as
> MMIO. Using the non-atomic 64-bit I/O helpers for this would be kind
> of awkward, since the accesses would never actually be split...
Well, if you know you're only ever doing MMIO, you'd probably just want
to use readq() directly.
Logan
Powered by blists - more mailing lists