> I've occasionally wondered if that spinlock needs to get split up, but > for the amount of pain that could ensue, I can't imagine it ever being > worthwhile. Wondered the same thing and decided against it. I do have every now and then some really crazy cases to deal with. One of them is the need to use something like fixmap/kmap_atomic because a vendors makes 32 bits CPUs that need 512MB of address space to map config space :-) Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Arjan van de Ven <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Jeff Garzik <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Arjan van de Ven <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Matthew Wilcox <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Arjan van de Ven <[email protected]>
- Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- From: Matthew Wilcox <[email protected]>
- [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- Prev by Date: Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- Next by Date: Re: do not stop/start devices in suspend/resume path: the SCSI case
- Previous by thread: Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- Next by thread: Re: [patch] Make MMCONFIG space (extended PCI config space) a driver opt-in issue
- Index(es):
 |