mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	"Yu, Fenghua" <fenghua.yu@intel.com>, Ingo Molnar <mingo@elte.hu>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
	"Zhu, Yi" <yi.zhu@intel.com>, Chris Wright <chrisw@sous-sol.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>
Subject: RE: [PATCH]iwlan dma mapping read and write changes
Date: Wed, 11 Feb 2009 22:13:33 +0000	[thread overview]
Message-ID: <1234390413.3586.85.camel@macbook.infradead.org> (raw)
In-Reply-To: <6F5C1D715B2DA5498A628E6B9C124F04F633E2FA@hasmsx504.ger.corp.intel.com>

On Thu, 2009-02-12 at 00:10 +0200, Winkler, Tomas wrote:
> 
> >-----Original Message-----
> >From: Johannes Berg [mailto:johannes@sipsolutions.net]
> >Sent: Wednesday, February 11, 2009 11:50 PM
> >To: Winkler, Tomas
> >Cc: Yu, Fenghua; David Woodhouse; Ingo Molnar; Stephen Rothwell; Grumbach,
> >Emmanuel; Zhu, Yi; Chris Wright; LKML; iommu@lists.linux-foundation.org
> >Subject: RE: [PATCH]iwlan dma mapping read and write changes
> >
> >On Wed, 2009-02-11 at 22:47 +0100, Johannes Berg wrote:
> >> > >> Indeed the firmware/ucode write back to host memory to update retry
> >> > >> counter for APMDU packets. I'm not sure if this is needed for legacy
> >> > >> traffic, though.
> >> > >
> >> > >I don't think they can be seeing AMPDU packets since that is, well,
> >> > >broken?
> >> >
> >> > Currently I'm not aware of any other cases where memory is accessed
> >> > back but I may have not complete info.  Will be back with the answer
> >> > tomorrow.
> >>
> >> I don't think it really matters, since AMPDU packets will be fixed soon,
> >> and for those you know it's necessary (and the report says that under
> >> some other circumstances it's also necessary). Unless there'd be some
> >> benefit from using BIDI only when we know it'll be needed, and using
> >> TODEV in the other cases?
> >
> >Or if there's a firmware bug.
> 
> That's why it's better to clear the picture. 
> Fenghua
> What exact HW do you get this error?

Lenovo T400.

00:00.0 0600: 8086:2a40 (rev 07)
00:02.0 0300: 8086:2a42 (rev 07)
00:02.1 0380: 8086:2a43 (rev 07)
00:03.0 0780: 8086:2a44 (rev 07)
00:03.2 0101: 8086:2a46 (rev 07)
00:03.3 0700: 8086:2a47 (rev 07)
00:19.0 0200: 8086:10f5 (rev 03)
00:1a.0 0c03: 8086:2937 (rev 03)
00:1a.1 0c03: 8086:2938 (rev 03)
00:1a.2 0c03: 8086:2939 (rev 03)
00:1a.7 0c03: 8086:293c (rev 03)
00:1b.0 0403: 8086:293e (rev 03)
00:1c.0 0604: 8086:2940 (rev 03)
00:1c.1 0604: 8086:2942 (rev 03)
00:1c.2 0604: 8086:2944 (rev 03)
00:1c.3 0604: 8086:2946 (rev 03)
00:1c.4 0604: 8086:2948 (rev 03)
00:1d.0 0c03: 8086:2934 (rev 03)
00:1d.1 0c03: 8086:2935 (rev 03)
00:1d.2 0c03: 8086:2936 (rev 03)
00:1d.7 0c03: 8086:293a (rev 03)
00:1e.0 0604: 8086:2448 (rev 93)
00:1f.0 0601: 8086:2917 (rev 03)
00:1f.2 0106: 8086:2929 (rev 03)
00:1f.3 0c05: 8086:2930 (rev 03)
03:00.0 0280: 8086:4236 
04:00.0 0580: 8086:444e (rev 11)
15:00.0 0607: 1180:0476 (rev ba)
15:00.1 0c00: 1180:0832 (rev 04)

-- 
dwmw2


  parent reply	other threads:[~2009-02-11 22:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 16:56 [PATCH 0/2]Add Variable Page Size and IA64 Support in Intel IOMMU Fenghua Yu
2008-10-03 15:50 ` Bjorn Helgaas
2008-10-06 19:44   ` Yu, Fenghua
2008-10-07  0:01 ` [PATCH V2 0/2] Add " Fenghua Yu
2009-02-11 18:26 ` [PATCH]iwlan dma mapping read and write changes Fenghua Yu
2009-02-11 18:35   ` Bhavesh Davda
2009-02-11 19:29     ` Yu, Fenghua
2009-02-11 18:59   ` Chris Wright
2009-02-11 21:27   ` Winkler, Tomas
2009-02-11 21:33     ` Johannes Berg
2009-02-11 21:41       ` Winkler, Tomas
2009-02-11 21:47         ` Johannes Berg
2009-02-11 21:50           ` Johannes Berg
2009-02-11 22:10             ` Winkler, Tomas
2009-02-11 22:13               ` Yu, Fenghua
2009-02-11 22:13               ` David Woodhouse [this message]
2009-02-12 13:42                 ` Winkler, Tomas

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=1234390413.3586.85.camel@macbook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=chrisw@sous-sol.org \
    --cc=emmanuel.grumbach@intel.com \
    --cc=fenghua.yu@intel.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sfr@canb.auug.org.au \
    --cc=tomas.winkler@intel.com \
    --cc=yi.zhu@intel.com \
    /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

Powered by JetHome