From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: xen-devel@lists.xensource.com, Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] Avoid panic when adjusting sedf parameters
Date: Thu, 17 Nov 2011 15:04:57 +0100 [thread overview]
Message-ID: <4EC51489.4090609@ts.fujitsu.com> (raw)
In-Reply-To: <CAEAC230.25135%keir.xen@gmail.com>
On 11/17/2011 02:52 PM, Keir Fraser wrote:
> On 17/11/2011 13:30, "Jan Beulich"<JBeulich@suse.com> wrote:
>
>> which would now associate the else with the wrong (inner) if. One
>> possible solution that comes to mind would be
>>
>> #define for_each_domain_in_cpupool(_d,_c) \
>> for_each_domain_in_cpupool (_d) \
>> if ((_d)->cpupool != (_c)) \
>> continue; \
>> else
>>
>> but I think I had seen a more clever solution to this problem, but cannot
>> remember/locate it right now.
> Given the gcc ({}) construction, you could do a double-loop:
> for ( (_d) = rcu_dereference(domain_list); \
> (_d) != NULL; \
> ({ while ((_d) = rcu_dereference((_d)->next_in_list != NULL)
> if ((_d)->cpupool == (_c)) break;
> (_d); }) )
>
> A bit ugly. ;-) And I still worry about cpupool locking...
What about:
static inline struct domain *next_domain_in_cpupool(
struct domain *d, struct cpupool *c)
{
for (d = rcu_dereference(d->next_in_list); d && d->cpupool != c;
d = rcu_dereference(d->next_in_list));
return d;
}
#define for_each_domain_in_cpupool(_d,_c) \
for ( (_d) = rcu_dereference(domain_list); \
(_d) != NULL; \
(_d) = next_domain_in_cpupool((_d), (_c)))
Juergen
--
Juergen Gross Principal Developer Operating Systems
PDG ES&S SWE OS6 Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28 Internet: ts.fujitsu.com
D-80807 Muenchen Company details: ts.fujitsu.com/imprint.html
next prev parent reply other threads:[~2011-11-17 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 13:03 [PATCH] Avoid panic when adjusting sedf parameters Juergen Gross
2011-11-17 13:30 ` Jan Beulich
2011-11-17 13:48 ` Keir Fraser
2011-11-17 14:02 ` Juergen Gross
2011-11-17 13:52 ` Keir Fraser
2011-11-17 14:04 ` Juergen Gross [this message]
2011-11-17 14:32 ` Jan Beulich
2011-11-17 14:41 ` Juergen Gross
2011-11-17 14:29 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2011-11-17 14:37 Juergen Gross
2011-11-17 12:33 Juergen Gross
2011-11-17 12:43 ` George Dunlap
2011-11-17 13:07 ` Juergen Gross
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=4EC51489.4090609@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=JBeulich@suse.com \
--cc=keir.xen@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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).