From: "H. Peter Anvin" <hpa@zytor.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Venkatesh Pallipadi <venki@google.com>,
Prarit Bhargava <prarit@redhat.com>,
Simon Arlott <simon@fire.lp0.eu>,
x86@kernel.org, Clemens Ladisch <clemens@ladisch.de>,
linux-kernel@vger.kernel.org, Marc Jones <marcj303@gmail.com>,
Jordan Crouse <jcrouse@codeaurora.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86, HPET: ignore any PCI BARs that match an HPET we already know about
Date: Wed, 22 Sep 2010 15:10:36 -0700 [thread overview]
Message-ID: <4C9A7EDC.5030809@zytor.com> (raw)
In-Reply-To: <201009221552.21896.bjorn.helgaas@hp.com>
On 09/22/2010 02:52 PM, Bjorn Helgaas wrote:
>
> We don't necessarily need to slavishly copy what Windows does, but
> I'd feel better if we understood how it avoided the problem on the
> Gigabyte board so we could make a more informed decision.
>
> It really doesn't look like Windows, and therefore BIOS writers,
> share your expectations about PCI BARs in E820 reserved areas.
> It's likely still *safe* to make them fixed resources, but we might
> be able to fix more issues if we knew how Windows avoids the problem.
>
Keep in mind that Windows -- the version they tested against -- might
just work by accident. That's a "ship it" condition for the BIOS for
almost every vendor.
Also, do note that the reservations don't necessarily need to come from
the BIOS; we can mark the HPET area internally reserved, for example,
when we discover it.
-hpa
next prev parent reply other threads:[~2010-09-22 22:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 20:15 [PATCH] x86, HPET: ignore any PCI BARs that match an HPET we already know about Bjorn Helgaas
2010-09-22 20:19 ` Bjorn Helgaas
2010-09-22 20:21 ` H. Peter Anvin
2010-09-22 20:56 ` H. Peter Anvin
2010-09-22 21:52 ` Bjorn Helgaas
2010-09-22 22:02 ` H. Peter Anvin
2010-09-22 22:10 ` H. Peter Anvin [this message]
2010-09-22 22:37 ` Bjorn Helgaas
2010-09-22 22:39 ` H. Peter Anvin
2010-09-22 21:22 ` [tip:x86/pci] x86, pci: Ignore " tip-bot for Bjorn Helgaas
2010-09-22 21:48 ` Yinghai Lu
2010-09-22 22:41 ` Bjorn Helgaas
2010-09-22 22:53 ` H. Peter Anvin
2010-09-23 22:51 ` Bjorn Helgaas
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=4C9A7EDC.5030809@zytor.com \
--to=hpa@zytor.com \
--cc=bjorn.helgaas@hp.com \
--cc=clemens@ladisch.de \
--cc=jcrouse@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcj303@gmail.com \
--cc=mingo@redhat.com \
--cc=prarit@redhat.com \
--cc=simon@fire.lp0.eu \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
--cc=x86@kernel.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.