From: Ben Hutchings <bhutchings@solarflare.com>
To: Ariel Elior <ariele@broadcom.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
<eilong@broadcom.com>, linux-pci <linux-pci@vger.kernel.org>
Subject: Re: [PATCH net-next 02/10] bnx2x: Removing indirect register access
Date: Thu, 26 Jan 2012 21:50:08 +0000 [thread overview]
Message-ID: <1327614608.2482.12.camel@bwh-desktop> (raw)
In-Reply-To: <1327593714-18358-3-git-send-email-ariele@broadcom.com>
On Thu, 2012-01-26 at 18:01 +0200, Ariel Elior wrote:
> In virtualized environments indirect access to the device may not be supported
> (depending on the Hypervisor type). Indirect device access was used since in
> some harware contexts (i.e. certain chipset and BIOS) every access the driver
> makes across the pci is followed by a BIOS initiated Zero Length Read to the
> same address.
[...]
This is intriguing. Isn't that a general problem that can affect many
devices? Can you be more specific about which systems have this
behaviour?
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2012-01-26 21:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 16:01 [PATCH 0/10] bnx2x: Physical Device Assignment patch series Ariel Elior
2012-01-26 16:01 ` [PATCH net-next 01/10] bnx2x: Support Queue Per Cos in 5771xx devices Ariel Elior
2012-01-26 16:01 ` [PATCH net-next 02/10] bnx2x: Removing indirect register access Ariel Elior
2012-01-26 21:50 ` Ben Hutchings [this message]
2012-01-27 7:19 ` Eilon Greenstein
2012-01-26 16:01 ` [PATCH net-next 03/10] bnx2x: Obtain Bus Device Function from register Ariel Elior
2012-01-26 16:01 ` [PATCH net-next 04/10] bnx2x: Function Level Reset Final Cleanup Ariel Elior
2012-01-26 16:01 ` [PATCH net-next 05/10] bnx2x: Loaded Firmware Version Validation Ariel Elior
2012-01-26 16:01 ` [PATCH net-next 06/10] bnx2x: Lock PF-common resources Ariel Elior
2012-01-26 16:01 ` [PATCH net-next 07/10] bnx2x: Track active PFs with bitmap Ariel Elior
2012-01-26 16:01 ` [PATCH net-next 08/10] bnx2x: Recovery flow bug fixes Ariel Elior
2012-01-26 16:01 ` [PATCH net-next 09/10] bnx2x: Recoverable and unrecoverable error statistics Ariel Elior
2012-01-26 16:01 ` [PATCH net-next 10/10] bnx2x: Update version to 1.72.0 and copyrights Ariel Elior
2012-01-26 18:40 ` [PATCH 0/10] bnx2x: Physical Device Assignment patch series David 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=1327614608.2482.12.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=ariele@broadcom.com \
--cc=davem@davemloft.net \
--cc=eilong@broadcom.com \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.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).