From: ebiederm@xmission.com (Eric W. Biederman)
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Intel Alder IOAPIC fix
Date: 15 Jan 2004 12:26:34 -0700 [thread overview]
Message-ID: <m17jztau8l.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1074185897.1868.118.camel@mulgrave>
James Bottomley <James.Bottomley@steeleye.com> writes:
> Ah, that explains why it's expecting to find the new resource covering
> the old one.
And that is why I believe it tucks the old resource under the new one.
> > Which is totally something different from this case where we just want
> > to ignore the BIOS, because we know better. I have seen a number of
> > boxes that reserver the area where apics or ioapics live. So I think
> > we need an IORESOURCE_TENTATIVE thing. This is the third flavor of
> > thing that has shown up, lately.
> >
> > Want me to code up a patch?
>
> Well, I'm not sure there's a need for it. It seems to me that all
> insert_resource is supposed to be doing is saying "I've got this
> resource here that should have been placed into the tree...please do it
> now".
>
> The ia64 I forgot this bridge, and the Alder IO-APIC this PCI BAR is
> actually the IO-APIC and thus part of the reserved BIOS area look to be
> similar aspects of the same problem.
The problem of you have an incorrect device tree what do you do yes.
The difference that I see is in how the tree gets wrong, and what
parts of it you want to keep.
> The only difference (which is what I needed the patch for) was that the
> Alder resource needs to go underneath the bios reserved area.
>
> How are you proposing that IORESOURCE_TENTATIVE should work?
The solution I keep am thinking of is to simply push an IORESOURCE_TENTATIVE
thing out of the way.
What I am thinking is that /proc/iomem would start out looking link:
fec00000-fec08fff : reserved
ffe80000-ffffffff : reserved
And end up looking like:
fec00000-fec00fff : reserved
fec01000-fec013ff : 0000:00:0f.0
fec01400-fec08fff : reserved
ffe80000-ffffffff : reserved
And either put the code to do that in request_resource, or have
a demand_resource thing that does it. The only thing worth preserving
in the mixed up BIOS case is that find_resource does not allocate that
range for something else.
Eric
next prev parent reply other threads:[~2004-01-15 19:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 2:55 James Bottomley
2004-01-12 21:24 ` Linus Torvalds
2004-01-12 22:13 ` James Bottomley
2004-01-12 23:04 ` James Bottomley
2004-01-12 23:04 ` Linus Torvalds
2004-01-13 0:25 ` James Bottomley
2004-01-13 0:45 ` James Bottomley
2004-01-13 0:25 ` Linus Torvalds
2004-01-13 16:52 ` James Bottomley
2004-01-15 5:18 ` Eric W. Biederman
2004-01-15 16:58 ` James Bottomley
2004-01-15 19:26 ` Eric W. Biederman [this message]
2004-01-15 19:54 ` James Bottomley
2004-01-16 5:32 ` Eric W. Biederman
2004-01-17 15:18 ` James Bottomley
2004-01-17 19:43 ` Eric W. Biederman
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=m17jztau8l.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.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
all inboxes | Powered by JetHome®