From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Gregory Cl??ment <gregory.clement@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org
Subject: Re: Issue with the emulated PCI bridge implementation
Date: Thu, 2 Jan 2014 17:26:56 -0700 [thread overview]
Message-ID: <20140103002656.GA12098@obsidianresearch.com> (raw)
In-Reply-To: <20131226165241.2c50b244@skate>
On Thu, Dec 26, 2013 at 04:52:41PM +0100, Thomas Petazzoni wrote:
> Here is an implementation of this idea, tested to work with an e1000e
> card, with the driver modified to do a few read/write to the I/O
> region. What do you think about it?
This seems reasonable, the only down side is that a stray read to an
unused portion of the Linux IO mapping will lock the machine instead
of getting a page fault - however I don't see that as a blocker.
Regards,
Jason
WARNING: multiple messages have this Message-ID (diff)
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: Issue with the emulated PCI bridge implementation
Date: Thu, 2 Jan 2014 17:26:56 -0700 [thread overview]
Message-ID: <20140103002656.GA12098@obsidianresearch.com> (raw)
In-Reply-To: <20131226165241.2c50b244@skate>
On Thu, Dec 26, 2013 at 04:52:41PM +0100, Thomas Petazzoni wrote:
> Here is an implementation of this idea, tested to work with an e1000e
> card, with the driver modified to do a few read/write to the I/O
> region. What do you think about it?
This seems reasonable, the only down side is that a stray read to an
unused portion of the Linux IO mapping will lock the machine instead
of getting a page fault - however I don't see that as a blocker.
Regards,
Jason
next prev parent reply other threads:[~2014-01-03 0:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-26 15:05 Issue with the emulated PCI bridge implementation Thomas Petazzoni
2013-12-26 15:05 ` Thomas Petazzoni
2013-12-26 15:52 ` Thomas Petazzoni
2013-12-26 15:52 ` Thomas Petazzoni
2014-01-02 21:41 ` Bjorn Helgaas
2014-01-02 21:41 ` Bjorn Helgaas
2014-01-03 0:26 ` Jason Gunthorpe [this message]
2014-01-03 0:26 ` Jason Gunthorpe
2014-01-03 12:22 ` Arnd Bergmann
2014-01-03 12:22 ` Arnd Bergmann
2014-01-03 18:44 ` Jason Gunthorpe
2014-01-03 18:44 ` Jason Gunthorpe
2014-01-03 19:03 ` Arnd Bergmann
2014-01-03 19:03 ` Arnd Bergmann
2014-01-03 19:01 ` Thomas Petazzoni
2014-01-03 19:01 ` Thomas Petazzoni
2014-01-03 19:04 ` Arnd Bergmann
2014-01-03 19:04 ` Arnd Bergmann
2014-01-03 19:10 ` Thomas Petazzoni
2014-01-03 19:10 ` Thomas Petazzoni
2014-01-03 19:13 ` Arnd Bergmann
2014-01-03 19:13 ` Arnd Bergmann
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=20140103002656.GA12098@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=alior@marvell.com \
--cc=bhelgaas@google.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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 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.