From: Phil Sutter <phil@nwl.cc>
To: Andrew Lunn <andrew@lunn.ch>
Cc: linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
ne@erfurth.eu, Johann Baudy <johann.baudy@gnu-log.net>,
Lennert Buytenhek <kernel@wantstofly.org>,
Nicolas Pitre <nico@fluxnic.net>
Subject: Re: ARM, AF_PACKET: caching problems on Marvell Kirkwood
Date: Fri, 6 May 2011 18:17:53 +0200 [thread overview]
Message-ID: <20110506161753.GC20777@orbit.nwl.cc> (raw)
In-Reply-To: <20110505194601.GA10565@lunn.ch>
Hi,
On Thu, May 05, 2011 at 09:46:01PM +0200, Andrew Lunn wrote:
> I can reproduce it on a Kirkwood:
>
> [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
Thanks for the information. Seems like we have the same CPU:
| [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053177
| [ 0.000000] CPU: VIVT data cache, VIVT instruction cache
and it's actually VIVT, not VIPT as I wrote in an earlier mail.
Greetings, Phil
WARNING: multiple messages have this Message-ID (diff)
From: phil@nwl.cc (Phil Sutter)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM, AF_PACKET: caching problems on Marvell Kirkwood
Date: Fri, 6 May 2011 18:17:53 +0200 [thread overview]
Message-ID: <20110506161753.GC20777@orbit.nwl.cc> (raw)
In-Reply-To: <20110505194601.GA10565@lunn.ch>
Hi,
On Thu, May 05, 2011 at 09:46:01PM +0200, Andrew Lunn wrote:
> I can reproduce it on a Kirkwood:
>
> [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053977
Thanks for the information. Seems like we have the same CPU:
| [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=00053177
| [ 0.000000] CPU: VIVT data cache, VIVT instruction cache
and it's actually VIVT, not VIPT as I wrote in an earlier mail.
Greetings, Phil
next prev parent reply other threads:[~2011-05-06 16:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 13:06 ARM, AF_PACKET: caching problems on Marvell Kirkwood Phil Sutter
2011-04-08 13:06 ` Phil Sutter
2011-05-05 14:11 ` Phil Sutter
2011-05-05 14:11 ` Phil Sutter
2011-05-05 14:56 ` Eric Dumazet
2011-05-05 14:56 ` Eric Dumazet
2011-05-06 16:12 ` Phil Sutter
2011-05-06 16:12 ` Phil Sutter
2011-05-05 19:46 ` Andrew Lunn
2011-05-05 19:46 ` Andrew Lunn
2011-05-06 16:17 ` Phil Sutter [this message]
2011-05-06 16:17 ` Phil Sutter
2011-05-09 8:59 ` Phil Sutter
2011-05-09 8:59 ` Phil Sutter
2011-05-25 10:32 ` Phil Sutter
2011-05-25 10:32 ` Phil Sutter
2011-09-02 11:08 ` [PATCH] af_packet: flush complete kernel cache in packet_sendmsg Phil Sutter
2011-09-02 11:08 ` Phil Sutter
2011-09-02 13:46 ` Ben Hutchings
2011-09-02 13:46 ` Ben Hutchings
2011-09-02 13:59 ` Phil Sutter
2011-09-02 13:59 ` Phil Sutter
2011-09-02 17:28 ` Russell King - ARM Linux
2011-09-02 17:28 ` Russell King - ARM Linux
2011-09-05 19:57 ` Phil Sutter
2011-09-05 19:57 ` Phil Sutter
2011-09-06 9:57 ` Russell King - ARM Linux
2011-09-06 9:57 ` Russell King - ARM Linux
2011-09-06 11:05 ` Phil Sutter
2011-09-06 11:05 ` Phil Sutter
[not found] ` <D3F292ADF945FB49B35E96C94C2061B90A239361@nsmail.netscout.com>
2011-09-02 14:00 ` FW: " chetan loke
2011-09-02 14:00 ` chetan loke
2011-09-02 15:31 ` Phil Sutter
2011-09-02 15:31 ` Phil Sutter
2011-09-02 16:49 ` chetan loke
2011-09-02 16:49 ` chetan loke
2011-09-06 9:44 ` Phil Sutter
2011-09-06 9:44 ` Phil Sutter
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=20110506161753.GC20777@orbit.nwl.cc \
--to=phil@nwl.cc \
--cc=andrew@lunn.ch \
--cc=johann.baudy@gnu-log.net \
--cc=kernel@wantstofly.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=ne@erfurth.eu \
--cc=netdev@vger.kernel.org \
--cc=nico@fluxnic.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.