From: Ralf Baechle <ralf@linux-mips.org>
To: KokHow.Teh@infineon.com
Cc: linux-mips@linux-mips.org
Subject: Re: linux-2.6.20 setjmp/longjmp OR how to contain bus-error for non-existing PCI device during PCI device scan?
Date: Tue, 17 Jul 2007 19:02:47 +0100 [thread overview]
Message-ID: <20070717180247.GA32255@linux-mips.org> (raw)
In-Reply-To: <31E09F73562D7A4D82119D7F6C172986019B76D7@sinse303.ap.infineon.com>
On Tue, Jul 17, 2007 at 07:03:34PM +0800, KokHow.Teh@infineon.com wrote:
> I am using linux-2.6.20 on MIPS24KE and I need to know what is the best way to contain bus error during PCI bus scan process for non-existing device? I thought of setjmp/longjmp but unfortunately, I have `googled` and `find` the whole kernel source tree there is no such support in the kernel for MIPS architecture. Any insight is appreciated.
Welcome to the kernel, there are no setjmp / longjmp. You can can try to
use the functions from <asm/paccess.h> to protect your memory accesses
against bus error exceptions. Note this won't work for cases where the
bus error exceptions is imprecise because then the EPC for the exception
isn't guranteed to have the proper value. The get_dbe / put_dbe functions
are used just like get_user / put_user from <linux/uaccess.h> except that
those are meant to protect against TLB exceptions.
Or just temporarily disable the bus error in your PCI config space
accessors.
Ralf
next prev parent reply other threads:[~2007-07-17 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 11:03 linux-2.6.20 setjmp/longjmp OR how to contain bus-error for non-existing PCI device during PCI device scan? KokHow.Teh
2007-07-17 11:03 ` KokHow.Teh
2007-07-17 18:02 ` Ralf Baechle [this message]
2007-07-18 8:20 ` linux-2.6.20 setjmp/longjmp OR how to contain bus-error fornon-existing " KokHow.Teh
2007-07-18 8:20 ` KokHow.Teh
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=20070717180247.GA32255@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=KokHow.Teh@infineon.com \
--cc=linux-mips@linux-mips.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