Re: [PATCH] resource/x86: add sticky resource type

[Ingo Molnar]

* Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:

> The fact is, the only reliable way to handle these things has _always_ 
> been to ask the hardware first. Add the broken resources from ACPI and 
> other BIOS tables _later_. If they conflict, it is the ACPI/BIOS 
> tables that should be removed.

i fully agree with that principle, i just messed up implementing it.

'Sticky resources' tried to be exactly the kind of 'untrusted, possibly 
wrong' resources, which should not prevent existing PCI resources from 
being registered - they would at most prevent new PCI resources from 
being allocated over them. (the free space is large enough for us to 
take the small/untrusted hint from the BIOS where not to allocate to)

I missed the possibility of a sticky resource not being wide enough and 
preventing a BAR from being registered, due to partial overlap. That was 
not intended.

I guess this whole patchset has to become a lot wider and a lot more 
involved.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/