[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <478543C5.5030401@zytor.com>
Date: Wed, 09 Jan 2008 13:59:33 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Christer Weinigel <christer@...nigel.se>
CC: Zachary Amsden <zach@...are.com>,
Rene Herman <rene.herman@...access.nl>,
"David P. Reed" <dpreed@...d.com>, Avi Kivity <avi@...ranet.com>,
Ondrej Zary <linux@...nbow-software.org>,
Bodo Eggert <7eggert@....de>, Ingo Molnar <mingo@...e.hu>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Paul Rolland <rol@...917.net>, Pavel Machek <pavel@....cz>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
rol <rol@...be.net>
Subject: Re: Re: [PATCH] x86: provide a DMI based port 0x80
I/O delay override.
Christer Weinigel wrote:
> On Wed, 09 Jan 2008 10:18:11 -0800
> "H. Peter Anvin" <hpa@...or.com> wrote:
>
>> Zachary Amsden wrote:
>>> I'm speaking specifically in terms of 64-bit platforms here.
>>> Shouldn't we unconditionally drop outb_p doing extra port I/O on
>>> 64-bit architectures? Especially considering they don't even have
>>> an ISA bus where the decode timing could even matter?
>>>
>> Why should the bitsize of the CPU matter for this? It seems one of
>> the less meaningful keys for this.
>
> Well, anything that runs x86_64 should be a fairly modern system.
>
Yes, but you hardly want a situation where the machine works booting a
32-bit kernel and not a 64-bit kernel, or vice versa.
Furthermore, it's not so much about "modern" versus "old", it is about
picking a certain set of bugs.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists