From: Harmandeep Kaur <write.harmandeep@gmail.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xen.org, Jan Beulich <JBeulich@suse.com>,
Shuai Ruan <shuai.ruan@linux.intel.com>
Subject: Re: Error booting Xen
Date: Thu, 21 Jan 2016 20:54:28 +0530 [thread overview]
Message-ID: <CAPtdW16wr0=rgf69gGn8ts6hgRtn2n2=UQcuj2TZywFi255R4Q@mail.gmail.com> (raw)
In-Reply-To: <1453389242.3116.106.camel@citrix.com>
On Thu, Jan 21, 2016 at 8:44 PM, Dario Faggioli
<dario.faggioli@citrix.com> wrote:
> On Wed, 2016-01-20 at 03:06 -0700, Jan Beulich wrote:
>> > > > On 19.01.16 at 20:55, <write.harmandeep@gmail.com> wrote:
>> >
>> > $ 'addr2line -e xen-syms ffff82d0801c1cce' returns
>> > 'xen/xen/arch/x86/xstate.c:387' which again points to
>> > xsave. Also, adding 'xsave=0' makes it boot just fine.
>>
>> Ah, I think I see the issue: We're zeroing the entire save area in
>> the fixup code, which will make XRSTORS fault unconditionally.
>> Shuai, would you please look into possible ways of fixing this?
>> Just setting the compressed flag may not be enough, and falling
>> back to plain XRSTOR doesn't seem to be an option either - I'm in
>> particular worried that the current model of zeroing everything
>> is bogus with the growing number of different components which
>> get loaded here.
>>
>> But of course another question then is why the XRSTORS faults
>> in the first place. I guess we'll need a debugging patch to dump
>> the full state to understand that.
>>
> If someone can produce and send such patch, I'm sure Harmandeep will be
> happy to give it a try on her hardware.
>
Yes, sure. I will be more than happy to do this :)
Thank you Dario.
Regards,
Harman
> Thanks and Regards,
> Dario
> --
> <<This happens because I choose it to happen!>> (Raistlin Majere)
> -----------------------------------------------------------------
> Dario Faggioli, Ph.D, http://about.me/dario.faggioli
> Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
>
next prev parent reply other threads:[~2016-01-21 15:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 18:03 Error booting Xen Harmandeep Kaur
2016-01-18 18:09 ` Andrew Cooper
2016-01-18 18:29 ` Dario Faggioli
2016-01-19 13:36 ` Jan Beulich
2016-01-19 14:51 ` Dario Faggioli
2016-01-19 15:07 ` Andrew Cooper
2016-01-19 16:27 ` Harmandeep Kaur
2016-01-19 16:47 ` Jan Beulich
2016-01-19 17:02 ` Andrew Cooper
2016-01-19 17:08 ` Dario Faggioli
2016-01-19 17:09 ` Andrew Cooper
2016-01-19 19:55 ` Harmandeep Kaur
2016-01-20 10:06 ` Jan Beulich
2016-01-21 15:14 ` Dario Faggioli
2016-01-21 15:24 ` Harmandeep Kaur [this message]
2016-01-25 13:42 ` Jan Beulich
2016-01-26 11:58 ` Dario Faggioli
2016-01-26 12:51 ` Harmandeep Kaur
2016-01-26 13:13 ` Harmandeep Kaur
2016-01-26 13:23 ` Jan Beulich
2016-01-26 17:01 ` Harmandeep Kaur
2016-01-26 17:23 ` Jan Beulich
2016-01-26 18:02 ` Harmandeep Kaur
2016-01-26 18:28 ` Dario Faggioli
2016-01-26 18:36 ` Harmandeep Kaur
2016-01-27 8:24 ` Jan Beulich
2016-01-27 13:12 ` Jan Beulich
2016-01-27 13:28 ` Harmandeep Kaur
2016-01-27 14:28 ` Jan Beulich
2016-01-28 19:17 ` Harmandeep Kaur
2016-01-29 10:13 ` Jan Beulich
2016-02-03 8:23 ` Dario Faggioli
2016-02-03 11:35 ` Harmandeep Kaur
2016-02-03 12:49 ` Jan Beulich
2016-02-03 12:55 ` Dario Faggioli
2016-02-03 13:10 ` Andrew Cooper
2016-02-03 13:17 ` Dario Faggioli
2016-02-03 16:57 ` Konrad Rzeszutek Wilk
2016-02-03 13:40 ` Harmandeep Kaur
2016-02-03 14:18 ` Jan Beulich
2016-01-26 13:22 ` Jan Beulich
2016-02-02 4:43 ` Shuai Ruan
[not found] ` <20160202044349.GA3036@shuai.ruan@linux.intel.com>
2016-02-02 10:39 ` Andrew Cooper
2016-02-03 0:56 ` Shuai Ruan
2016-02-03 7:56 ` Shuai Ruan
2016-01-19 14:07 ` Harmandeep Kaur
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='CAPtdW16wr0=rgf69gGn8ts6hgRtn2n2=UQcuj2TZywFi255R4Q@mail.gmail.com' \
--to=write.harmandeep@gmail.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=shuai.ruan@linux.intel.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).