From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Patch] continue_hypercall_on_cpu rework using tasklets
Date: Thu, 15 Apr 2010 10:29:21 +0200 [thread overview]
Message-ID: <4BC6CE61.1010505@ts.fujitsu.com> (raw)
In-Reply-To: <C7EC8922.11572%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 15/04/2010 08:57, "Juergen Gross" <juergen.gross@ts.fujitsu.com> wrote:
>
>>> What revision did you test? I put in some fixes as c/s 21173.
>> My highest c/s was 21167.
>> c/s 21173 is hanging, too (sorry for the delay, but I had to remove my cpupool
>> stuff due to the scheduler changes for credit2).
>
> Ah yes, just done a test myself (clearly my dom0 setup is not doing
> microcode updates) and I've now fixed it as c/s 21176. Thanks!
Great! Works for me, too.
>
>> Is a call of sync_vcpu_execstate() fro a tasklet really allowed? I don't
>> think the ASSERTs in __sync_lazy_execstate() are all fulfilled in this case.
>
> Better hope so or e.g.,
> acpi_enter_sleep
> ->continue_hypercall_on_cpu(enter_state_helper)
> ->enter_state
> ->freeze_domains
> ->domain_pause
> ->vcpu_sleep_sync
> ->sync_vcpu_execstate
> Also wouldn't work.
>
> There is only one ASSERT in __sync_lazy_execstate, and it's safe for this
> case. Bear in mind that our softirqs always run in the context of whatever
> domain happens to be running on that cpu currently -- they don't have their
> own proper vcpu context.
I don't see how it should be guaranteed that the current vcpu MUST be an idle
one...
>
> By the by, your original attempt at synchronisation (spin on return value in
> regs changing) was risky as it could be unbounded time before the vcpu
> registers get copied out of the original cpu's stack. Especially during
> early dom0 boot, when the system is very idle.
Indeed. I realized my version had another flaw in case of nested calls of
c_h_o_c: if one call would return a non-zero value and issue another call
of c_h_o_c, the tasklet would hang for ever...
Your version is cleaner.
Juergen
--
Juergen Gross Principal Developer Operating Systems
TSP 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:[~2010-04-15 8:29 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 13:19 [Patch] continue_hypercall_on_cpu rework using tasklets Juergen Gross
2010-04-13 13:40 ` Jan Beulich
2010-04-13 13:49 ` Juergen Gross
2010-04-13 15:08 ` Keir Fraser
2010-04-14 6:54 ` Juergen Gross
2010-04-13 14:41 ` Keir Fraser
2010-04-14 4:26 ` Juergen Gross
2010-04-14 6:46 ` Keir Fraser
2010-04-14 6:58 ` Juergen Gross
2010-04-14 7:15 ` Keir Fraser
2010-04-14 7:25 ` Juergen Gross
2010-04-14 7:35 ` Keir Fraser
2010-04-14 8:04 ` Juergen Gross
2010-04-14 10:30 ` Keir Fraser
2010-04-15 6:31 ` Juergen Gross
2010-04-15 6:39 ` Keir Fraser
2010-04-15 7:57 ` Juergen Gross
2010-04-15 8:13 ` Keir Fraser
2010-04-15 8:22 ` Keir Fraser
2010-04-15 9:59 ` Jiang, Yunhong
2010-04-15 11:06 ` Keir Fraser
2010-04-15 11:22 ` Keir Fraser
2010-04-16 9:20 ` Yu, Ke
2010-04-16 17:51 ` Keir Fraser
2010-04-19 10:50 ` Keir Fraser
2010-04-19 12:04 ` Yu, Ke
2010-04-20 5:35 ` Wei, Gang
2010-04-20 12:51 ` Keir Fraser
2010-04-20 14:10 ` Wei, Gang
2010-04-21 6:47 ` Wei, Gang
2010-04-16 6:42 ` Jiang, Yunhong
2010-04-16 6:55 ` Juergen Gross
2010-04-16 8:30 ` Jiang, Yunhong
2010-04-16 7:13 ` Keir Fraser
2010-04-16 8:16 ` Jiang, Yunhong
2010-04-16 17:57 ` Keir Fraser
2010-04-19 5:53 ` Jiang, Yunhong
2010-04-19 6:48 ` Keir Fraser
2010-04-16 6:45 ` Jiang, Yunhong
2010-04-15 8:29 ` Juergen Gross [this message]
2010-04-15 9:08 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2009-12-30 13:46 Juergen Gross
2009-12-30 13:57 ` Keir Fraser
2009-12-30 13:59 ` 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=4BC6CE61.1010505@ts.fujitsu.com \
--to=juergen.gross@ts.fujitsu.com \
--cc=keir.fraser@eu.citrix.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 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.