On Nov 28, 2014, at 00:50, Jan Beulich <jbeul...@suse.com> wrote:

>>>> On 28.11.14 at 09:24, <sfl...@ihonk.com> wrote:
>>> And with 6 errata
>>> documented it's not all that unlikely that there's a 7th one with
>>> MONITOR/MWAIT behavior. The commit you bisected to (and
>>> which you had verified to be the culprit by just forcing
>>> arch_skip_send_event_check() to always return false) could be
>>> reasonably assumed to be broken only when MWAIT use for all
>>> C states didn't work.
>> 
>> Now I did get a hang with max_cstate=3 and mwait-idle=0.
> 
> According to the data you provided earlier, max_cstate=3 is
> identical to not using that option at all when you also use
> mwait-idle=0. It would make a difference only when not using
> that latter option (and I specifically pointed this out in earlier
> replies).
> 

Apologies for asking you to repeat yourself. Most of this stuff is over my head 
-- the only time I was this far down the rabbit hole was on an 8051.  Thanks 
for your patience. :-)

Steve


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

Reply via email to