From: Andi Kleen <ak@muc.de>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Peter Buckingham <peter@pantasys.com>,
"David S. Miller" <davem@davemloft.net>,
jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: Mystery packet killing tg3
Date: 5 May 2005 20:01:06 +0200
Date: Thu, 5 May 2005 20:01:06 +0200 [thread overview]
Message-ID: <20050505180106.GA24386@muc.de> (raw)
In-Reply-To: <427A47C9.6040302@osdl.org>
On Thu, May 05, 2005 at 09:20:25AM -0700, Stephen Hemminger wrote:
> Andi Kleen wrote:
>
> >>>IOMMU code on x86-64 should be never active unless Stephen
> >>>used IOMMU_DEBUG or iommu=force. THat is because the tg3
> >>>is a 64bit capable device and should always use bypass.
> >>>
> >>>
> >>how is this detected? we have a board that is using a 32bit e1000 and we
> >>have to use iommu=force otherwise it doesn't do the right thing with >
> >>4GB of RAM.
> >>
> >>
> >
> >"32bit e1000"? How did you get such a beast? AFAIK all e1000s are 64bit
> >address capable. Please supply a full boot log without iommu=force
> >and describe what happens exactly.
> >
> >
> One of the osdl e1000's in the lab is an IBM rebranded card that although
> it uses a 64bit slot, is really only 32bit
Ok, but it still supports DAC. The PCI bus width is a different
thing from the size of the address registers.
What we are talking about here is just if the card can directly
address physical memory above 4GB. What width the bus is
is a hardware internal thing that we do not really care about
in the IOMMU code.
-Andi
next prev parent reply other threads:[~2005-05-05 18:01 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 23:24 Mystery packet killing tg3 Stephen Hemminger
2005-05-03 3:02 ` David S. Miller
2005-05-03 21:05 ` Stephen Hemminger
2005-05-03 21:13 ` David S. Miller
2005-05-03 20:41 ` Michael Chan
2005-05-03 22:03 ` David S. Miller
2005-05-03 21:28 ` Michael Chan
2005-05-03 22:53 ` David S. Miller
2005-05-03 22:45 ` Stephen Hemminger
2005-05-03 22:39 ` David S. Miller
2005-05-03 22:59 ` Stephen Hemminger
2005-05-03 21:29 ` Stephen Hemminger
2005-05-04 18:30 ` Andi Kleen
2005-05-04 18:44 ` Peter Buckingham
2005-05-05 11:43 ` Andi Kleen
2005-05-05 16:20 ` Stephen Hemminger
2005-05-05 18:01 ` Andi Kleen [this message]
2005-05-05 17:09 ` Peter Buckingham
2005-05-05 17:32 ` Rick Jones
2005-05-05 17:38 ` Peter Buckingham
2005-05-05 17:45 ` John Heffner
2005-05-05 18:06 ` Andi Kleen
2005-05-05 18:21 ` Peter Buckingham
2005-05-05 18:31 ` Andi Kleen
2005-05-05 18:40 ` Peter Buckingham
2005-05-05 18:56 ` Andi Kleen
2005-05-05 19:02 ` Peter Buckingham
2005-05-05 19:24 ` Andi Kleen
2005-05-04 19:41 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 6:09 Michael Chan
2005-05-04 6:27 Michael Chan
2005-05-04 22:51 ` Stephen Hemminger
2005-05-04 22:30 ` Michael Chan
[not found] ` <20050505113356.0f1b4c00.davem@davemloft.net>
2005-05-05 19:56 ` Michael Chan
2005-05-05 21:42 ` David S. Miller
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=20050505180106.GA24386@muc.de \
--to=ak@muc.de \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=peter@pantasys.com \
--cc=shemminger@osdl.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).