From: Linus Torvalds <torvalds@linux-foundation.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: split e820 reserved entries record to late
Date: Thu, 28 Aug 2008 13:38:33 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808281334150.3300@nehalem.linux-foundation.org> (raw)
In-Reply-To: <48B70ABC.8010805@zytor.com>
On Thu, 28 Aug 2008, H. Peter Anvin wrote:
>
> The sucky case, of course, would be an uninitialized BAR pointing
> into unusable address space which happens to be reserved in e820. This
> seems very difficult to disambiguate from the above case through any
> algorithm that I can think of.
Yeah, well, the good news is that it should be fairly rare. Any sane PCI
device will come out of reset with IO and MEM disabled, and even if some
crazy BIOS enables IO/MEM on it and activates the BAR's with some random
content, I'm not seeing how that would work well with Windows either if it
really was overlapping with some critical real other piece of hardware.
So I'd _assume_ that something like that would break Windows too, and thus
not actually make it into a real product.
Maybe.
Linus
next prev parent reply other threads:[~2008-08-28 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-28 19:39 Yinghai Lu
2008-08-28 20:05 ` Linus Torvalds
2008-08-28 20:19 ` Yinghai Lu
2008-08-28 20:29 ` H. Peter Anvin
2008-08-28 20:38 ` Linus Torvalds [this message]
2008-08-28 20:45 ` H. Peter Anvin
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=alpine.LFD.1.10.0808281334150.3300@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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®