On Thu, 2007-08-09 at 02:24 +0200, Andi Kleen wrote: > Not sure what's best. Ok using a normal export is easiest and not > that big an issue. Yeah, there's also been talk of breaking up paravirt_ops into multiple structs by area, which would lead naturally into finer-grained export control. Cheers, Rusty. - 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 25/25] [PATCH] add paravirtualization support for x86_64
- From: Jeremy Fitzhardinge <[email protected]>
- Re: [PATCH 25/25] [PATCH] add paravirtualization support for x86_64
- References:
- Introducing paravirt_ops for x86_64
- From: Glauber de Oliveira Costa <[email protected]>
- Re: [PATCH 25/25] [PATCH] add paravirtualization support for x86_64
- From: "Glauber de Oliveira Costa" <[email protected]>
- Re: [PATCH 25/25] [PATCH] add paravirtualization support for x86_64
- From: Rusty Russell <[email protected]>
- Re: [PATCH 25/25] [PATCH] add paravirtualization support for x86_64
- From: Andi Kleen <[email protected]>
- Introducing paravirt_ops for x86_64
- Prev by Date: Re: [PATCH] x86_64: Avoid NMI Watchdog and/or long wait in setup_APIC_timer
- Next by Date: Re: [PATCH] x86_64: Avoid NMI Watchdog and/or long wait in setup_APIC_timer
- Previous by thread: Re: [PATCH 25/25] [PATCH] add paravirtualization support for x86_64
- Next by thread: Re: [PATCH 25/25] [PATCH] add paravirtualization support for x86_64
- Index(es):
 |