From: David Wang <davidwang@zhaoxin.com>
To: 'Christoph Hellwig' <hch@infradead.org>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
<gregkh@linuxfoundation.org>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <brucechang@via-alliance.com>,
<cooperyan@zhaoxin.com>, <qiyuanwang@zhaoxin.com>,
<benjaminpan@viatech.com>, <lukelin@viacpu.com>,
<timguo@zhaoxin.com>
Subject: Re: [PATCH] x86/dma-mapping: override via_no_dac for new VIA PCI bridges
Date: Tue, 17 Apr 2018 16:44:32 +0800 [thread overview]
Message-ID: <000001d3d628$4e91a4c0$ebb4ee40$@zhaoxin.com> (raw)
> -----邮件原件-----
> 发件人: Christoph Hellwig [mailto:hch@infradead.org]
> 发送时间: 2018年4月16日 20:34
> 收件人: David Wang <davidwang@zhaoxin.com>
> 抄送: tglx@linutronix.de; mingo@redhat.com; hpa@zytor.com;
> gregkh@linuxfoundation.org; x86@kernel.org; linux-
> kernel@vger.kernel.org; brucechang@via-alliance.com;
> cooperyan@zhaoxin.com; qiyuanwang@zhaoxin.com;
> benjaminpan@viatech.com; lukelin@viacpu.com; timguo@zhaoxin.com
> 主题: Re: [PATCH] x86/dma-mapping: override via_no_dac for new VIA PCI
> bridges
>
> On Mon, Apr 16, 2018 at 05:26:56PM +0800, David Wang wrote:
> > PCI bridges integrated in new VIA chipset/SoC have no DAC issue.
> > Enable DAC for the platforms with these chipset/SoC can improve DMA
> > performance about 20% when DRAM size > 4GB.
> >
>
> So we get an exception to an exception? Is there any way to figure out
the
> PCI IDs actually affected?
Yes.
Do you mean we should list the PCI IDs of the PCI bridges which have no DAC
issue?
There are lots of PCI bridges(PCIE root ports) in our new chipsets/SoCs. And
no DMA issues found.
So, we only want to recognize the chipset/SoC by reading VID/DID of Bus 0,
Device 17, function 0.
Thx.
---
David
next reply other threads:[~2018-04-17 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 8:44 David Wang [this message]
2018-04-17 8:54 ` [PATCH] x86/dma-mapping: override via_no_dac for new VIA PCI bridges Thomas Gleixner
2018-04-17 13:00 ` 'Christoph Hellwig'
2018-04-17 13:33 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2018-04-16 9:26 David Wang
2018-04-16 12:33 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000001d3d628$4e91a4c0$ebb4ee40$@zhaoxin.com' \
--to=davidwang@zhaoxin.com \
--cc=benjaminpan@viatech.com \
--cc=brucechang@via-alliance.com \
--cc=cooperyan@zhaoxin.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukelin@viacpu.com \
--cc=mingo@redhat.com \
--cc=qiyuanwang@zhaoxin.com \
--cc=tglx@linutronix.de \
--cc=timguo@zhaoxin.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox