From: "David S. Miller" <davem@davemloft.net>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: jonsmirl@gmail.com, willy@debian.org, linux-kernel@vger.kernel.org
Subject: Re: multi-domain PCI and sysfs
Date: Tue, 7 Sep 2004 21:16:37 -0700 [thread overview]
Message-ID: <20040907211637.20de06f4.davem@davemloft.net> (raw)
In-Reply-To: <200409072115.09856.jbarnes@engr.sgi.com>
On Tue, 7 Sep 2004 21:15:09 -0700
Jesse Barnes <jbarnes@engr.sgi.com> wrote:
> On Tuesday, September 7, 2004 4:11 pm, David S. Miller wrote:
> > This is a real touchy area btw, because if there is no
> > VGA card, such I/O port accesses are going to trap and
> > we need to have a common way to handle that somehow.
>
> So I take it your platform won't soft fail the accesses and return all 1s?
Nope, you get a machine check trap. We have to catch these when doing
PCI config space accesses in the kernel too. Grep for pci_poke_* in
arch/sparc64/kernel/*.c
> A potentially cleaner option which Ben and I would prefer is to use
> the vga device Jon is creating to do legacy I/O with explicit
> read/write or ioctl calls.
Definitely. Note that xfree86 already has a signal handler for this
stuff, ppc generates traps like sparc64 too.
next prev parent reply other threads:[~2004-09-08 4:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 20:00 multi-domain PCI and sysfs Jon Smirl
2004-09-04 21:57 ` Jesse Barnes
2004-09-04 22:12 ` Jon Smirl
2004-09-04 22:27 ` Jesse Barnes
2004-09-04 22:45 ` Jon Smirl
2004-09-04 23:03 ` Jesse Barnes
2004-09-05 23:04 ` Matthew Wilcox
2004-09-05 23:50 ` Jon Smirl
2004-09-05 23:00 ` Alan Cox
2004-09-06 1:40 ` Matthew Wilcox
2004-09-07 22:58 ` Jon Smirl
2004-09-07 23:11 ` David S. Miller
2004-09-08 3:39 ` Jon Smirl
2004-09-08 4:12 ` David S. Miller
2004-09-08 4:16 ` Jesse Barnes
2004-09-08 4:15 ` Jesse Barnes
2004-09-08 4:16 ` David S. Miller [this message]
2004-09-08 4:25 ` Jesse Barnes
2004-09-08 6:01 ` Jon Smirl
2004-09-08 13:02 ` Alan Cox
2004-09-08 16:02 ` Jesse Barnes
2004-09-08 18:20 ` David S. Miller
2004-09-08 18:32 ` Jesse Barnes
2004-09-08 18:54 ` David S. Miller
2004-09-08 6:55 ` Jon Smirl
2004-09-08 11:11 ` Geert Uytterhoeven
2004-09-08 11:38 ` Matthew Wilcox
2004-09-08 18:21 ` David S. Miller
2004-09-08 22:41 ` Alan Cox
2004-09-09 0:31 ` Jon Smirl
2004-09-09 13:06 ` Alan Cox
2004-09-08 15:03 ` Matthew Wilcox
2004-09-06 0:06 ` Jesse Barnes
2004-09-06 0:31 ` Jon Smirl
2004-09-06 1:38 ` Jon Smirl
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=20040907211637.20de06f4.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jbarnes@engr.sgi.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@debian.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 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.