From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
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 v4
Date: Fri, 29 Aug 2008 08:26:52 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808290824070.3300@nehalem.linux-foundation.org> (raw)
In-Reply-To: <20080829063012.GA19459@elte.hu>
On Fri, 29 Aug 2008, Ingo Molnar wrote:
>
> BIOS-e820: 0000000077ff0000 - 0000000078000000 (reserved)
> BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
> BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
>
> which overlaps with the chipset PCI BAR (hpet) resource:
>
> pci 0000:00:14.0: BAR has HPET at fed00000-fed003ff
>
> so due to this 1K conflict we take the full e820-reserved entry out and
> give the range 0xfec00000-0x100000000 as 'free'.
That's wrong. It's a full overlap, so "insert_resource()" should happily
insert the 00000000fec00000 - 0000000100000000 _around_ the HPET bar.
Do you actually see this behavior, or do you just misunderstand how
"insert_resource()" works?
Linus
next prev parent reply other threads:[~2008-08-29 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-29 1:29 Yinghai Lu
2008-08-29 6:30 ` Ingo Molnar
2008-08-29 6:47 ` Yinghai Lu
2008-08-29 6:58 ` Ingo Molnar
2008-08-29 7:16 ` Yinghai Lu
2008-08-29 7:28 ` Ingo Molnar
2008-08-29 7:52 ` Yinghai Lu
2008-08-29 15:31 ` Linus Torvalds
2008-08-29 15:26 ` Linus Torvalds [this message]
2008-09-06 17:55 ` Ingo Molnar
2008-08-30 7:58 [PATCH] x86: unify using pci_mmcfg_insert_resource Yinghai Lu
2008-08-30 7:58 ` [PATCH] x86: split e820 reserved entries record to late v4 Yinghai Lu
2008-08-30 20:36 Yinghai Lu
2008-08-31 2:18 ` Yinghai Lu
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.0808290824070.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®