From: Thomas Gleixner <tglx@linutronix.de>
To: 'Christoph Hellwig' <hch@infradead.org>
Cc: David Wang <davidwang@zhaoxin.com>,
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 15:33:08 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1804171532580.1694@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180417130040.GA9426@infradead.org>
On Tue, 17 Apr 2018, 'Christoph Hellwig' wrote:
> On Tue, Apr 17, 2018 at 10:54:37AM +0200, Thomas Gleixner wrote:
> > The question was rather to have a list of PCI IDs for those chipsets which
> > have the problem and set the 'disable' flag only for those. That makes a lot
> > more sense than making a list of new chips which disable the disable flag.
>
> Agreed.
>
> There are a few other things I'd like to do in this area while we're
> at it (I'm happy to do the work, not trying to offload it to David
> or Thomas):
>
> (1) make the nodac flag a per-device flag. Set for every device
> under one of the affected VIA bridges, or for all PCI devices
> if the nodac command line option is used
> (2) move that flag into the common struct device (or the to be
> designed dma struct hanging off it in the future) and make that
> bit handled in common code as there is a common Xilinx host
> bridge with a 32-bit dma limitation
> (3) kill of the forcesac option, which was a strange performance
> tweak back in plain PCI days, which probably didn't even work
> as expected to start with.
Sounds good.
next prev parent reply other threads:[~2018-04-17 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 8:44 David Wang
2018-04-17 8:54 ` Thomas Gleixner
2018-04-17 13:00 ` 'Christoph Hellwig'
2018-04-17 13:33 ` Thomas Gleixner [this message]
-- 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=alpine.DEB.2.21.1804171532580.1694@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=benjaminpan@viatech.com \
--cc=brucechang@via-alliance.com \
--cc=cooperyan@zhaoxin.com \
--cc=davidwang@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=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
all inboxes | Powered by JetHome®