From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Jiri Slaby <jslaby@suse.cz>, "H. Peter Anvin" <hpa@zytor.com>,
Akinobu Mita <akinobu.mita@gmail.com>,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, x86@kernel.org,
linux-usb@vger.kernel.org, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] pci-dma: Fix x86 dma_alloc_coherent to fully clear all pages returned
Date: Wed, 18 Feb 2015 12:36:54 -0800 [thread overview]
Message-ID: <20150218203654.GA26136@kroah.com> (raw)
In-Reply-To: <1424290743.9530.122.camel@schen9-desk2.jf.intel.com>
On Wed, Feb 18, 2015 at 12:19:03PM -0800, Tim Chen wrote:
> On Wed, 2015-02-18 at 14:53 -0500, Alan Stern wrote:
> > On Wed, 18 Feb 2015, Tim Chen wrote:
> >
> > > On Wed, 2015-02-04 at 10:30 -0800, Tim Chen wrote:
> > > > On Mon, 2015-02-02 at 19:39 +0300, Sergei Shtylyov wrote:
> > > >
> > > > >
> > > > > > Hi, is this an open-coded version of PAGE_ALIGN?
> > > > >
> > > > > Yes, it appears so. :-)
> > > > >
> > > > > WBR, Sergei
> > > > >
> > > >
> > > > Thanks for the suggestion by Jiri. I updated the patch to use PAGE_ALIGN
> > > > below.
> > > >
> > > > Regards,
> > > > Tim
> > > >
> > >
> > > Is there any resolution on this patch? I haven't seen fixes from the
> > > XHCI folks yet. This is breaking many of our systems.
> >
> > Have you tried doing the experiments I suggested in
> >
> > http://marc.info/?l=linux-usb&m=142272448620716&w=2
> >
> > to determine where the problem occurs?
> >
>
> I was bogged down with other things lately and I haven't got a chance to
> test that. But as you said, there's very few places where xhci
> call this memory allocation. So I think the problem has been fairly
> narrowed down for the XHCI folks.
The "XHCI folks" are in a cube near you, go poke them in person if they
aren't answering their emails :)
good luck,
greg k-h
next prev parent reply other threads:[~2015-02-18 20:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1422647641.9530.2.camel@schen9-desk2.jf.intel.com>
[not found] ` <54CBF1A0.9080005@cogentembedded.com>
2015-01-30 21:54 ` [PATCH] pci-dma: Fix x86 dma_alloc_coherent to fully clear all pages returned Tim Chen
2015-02-02 14:02 ` Jiri Slaby
2015-02-02 16:39 ` Sergei Shtylyov
2015-02-04 18:30 ` Tim Chen
2015-02-18 19:40 ` Tim Chen
2015-02-18 19:53 ` Alan Stern
2015-02-18 20:19 ` Tim Chen
2015-02-18 20:36 ` Greg Kroah-Hartman [this message]
2015-02-18 20:39 ` Andi Kleen
2015-02-18 21:15 ` Alan Stern
2015-02-18 20:45 ` Alan Stern
2015-02-18 23:59 ` Tim Chen
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=20150218203654.GA26136@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mathias.nyman@linux.intel.com \
--cc=mingo@elte.hu \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=stable@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.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;
as well as URLs for NNTP newsgroup(s).