Re: [Xen-devel] XSAVE/XRSTOR crash resurgence in 4.3

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 12.07.13 at 15:49, Ben Guthro <ben.guthro@xxxxxxxxx> wrote:
> On Fri, Jul 12, 2013 at 9:38 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>>> On 12.07.13 at 15:11, Ben Guthro <ben.guthro@xxxxxxxxx> wrote:
>>> The odd part is, that in this failing case - this machine does not
>>> seem to be printing these debug messages at all.
>>>
>>> Is this the only path this can go through for xsave, or are there others?
>>
>> For xsave that's the only one. On systems not supporting xsave, it
>> would go through the (not instrumented) fxsave path instead. But
>> if we know that the system uses xsave, yet none of the messages
>> gets printed, that's also a valuable piece of information.
> 
> It at least has the xsave cpuid leaf in /proc/cpuinfo
> 
> Is there something else in the Xen log I should look for to know that
> Xen is actually using xsave?

        printk("%s: using cntxt_size: %#x and states: %#"PRIx64"\n",
            __func__, xsave_cntxt_size, xfeature_mask);

(in xstate_init()).

Jan


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