[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F7D4922D6@ORSMSX110.amr.corp.intel.com>
Date: Tue, 11 Dec 2018 17:13:30 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Christoph Hellwig <hch@....de>
CC: "iommu@...ts.linux-foundation.org" <iommu@...ts.linux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jesper Dangaard Brouer <brouer@...hat.com>,
Tariq Toukan <tariqt@...lanox.com>,
Ilias Apalodimas <ilias.apalodimas@...aro.org>,
Toke Høiland-Jørgensen <toke@...e.dk>,
Robin Murphy <robin.murphy@....com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"Marek Szyprowski" <m.szyprowski@...sung.com>,
"Busch, Keith" <keith.busch@...el.com>,
"Derrick, Jonathan" <jonathan.derrick@...el.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [RFC] avoid indirect calls for DMA direct mappings v2
> But that might not be your fault. My ancient system is getting flaky. A v4.19 build that
> has booted before is also resetting :-(
After a power-cycle (and some time to let the machine cool off). System now boots
with your patch series plus the __phys_to_pfn() #define
So if you can figure the right way to fix that, you are good to go.
Tested-by: Tony Luck <tony.luck@...el.com>
Powered by blists - more mailing lists