Andi Kleen wrote:
I don't see why it's intrusive -- they all use the APIs, right?Yes, but it still changes them. It might have a larger impacton code size for example.
Only if CONFIG_PARAVIRT is defined. And even then, all the performance sensitive stuff uses mmio, no?
-- error compiling committee.c: too many arguments to function - 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] Add I/O hypercalls for i386 paravirt
- From: Jeff Garzik <[email protected]>
- Re: [PATCH] Add I/O hypercalls for i386 paravirt
- From: Andi Kleen <[email protected]>
- Re: [PATCH] Add I/O hypercalls for i386 paravirt
- References:
- [PATCH] Add I/O hypercalls for i386 paravirt
- From: Zachary Amsden <[email protected]>
- Re: [PATCH] Add I/O hypercalls for i386 paravirt
- From: Avi Kivity <[email protected]>
- Re: [PATCH] Add I/O hypercalls for i386 paravirt
- From: Rusty Russell <[email protected]>
- Re: [PATCH] Add I/O hypercalls for i386 paravirt
- From: Andi Kleen <[email protected]>
- Re: [PATCH] Add I/O hypercalls for i386 paravirt
- From: Avi Kivity <[email protected]>
- Re: [PATCH] Add I/O hypercalls for i386 paravirt
- From: Andi Kleen <[email protected]>
- [PATCH] Add I/O hypercalls for i386 paravirt
- Prev by Date: Re: [PATCH 0/3] x86_64 EFI runtime service support
- Next by Date: Re: [PATCH] MAINTAINTERS: use our mail list as Blackfin arch maintainters.
- Previous by thread: Re: [PATCH] Add I/O hypercalls for i386 paravirt
- Next by thread: Re: [PATCH] Add I/O hypercalls for i386 paravirt
- Index(es):
 |