Messages in this thread | | | Date | Wed, 22 Aug 2007 18:34:31 +0100 | From | Alan Cox <> | Subject | Re: [PATCH] Add I/O hypercalls for i386 paravirt |
| |
> out is usually a single byte. Shouldn't be very expensive > to decode. In fact it should be roughly equivalent to your > hypercall multiplex.
Why is a performance critical path on a paravirt kernel even using I/O instructions and not paravirtual device drivers ?
It clearly makes sense to virtualise I/O operations if you are doing that (so you can do posting, triggers and predicted reply handling guest side to keep the trap rate sane) but I don't see why this situation occurs in the first place for paravirt.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |