On 05/20/2010 01:27 AM, Michael S. Tsirkin wrote:
On Wed, May 19, 2010 at 08:04:51PM +0300, Avi Kivity wrote:
On 05/18/2010 04:19 AM, Michael S. Tsirkin wrote:
With PUBLISH_USED_IDX, guest tells us which used entries
it has consumed. This can be used to reduce the number
of
On 05/18/2010 04:19 AM, Michael S. Tsirkin wrote:
With PUBLISH_USED_IDX, guest tells us which used entries
it has consumed. This can be used to reduce the number
of interrupts: after we write a used entry, if the guest has not yet
consumed the previous entry, or if the guest has already consumed
On Wed, May 19, 2010 at 08:04:51PM +0300, Avi Kivity wrote:
On 05/18/2010 04:19 AM, Michael S. Tsirkin wrote:
With PUBLISH_USED_IDX, guest tells us which used entries
it has consumed. This can be used to reduce the number
of interrupts: after we write a used entry, if the guest has not yet
On Thu, 20 May 2010 07:57:18 am Michael S. Tsirkin wrote:
On Wed, May 19, 2010 at 08:04:51PM +0300, Avi Kivity wrote:
On 05/18/2010 04:19 AM, Michael S. Tsirkin wrote:
With PUBLISH_USED_IDX, guest tells us which used entries
it has consumed. This can be used to reduce the number
of
With PUBLISH_USED_IDX, guest tells us which used entries
it has consumed. This can be used to reduce the number
of interrupts: after we write a used entry, if the guest has not yet
consumed the previous entry, or if the guest has already consumed the
new entry, we do not need to interrupt.
This
From: Michael S. Tsirkin m...@redhat.com
Date: Tue, 18 May 2010 04:19:31 +0300
With PUBLISH_USED_IDX, guest tells us which used entries
it has consumed. This can be used to reduce the number
of interrupts: after we write a used entry, if the guest has not yet
consumed the previous entry, or