search for: css_by_id

...On Tue, 9 Apr 2019 19:14:53 +0200 > Cornelia Huck <cohuck at redhat.com> wrote: > > [..] > > > > > At this point, you're always going via the css0 device. I'm > > > > wondering whether you should pass in the cssid here and use > > > > css_by_id(cssid) to make this future proof. But then, I'm not > > > > quite clear from which context this will be called. > > > > > > As said before I don't see MCSS-E coming. Regarding the client code, > > > please check out the rest of the series. Espec...

...urn NULL; > + gen_pool_add_virt(cio_dma_pool, addr, dma_addr, PAGE_SIZE, -1); > + addr = gen_pool_alloc(cio_dma_pool, size); > + } > + return (void *) addr; At this point, you're always going via the css0 device. I'm wondering whether you should pass in the cssid here and use css_by_id(cssid) to make this future proof. But then, I'm not quite clear from which context this will be called. > +} > + > +void cio_dma_free(void *cpu_addr, size_t size) > +{ > + memset(cpu_addr, 0, size); > + gen_pool_free(cio_dma_pool, (unsigned long) cpu_addr, size); > +} >...

...dr, PAGE_SIZE, -1); > > > + addr = gen_pool_alloc(cio_dma_pool, size); > > > + } > > > + return (void *) addr; > > > > At this point, you're always going via the css0 device. I'm wondering > > whether you should pass in the cssid here and use css_by_id(cssid) to > > make this future proof. But then, I'm not quite clear from which > > context this will be called. > > As said before I don't see MCSS-E coming. Regarding the client code, > please check out the rest of the series. Especially patch 6. > > From my...