On 12/06/2019 20:58, Christopher Clark wrote:
> On Wed, Jun 12, 2019 at 5:35 AM Nicholas Tsirakis
> wrote:
>> When a message is requeue'd in Xen's internal queue, the queue
>> entry contains the length of the message so that Xen knows to
>> send a VIRQ to the respective domain when enough space fr
On Wed, Jun 12, 2019 at 5:35 AM Nicholas Tsirakis
wrote:
>
> When a message is requeue'd in Xen's internal queue, the queue
> entry contains the length of the message so that Xen knows to
> send a VIRQ to the respective domain when enough space frees up
> in the ring. Due to a small bug, however,
On Wed, Jun 12, 2019 at 8:47 AM Andrew Cooper wrote:
>
> On 12/06/2019 13:34, Nicholas Tsirakis wrote:
> > When a message is requeue'd in Xen's internal queue, the queue
> > entry contains the length of the message so that Xen knows to
> > send a VIRQ to the respective domain when enough space fre
On 12/06/2019 13:34, Nicholas Tsirakis wrote:
> When a message is requeue'd in Xen's internal queue, the queue
> entry contains the length of the message so that Xen knows to
> send a VIRQ to the respective domain when enough space frees up
> in the ring. Due to a small bug, however, Xen doesn't po
When a message is requeue'd in Xen's internal queue, the queue
entry contains the length of the message so that Xen knows to
send a VIRQ to the respective domain when enough space frees up
in the ring. Due to a small bug, however, Xen doesn't populate
the length of the msg if a given write fails, s
