From mboxrd@z Thu Jan  1 00:00:00 1970
From: Harmandeep Kaur <write.harmandeep@gmail.com>
Subject: Re: Error booting Xen
Date: Thu, 21 Jan 2016 20:54:28 +0530
Message-ID: <CAPtdW16wr0=rgf69gGn8ts6hgRtn2n2=UQcuj2TZywFi255R4Q@mail.gmail.com>
References: <CAPtdW14j0TgsHQaCw5+Z-yxZrZzSozgt8bHjLEaNemkDQkgaHw@mail.gmail.com>
	<569D2A49.1090409@citrix.com>
	<1453141749.11427.92.camel@citrix.com>
	<569E4A0102000078000C8917@prv-mh.provo.novell.com>
	<1453215095.11427.144.camel@citrix.com>
	<569E5118.4030704@citrix.com>
	<CAPtdW14duUx7T6D26sUnZ0m1Cb8gW=p_oL4YAZ3rZbNhU2MbXQ@mail.gmail.com>
	<569E76B102000078000C8C14@prv-mh.provo.novell.com>
	<569E6C36.3070402@citrix.com>
	<1453223282.11427.149.camel@citrix.com>
	<CAPtdW14HFrHN8ywa-HwibVkQtfUs1YXGUKmbEiMS5xgY4cTohw@mail.gmail.com>
	<569F6A2102000078000C8F20@prv-mh.provo.novell.com>
	<1453389242.3116.106.camel@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1453389242.3116.106.camel@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
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>
List-Id: xen-devel@lists.xenproject.org

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)
>