Re: change MSI/MSI-X APIs

2015-05-12 Thread Kengo NAKAHARA
Hi, On 2015/05/13 10:34, Christos Zoulas wrote: > On May 13, 9:03am, k-nakah...@iij.ad.jp (Kengo NAKAHARA) wrote: > -- Subject: Re: change MSI/MSI-X APIs > > | > http://www.netbsd.org/~christos/if_wm-example.diff > | > [I have not even tried to compile this, just some thoughts] > | > | That

Re: change MSI/MSI-X APIs

2015-05-12 Thread Christos Zoulas
On May 13, 9:03am, k-nakah...@iij.ad.jp (Kengo NAKAHARA) wrote: -- Subject: Re: change MSI/MSI-X APIs | > http://www.netbsd.org/~christos/if_wm-example.diff | > [I have not even tried to compile this, just some thoughts] | | That URL is not available. Is the same name file directly under

Re: change MSI/MSI-X APIs

2015-05-12 Thread Kengo NAKAHARA
Hi, On 2015/05/12 23:37, Christos Zoulas wrote: > In article <55516416.3050...@iij.ad.jp> you write: >> Here is the example code of if_wm: >>http://www.netbsd.org/~knakahara/unify-msi-apis/if_wm-example.diff >> >> This diff includes pci_intr_disestablish()/pci_intr_release() and >> pci_{intx,m

RE: change MSI/MSI-X APIs

2015-05-12 Thread Terry Moore
> From: tech-kern-ow...@netbsd.org [mailto:tech-kern-ow...@netbsd.org] On > Behalf Of Kengo NAKAHARA > > Hi > > On 2015/05/11 23:18, Christos Zoulas wrote: > > Can't we have a: > > > > int pci_intr_map(struct pci_attach_args *pa, pci_intr_handle_t *ih); > > > > for the drivers that have only

Re: change MSI/MSI-X APIs

2015-05-12 Thread Kengo NAKAHARA
Hi On 2015/05/11 23:18, Christos Zoulas wrote: > In article <555048fd.6020...@iij.ad.jp>, > Kengo NAKAHARA wrote: >> I received feedback from some device driver authors. They point out >> establish, disestablish and release APIs should be unified for INTx, >> MSI and MSI-X. So, I would change th