On Thursday 03 August 2006 03:25, Christoph Lameter wrote: > Good idea. This will also make it easier to support this special > functionality. And it will avoid use in contexts where these are > not necessary. I think it's a bad idea. We don't want lots of architecture ifdefs in some Xen specific file -Andi - 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/
- Follow-Ups:
- Re: [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor.
- From: Christoph Lameter <[email protected]>
- Re: [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor.
- References:
- [patch 0/8] Basic infrastructure patches for a paravirtualized kernel
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor.
- From: Zachary Amsden <[email protected]>
- Re: [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor.
- From: Christoph Lameter <[email protected]>
- [patch 0/8] Basic infrastructure patches for a paravirtualized kernel
- Prev by Date: Re: [PATCH 2 of 4] [x86-64] Calgary: only verify the allocation bitmap if CONFIG_IOMMU_DEBUG is on
- Next by Date: system freeze on cdrom failure
- Previous by thread: Re: [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor.
- Next by thread: Re: [patch 2/8] Implement always-locked bit ops, for memory shared with an SMP hypervisor.
- Index(es):
 |