Re: [Xen-devel] Request for input: Extended event channel support

[George Dunlap <George.Dunlap@xxxxxxxxxxxxx>]

On Thu, Mar 28, 2013 at 1:56 AM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
>> So the implementation was tweaked, so that scans don't start at 0, but
>> continue where the last event left off.  This made it so that earlier
>> events were not prioritized and removed the starvation issue, but at
>> the cost of removing all event priorities.  Certain events, like the
>> timer event, are special-cased to be always checked, but this is
>> rather a bit of a hack and not very scalable or flexible.
>
> Hm, I actually think that is not in the upstream kernel at all. That
> would explain why on very heavily busy guest the hrtimer: interrupt
> took XXxXXXXxx ns is printed.
>
> Is this patch somewhere available?

I think it was David who told me this -- maybe there is such a hack on
the "classic xen" kernel we're using in XenServer?

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel