Helge Deller
2020-Sep-01 16:21 UTC
[Nouveau] [PATCH 07/28] 53c700: improve non-coherent DMA handling
On 01.09.20 17:22, James Bottomley wrote:> On Tue, 2020-09-01 at 16:05 +0100, Matthew Wilcox wrote: >> On Tue, Sep 01, 2020 at 07:52:40AM -0700, James Bottomley wrote: >>> I think this looks mostly OK, except for one misnamed parameter >>> below. Unfortunately, the last non-coherent parisc was the 700 >>> series and I no longer own a box, so I can't test that part of it >>> (I can fire up the C360 to test it on a coherent arch). >> >> I have a 715/50 that probably hasn't been powered on in 15 years if >> you need something that old to test on (I believe the 725/100 uses >> the 7100LC and so is coherent). I'll need to set up a cross-compiler >> ... > > I'm not going to say no to actual testing, but it's going to be a world > of pain getting something so old going. I do have a box of older > systems I keep for architectural testing that I need to rummage around > in ... I just have a vague memory that my 715 actually caught fire a > decade ago and had to be disposed of.I still have a zoo of machines running for such testing, including a 715/64 and two 730. I'm going to test this git tree on the 715/64: git://git.infradead.org/users/hch/misc.git dma_alloc_pages Helge
Helge Deller
2020-Sep-01 16:41 UTC
[Nouveau] [PATCH 07/28] 53c700: improve non-coherent DMA handling
On 01.09.20 18:21, Helge Deller wrote:> On 01.09.20 17:22, James Bottomley wrote: >> On Tue, 2020-09-01 at 16:05 +0100, Matthew Wilcox wrote: >>> On Tue, Sep 01, 2020 at 07:52:40AM -0700, James Bottomley wrote: >>>> I think this looks mostly OK, except for one misnamed parameter >>>> below. Unfortunately, the last non-coherent parisc was the 700 >>>> series and I no longer own a box, so I can't test that part of it >>>> (I can fire up the C360 to test it on a coherent arch). >>> >>> I have a 715/50 that probably hasn't been powered on in 15 years if >>> you need something that old to test on (I believe the 725/100 uses >>> the 7100LC and so is coherent). I'll need to set up a cross-compiler >>> ... >> >> I'm not going to say no to actual testing, but it's going to be a world >> of pain getting something so old going. I do have a box of older >> systems I keep for architectural testing that I need to rummage around >> in ... I just have a vague memory that my 715 actually caught fire a >> decade ago and had to be disposed of. > > I still have a zoo of machines running for such testing, including a > 715/64 and two 730. > I'm going to test this git tree on the 715/64: > git://git.infradead.org/users/hch/misc.git dma_alloc_pagesThis tree boots nicely (up to a command prompt with i82596 nic working): 53c700: Version 2.8 By James.Bottomley at HansenPartnership.com scsi0: 53c710 rev 2 scsi host0: LASI SCSI 53c700 scsi 0:0:6:0: Direct-Access QUANTUM FIREBALL_TM3200S 300X PQ: 0 ANSI: 2 scsi target0:0:6: Beginning Domain Validation scsi 0:0:6:0: tag#56 Enabling Tag Command Queuing scsi target0:0:6: asynchronous scsi target0:0:6: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 8) scsi target0:0:6: Domain Validation skipping write tests scsi target0:0:6: Ending Domain Validation scsi 0:0:6:1: tag#63 Disabling Tag Command Queuing st: Version 20160209, fixed bufsize 32768, s/g segs 256 sd 0:0:6:0: Power-on or device reset occurred sd 0:0:6:0: Attached scsi generic sg0 type 0 LASI 82596 driver - Revision: 1.30 Found i82596 at 0xf0107000, IRQ 17 eth0: 82596 at 0xf0107000, 08:00:09:c2:9e:60 IRQ 17. sd 0:0:6:0: [sda] 6281856 512-byte logical blocks: (3.22 GB/3.00 GiB) sd 0:0:6:0: [sda] Write Protect is off Christoph, you may add a Tested-by: Helge Deller <deller at gmx.de> # parisc to the series. Helge
Matthew Wilcox
2020-Sep-01 16:53 UTC
[Nouveau] [PATCH 07/28] 53c700: improve non-coherent DMA handling
On Tue, Sep 01, 2020 at 06:41:12PM +0200, Helge Deller wrote:> > I still have a zoo of machines running for such testing, including a > > 715/64 and two 730. > > I'm going to test this git tree on the 715/64:The 715/64 is a 7100LC machine though. I think you need to boot on the 730 to test the non-coherent path.
Possibly Parallel Threads
- [PATCH 07/28] 53c700: improve non-coherent DMA handling
- [PATCH 07/28] 53c700: improve non-coherent DMA handling
- [PATCH 07/28] 53c700: improve non-coherent DMA handling
- [PATCH 11/17] sgiseeq: convert to dma_alloc_noncoherent
- [PATCH 07/28] 53c700: improve non-coherent DMA handling