From: Jim Fehlig <jfehlig@suse.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: libvirt libxl timer handling issue
Date: Fri, 31 Jan 2014 08:47:36 -0700 [thread overview]
Message-ID: <52EBC598.6030600@suse.com> (raw)
In-Reply-To: <21227.48873.879761.827214@mariner.uk.xensource.com>
Ian Jackson wrote:
> Ian Jackson writes ("Re: libvirt libxl timer handling issue"):
>
>> Jim Fehlig writes ("libvirt libxl timer handling issue"):
>>
>>> On the bright side, I seem to have the fd event handling issues sorted out.
>>>
>> Good, I guess. Let me look at your crash stacktrace and the libxl
>> code in more detail...
>>
>
> I think this is due to libxl_event.c not clearing the ->func member of
> its timeout structs when the timeout occurs. TBH it's surprising that
> this hasn't caused more trouble and I haven't been able to test this
> so I'm not sure.
>
> But please take a look at
> git://xenbits.xen.org/people/iwj/xen.git#wip.timeout-func0
>
> The top two patches there are new; the rest is my fork fixup branch.
> Note once again that I have compiled but NOT EXECUTED these two
> patches. But since I'm about to be out of touch travelling and then
> at FOSDEM I thought I'd send this to you right away.
>
Ok, thanks. I'll give this a try in a bit.
> Sorry if this too turns out to be my fault...
>
Well, I should spend some time becoming familiar with this part of libxl
so I can help fix issues too, instead of whining about them :).
Enjoy FOSDEM.
Regards,
Jim
next prev parent reply other threads:[~2014-01-31 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 6:01 libvirt libxl timer handling issue Jim Fehlig
2014-01-31 12:17 ` Ian Jackson
2014-01-31 15:19 ` Ian Jackson
2014-01-31 15:47 ` Jim Fehlig [this message]
2014-02-03 14:45 ` Ian Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52EBC598.6030600@suse.com \
--to=jfehlig@suse.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.