public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andi Kleen <ak@suse.de>
Cc: Jeff Garzik <jeff@garzik.org>,
	discuss@x86-64.org, torvalds@osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [discuss] Re: Please pull x86-64 bug fixes
Date: Thu, 05 Oct 2006 23:00:49 +0100	[thread overview]
Message-ID: <1160085649.1607.35.camel@localhost.localdomain> (raw)
In-Reply-To: <200610051953.23510.ak@suse.de>

Ar Iau, 2006-10-05 am 19:53 +0200, ysgrifennodd Andi Kleen:
> If you have a patch that works with all known BIOS bugs (including Mac Mini,
> a random Intel 975 board and a Asus AMD K8 board with PCI Express) please share it.

Well you currently don't have such a patch so thats a disingenuous
argument. More useful for the short term till this is fixed might be to
provide

	pci_requires_mmconfig(dev)

which forces it on for that device regardless and may (internal
implementation detail) print a warning "if your system hangs at this
point.." type message.

That gets us the best of both worlds.


  parent reply	other threads:[~2006-10-05 21:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-05 17:10 Please pull x86-64 bug fixes Andi Kleen
2006-10-05 17:17 ` Jeff Garzik
2006-10-05 17:31   ` [discuss] " Andi Kleen
2006-10-05 17:43     ` Jeff Garzik
2006-10-05 17:53       ` Andi Kleen
2006-10-05 19:29         ` Jeff Garzik
2006-10-05 19:42           ` Andi Kleen
2006-10-05 20:02             ` Jeff Garzik
2006-10-05 20:10               ` Andi Kleen
2006-10-05 22:45               ` Linus Torvalds
2006-10-05 22:52                 ` Andi Kleen
2006-10-05 23:07                   ` Linus Torvalds
2006-10-05 23:21                     ` Andi Kleen
2006-10-05 23:36                     ` Jeff Garzik
2006-10-06  0:57                     ` Jeff Garzik
2006-10-06  1:29                       ` Linus Torvalds
2006-10-06 11:03                 ` Arjan van de Ven
2006-10-06 16:07                   ` Linus Torvalds
2006-10-06 16:19                     ` Arjan van de Ven
2006-10-06 22:01                     ` Rafael J. Wysocki
2006-10-06 22:31                       ` Duran, Leo
2006-10-06 23:06                         ` Jeff Garzik
2006-10-07  5:23                           ` Arjan van de Ven
2006-10-07  2:20                         ` Linus Torvalds
2006-10-08 20:59                           ` Duran, Leo
2006-10-08 22:42                             ` Linus Torvalds
2006-10-05 22:00         ` Alan Cox [this message]
2006-10-05 21:44           ` Andi Kleen
2006-10-06 11:14             ` Alan Cox
2006-10-16 12:21               ` Andi Kleen
2006-10-05 17:21 ` Linus Torvalds
2006-10-05 17:27   ` [discuss] " Andi Kleen
2006-10-05 22:59     ` Linus Torvalds
2006-10-05 23:05       ` Andi Kleen

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=1160085649.1607.35.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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