mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Richard Henderson <rth@twiddle.net>,
	Patrick Mochel <mochel@osdl.org>, Willy Tarreau <willy@w.ods.org>,
	Petr Vandrovec <VANDROVE@vc.cvut.cz>,
	linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: /proc/pci deprecation?
Date: Mon, 9 Dec 2002 16:35:11 +0300	[thread overview]
Message-ID: <20021209163511.A1637@jurassic.park.msu.ru> (raw)
In-Reply-To: <Pine.LNX.4.44.0212081747590.1209-100000@home.transmeta.com>; from torvalds@transmeta.com on Sun, Dec 08, 2002 at 05:54:16PM -0800

On Sun, Dec 08, 2002 at 05:54:16PM -0800, Linus Torvalds wrote:
> Writing it back is actively _bad_, since it will make it very hard to
> re-boot the machine without the BIOS re-enumarating the PCI bus and
> filling it in again (ie it would definitely screw up using things like
> kexec() on PC's, if the kernel we boot _from_ is an APIC kernel, but the
> kernel we boot _into_ is not).

True. This applies to alpha as well because of the way how modern consoles
encode IRQs routed through the ISA bridge (actual IRQ + 0xe0).

Probably we should eliminate pcibios_update_irq() call in
drivers/pci/setup-irq.c and see what happens. Nothing bad, I guess.

Ivan.

  parent reply	other threads:[~2002-12-09 13:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-06 23:18 Petr Vandrovec
2002-12-07  7:44 ` Willy Tarreau
2002-12-07 13:20   ` Tomas Szepe
2002-12-07 19:03   ` Linus Torvalds
2002-12-08  2:56     ` Patrick Mochel
2002-12-08  4:21       ` Linus Torvalds
2002-12-08 20:56         ` Richard Henderson
2002-12-09  1:54           ` Linus Torvalds
2002-12-09  3:59             ` Patrick Mochel
2002-12-13 12:36               ` kernel isapnp (2.4.20) h-peter recktenwald
2002-12-09 13:35             ` Ivan Kokshaysky [this message]
2002-12-09 14:11             ` /proc/pci deprecation? Alan Cox
2002-12-09 17:00               ` Linus Torvalds
2002-12-09 18:29                 ` Alan Cox
2002-12-09 18:11                   ` Linus Torvalds
2002-12-09 18:16                     ` Jeff Garzik
2002-12-10  0:43                     ` Alan Cox
2002-12-10  0:30                       ` Linus Torvalds
2002-12-10  5:57                   ` Eric W. Biederman
2002-12-09 23:27                 ` Vojtech Pavlik
2002-12-09 14:14             ` Alan Cox
2002-12-10 16:42         ` Martin Mares
2002-12-07 12:35 ` Erik Hensema
2002-12-07 13:15   ` Dr. David Alan Gilbert
2002-12-07 17:46     ` Arnaldo Carvalho de Melo
2002-12-09 19:03       ` Rogier Wolff
2002-12-09 19:08         ` Arnaldo Carvalho de Melo
2002-12-07 13:14 ` Tomas Szepe
2002-12-07 18:52   ` Petr Vandrovec
2002-12-08 12:30     ` Erik Hensema
2002-12-09 10:14       ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2002-12-09 11:00 Nicolas Mailhot
2002-12-09  9:15 Adam J. Richter
2002-12-06 21:13 Patrick Mochel
2002-12-06 22:17 ` Jeff Garzik
2002-12-06 22:13   ` Patrick Mochel
2002-12-07 16:23     ` Krzysztof Halasa
2002-12-07 21:18     ` Kai Henningsen
2002-12-08 20:01       ` Krzysztof Halasa

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=20021209163511.A1637@jurassic.park.msu.ru \
    --to=ink@jurassic.park.msu.ru \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=rth@twiddle.net \
    --cc=torvalds@transmeta.com \
    --cc=willy@w.ods.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

all inboxes | Powered by JetHome®