Yeah, I agree. I am not advocating we expend energy on this now. But my thoughts at the time were that that particular problem can be solved at io-setup time with some kind of call to qualify the address. Iow: a slow path call with the address would return flags on whether iowrite() should do a real io, or a IOoHC. -greg -----Original Message----- From: Avi Kivity <avi@xxxxxxxxxx> To: Gregory Haskins <GHaskins@xxxxxxxxxx> Cc: <mingo@xxxxxxx> Cc: <gregory.haskins@xxxxxxxxx> Cc: <alacrityvm-devel@xxxxxxxxxxxxxxxxxxxxx> Cc: <mst@xxxxxxxxxx> Cc: <kvm@xxxxxxxxxxxxxxx> Cc: <linux-kernel@xxxxxxxxxxxxxxx> Cc: <netdev@xxxxxxxxxxxxxxx> Sent: 8/18/2009 6:29:08 AM Subject: Re: [PATCH v3 3/6] vbus: add a "vbus-proxy" bus model for On 08/18/2009 03:24 PM, Gregory Haskins wrote: > (Again on the top post) > > No, Avi, nothing has changed to my knowledge. I just saw that you and Michael were heading down the same path, so I thought I might interject that we've already covered that ground. > > As of right now, I am of the opinion that its not worth any change in the short term, and may be worth IOoHC in the long term (primarily so that mmios get a boost) > The primary issue with IOoHC is that while hypercalls are faster than emulated mmio, they're much slower than assigned mmio. So we have to distinguish between these two cases, which gets kinda icky. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
