RE: [RFC PATCH v6 1/5] iommu: add an exported function to get minimum page size for a domain

2019-06-16 Thread Yoshihiro Shimoda
Hi Robin, > From: Robin Murphy, Sent: Friday, June 14, 2019 6:41 PM > > On 13/06/2019 11:20, Yoshihiro Shimoda wrote: > > This patch adds an exported function to get minimum page size for > > a domain. This patch also modifies similar codes on the iommu.c. > > Heh, seeing this gave me a genuine

RE: [RFC PATCH v6 1/5] iommu: add an exported function to get minimum page size for a domain

2019-06-16 Thread Yoshihiro Shimoda
Hi Wolfram-san, > From: Wolfram Sang, Sent: Friday, June 14, 2019 4:38 AM > > On Thu, Jun 13, 2019 at 07:20:11PM +0900, Yoshihiro Shimoda wrote: > > This patch adds an exported function to get minimum page size for > > a domain. This patch also modifies similar codes on the iommu.c. > > > >

RE: [RFC PATCH v6 4/5] mmc: tmio: Use dma_max_mapping_size() instead of a workaround

2019-06-16 Thread Yoshihiro Shimoda
Hi Geert, Christoph, Thank you for your comments! > From: Geert Uytterhoeven, Sent: Friday, June 14, 2019 4:27 PM > > Hi Christoph, > > On Fri, Jun 14, 2019 at 9:18 AM Christoph Hellwig wrote: > > On Thu, Jun 13, 2019 at 10:35:44PM +0200, Geert Uytterhoeven wrote: > > > I'm always triggered by

RE: [RFC PATCH v6 4/5] mmc: tmio: Use dma_max_mapping_size() instead of a workaround

2019-06-16 Thread Yoshihiro Shimoda
Hi Wolfram-san, > From: Wolfram Sang, Sent: Friday, June 14, 2019 4:46 AM > > On Thu, Jun 13, 2019 at 07:20:14PM +0900, Yoshihiro Shimoda wrote: > > Since the commit 133d624b1cee ("dma: Introduce dma_max_mapping_size()") > > provides a helper function to get the max mapping size, we can use > >

Re: [RFC] switch nds32 to use the generic remapping DMA allocator

2019-06-16 Thread Greentime Hu
Christoph Hellwig 於 2019年6月14日 週五 下午8:22寫道: > > On Fri, Jun 14, 2019 at 07:35:29PM +0800, Greentime Hu wrote: > > It looks good to me. I just verified in nds32 platform and it works fine. > > Should I put it in my next-tree or you will pick it up in your tree? :) > > Either way works for me, let

Re: [virtio-dev] Re: [PATCH v8 2/7] dt-bindings: virtio: Add virtio-pci-iommu node

2019-06-16 Thread Michael S. Tsirkin
On Fri, May 31, 2019 at 12:13:47PM +0100, Jean-Philippe Brucker wrote: > On 30/05/2019 18:45, Michael S. Tsirkin wrote: > > On Thu, May 30, 2019 at 06:09:24PM +0100, Jean-Philippe Brucker wrote: > >> Some systems implement virtio-iommu as a PCI endpoint. The operating > >> system needs to discover

Re: [RFC PATCH v4 20/21] iommu/vt-d: hpet: Reserve an interrupt remampping table entry for watchdog

2019-06-16 Thread Thomas Gleixner
On Thu, 23 May 2019, Ricardo Neri wrote: > When the hardlockup detector is enabled, the function > hld_hpet_intremapactivate_irq() activates the recently created entry > in the interrupt remapping table via the modify_irte() functions. While > doing this, it specifies which CPU the interrupt must

Re: [RFC PATCH v4 20/21] iommu/vt-d: hpet: Reserve an interrupt remampping table entry for watchdog

2019-06-16 Thread Thomas Gleixner
On Thu, 23 May 2019, Ricardo Neri wrote: > When interrupt remapping is enabled, MSI interrupt messages must follow a > special format that the IOMMU can understand. Hence, when the HPET hard > lockup detector is used with interrupt remapping, it must also follow this > special format. > > The

Re: [PATCH 3/7] openrisc: remove the partial DMA_ATTR_NON_CONSISTENT support

2019-06-16 Thread Stafford Horne
On Fri, Jun 14, 2019 at 04:44:27PM +0200, Christoph Hellwig wrote: > The openrisc DMA code supports DMA_ATTR_NON_CONSISTENT allocations, but > does not provide a cache_sync operation. This means any user of it > will never be able to actually transfer cache ownership and thus cause > coherency

Re: [RFC PATCH v4 21/21] x86/watchdog/hardlockup/hpet: Support interrupt remapping

2019-06-16 Thread Thomas Gleixner
On Sun, 16 Jun 2019, Thomas Gleixner wrote: > On Thu, 23 May 2019, Ricardo Neri wrote: > > +/** irq_remapping_enabled() - Detect if interrupt remapping is enabled > > + * @hdata: A data structure with the HPET block id > > + * > > + * Determine if the HPET block that the hardlockup detector is

Re: [RFC PATCH v4 21/21] x86/watchdog/hardlockup/hpet: Support interrupt remapping

2019-06-16 Thread Thomas Gleixner
On Thu, 23 May 2019, Ricardo Neri wrote: > +/** irq_remapping_enabled() - Detect if interrupt remapping is enabled > + * @hdata: A data structure with the HPET block id > + * > + * Determine if the HPET block that the hardlockup detector is under > + * the remapped interrupt domain. > + * > + *