Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1519027 > unrolled thread

[PATCH v1 1/1] mfd: intel-lpss: Try to enable Memory-Write-Invalidate

Started byAndy Shevchenko <andriy.shevchenko@linux.intel.com>
First post2016-11-10 16:00 +0100
Last post2016-11-10 17:50 +0100
Articles 4 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH v1 1/1] mfd: intel-lpss: Try to enable Memory-Write-Invalidate Andy Shevchenko <andriy.shevchenko@linux.intel.com> - 2016-11-10 16:00 +0100
    Re: [PATCH v1 1/1] mfd: intel-lpss: Try to enable  Memory-Write-Invalidate Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-11-10 16:10 +0100
      Re: [PATCH v1 1/1] mfd: intel-lpss: Try to enable  Memory-Write-Invalidate Andy Shevchenko <andriy.shevchenko@linux.intel.com> - 2016-11-10 16:30 +0100
        Re: [PATCH v1 1/1] mfd: intel-lpss: Try to enable  Memory-Write-Invalidate Mika Westerberg <mika.westerberg@linux.intel.com> - 2016-11-10 17:50 +0100

#1519027 — [PATCH v1 1/1] mfd: intel-lpss: Try to enable Memory-Write-Invalidate

FromAndy Shevchenko <andriy.shevchenko@linux.intel.com>
Date2016-11-10 16:00 +0100
Subject[PATCH v1 1/1] mfd: intel-lpss: Try to enable Memory-Write-Invalidate
Message-ID<sBYZA-7y9-27@gated-at.bofh.it>
Enable MWI mechanism if PCI bus master supports it.

Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
 drivers/mfd/intel-lpss-pci.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/mfd/intel-lpss-pci.c b/drivers/mfd/intel-lpss-pci.c
index 50e78db..4756153 100644
--- a/drivers/mfd/intel-lpss-pci.c
+++ b/drivers/mfd/intel-lpss-pci.c
@@ -41,6 +41,7 @@ static int intel_lpss_pci_probe(struct pci_dev *pdev,
 
 	/* Probably it is enough to set this for iDMA capable devices only */
 	pci_set_master(pdev);
+	pci_try_set_mwi(pdev);
 
 	ret = intel_lpss_probe(&pdev->dev, info);
 	if (ret)
-- 
2.9.3

[toc] | [next] | [standalone]


#1519043 — Re: [PATCH v1 1/1] mfd: intel-lpss: Try to enable Memory-Write-Invalidate

FromMika Westerberg <mika.westerberg@linux.intel.com>
Date2016-11-10 16:10 +0100
SubjectRe: [PATCH v1 1/1] mfd: intel-lpss: Try to enable Memory-Write-Invalidate
Message-ID<sBZ9g-7QM-25@gated-at.bofh.it>
In reply to#1519027
On Thu, Nov 10, 2016 at 04:51:42PM +0200, Andy Shevchenko wrote:
> Enable MWI mechanism if PCI bus master supports it.

Why?

[toc] | [prev] | [next] | [standalone]


#1519052 — Re: [PATCH v1 1/1] mfd: intel-lpss: Try to enable Memory-Write-Invalidate

FromAndy Shevchenko <andriy.shevchenko@linux.intel.com>
Date2016-11-10 16:30 +0100
SubjectRe: [PATCH v1 1/1] mfd: intel-lpss: Try to enable Memory-Write-Invalidate
Message-ID<sBZsB-7Yu-5@gated-at.bofh.it>
In reply to#1519043
On Thu, 2016-11-10 at 16:59 +0200, Mika Westerberg wrote:
> On Thu, Nov 10, 2016 at 04:51:42PM +0200, Andy Shevchenko wrote:
> > Enable MWI mechanism if PCI bus master supports it.
> 
> Why?

It might be potential benefit in some cases. Documentation says that
standard Memory Write might supply more current data than in the CPU
modified cache line and "trashing a line in the cache may trash some
data that is more current that in the memory line". This allows to avoid
potential retries and other performance degradation issues on the bus.
Though, I dunno how to measure it.

Would be enough to extend commit message by this paragraph?

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

[toc] | [prev] | [next] | [standalone]


#1519130 — Re: [PATCH v1 1/1] mfd: intel-lpss: Try to enable Memory-Write-Invalidate

FromMika Westerberg <mika.westerberg@linux.intel.com>
Date2016-11-10 17:50 +0100
SubjectRe: [PATCH v1 1/1] mfd: intel-lpss: Try to enable Memory-Write-Invalidate
Message-ID<sC0I1-h7-7@gated-at.bofh.it>
In reply to#1519052
On Thu, Nov 10, 2016 at 05:22:40PM +0200, Andy Shevchenko wrote:
> On Thu, 2016-11-10 at 16:59 +0200, Mika Westerberg wrote:
> > On Thu, Nov 10, 2016 at 04:51:42PM +0200, Andy Shevchenko wrote:
> > > Enable MWI mechanism if PCI bus master supports it.
> > 
> > Why?
> 
> It might be potential benefit in some cases. Documentation says that
> standard Memory Write might supply more current data than in the CPU
> modified cache line and "trashing a line in the cache may trash some
> data that is more current that in the memory line". This allows to avoid
> potential retries and other performance degradation issues on the bus.
> Though, I dunno how to measure it.
> 
> Would be enough to extend commit message by this paragraph?

That's better, yes.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web