From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Timothy Miller <miller@techsource.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Blocking access to a PCI device for "a long time"?
Date: Sun, 21 Nov 2004 11:10:11 +1100 [thread overview]
Message-ID: <1100995811.27157.46.camel@gaston> (raw)
In-Reply-To: <419E66D1.8000304@techsource.com>
> - Make sure that nothing can get confused by the device "going away" on
> the PCI/AGP bus, using whatever kernel locks are necessary
> - Save PCI config state of device
> - Instruct the FPGA to reload itself
> - Wait many, many, many, many milliseconds
> - Reload PCI config state
> - Unlock and continue
>
> Other drivers accessing the bus for other devices is PROBABLY not a
> problem, but nothing can touch the GPU while it's reloading.
>
> Are there any problems with this approach that would make it a really
> bad idea?
You should read the thread called [PATCH 1/2] pci: Block config access
during BIST where a similar issues with proposed solution is discussed.
Ben.
prev parent reply other threads:[~2004-11-21 0:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 21:34 Blocking access to a PCI device for "a long time"? Timothy Miller
2004-11-21 0:10 ` Benjamin Herrenschmidt [this message]
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=1100995811.27157.46.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.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.