From: George Dunlap <george.dunlap@citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>,
Julien Grall <julien.grall@arm.com>
Cc: Varun.Swara@arm.com, Xen Devel <xen-devel@lists.xen.org>,
Steve Capper <Steve.Capper@arm.com>
Subject: Re: xen/arm: Assertion 'timer->status >= TIMER_STATUS_inactive' failed at timer.c:279
Date: Wed, 27 Apr 2016 15:29:40 +0100 [thread overview]
Message-ID: <5720CCD4.5010501@citrix.com> (raw)
In-Reply-To: <1461765951.3525.140.camel@citrix.com>
On 27/04/16 15:05, Dario Faggioli wrote:
> On Wed, 2016-04-27 at 14:43 +0100, George Dunlap wrote:
>> On 26/04/16 18:49, Dario Faggioli wrote:
>>>
>>> Let me know, and I'll resubmit the patch properly (together with
>>> another bugfix I have in my queue).
>> Yeah, assuming the description in your changeset is accurate, this
>> seems
>> like the right approach.
>>
> Ok, thanks for having a look, I'll submit a proper series.
>
>> The main thing to add here I think is that we need to document what
>> different circumstances under which the various functions may be
>> called
>> -- for instance, in credit1 free_pdata(), it seems to expect that spc
>> may == null at some point. Future schedulers need to know the
>> circumstances under which this might happen so they can DTRT.
>>
> I saw that too (many times). And in fact, I'm not sure whether that can
> actually happen or not, but I certainly can look at this.
>
> And if by "document what different circumstances under which the
> various functions may be called" you mean adding comments to that
> effect somewhere, I'm up for that (I just need to figure out where it
> would be best to put such comments).
Yes, comments is what I meant. At very least it should be documented
that alloc/free might be called without init/deinit netsed inside. If
you're also not sure how free_pdata() could be called with spc == null,
then I think we can probably punt an investigation into that until later
as well.
>> It might be nice at some point to have the alloc / free / init /
>> deinit
>> functions in credit1 ordered in a rational way so that they could be
>> understood by glancing at them, rather than having to jump around,
>> but
>> that's probably a nice-to-have clean-up for another time. :-)
>>
> When you say "ordered" you mean the order in which they appear in the
> source file? If yes, I agree, but no, I'm not doing that right now (but
> I can queue this for when 4.8 opens).
Sorry, yes I meant ordered in the source file.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-27 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 14:25 xen/arm: Assertion 'timer->status >= TIMER_STATUS_inactive' failed at timer.c:279 Julien Grall
2016-04-26 17:49 ` Dario Faggioli
2016-04-26 18:05 ` Julien Grall
2016-04-27 13:43 ` George Dunlap
2016-04-27 14:05 ` Dario Faggioli
2016-04-27 14:29 ` George Dunlap [this message]
2016-05-03 13:03 ` Julien Grall
2016-05-03 13:20 ` George Dunlap
2016-05-03 13:22 ` Julien Grall
2016-05-03 13:23 ` Wei Liu
2016-05-03 21:52 ` Dario Faggioli
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=5720CCD4.5010501@citrix.com \
--to=george.dunlap@citrix.com \
--cc=Steve.Capper@arm.com \
--cc=Varun.Swara@arm.com \
--cc=dario.faggioli@citrix.com \
--cc=julien.grall@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).