From: John Doe <securef33d@gmail.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Jan Beulich <JBeulich@suse.com>
Cc: Ingo Molnar <mingo@kernel.org>,
x86@kernel.org, xen-devel@lists.xen.org,
linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] PROBLEM: kernel panic xsave_init
Date: Wed, 21 Oct 2015 02:17:00 +0200 [thread overview]
Message-ID: <5626D97C.1060609@gmail.com> (raw)
In-Reply-To: <56264F5D.9000104@oracle.com>
On 20/10/2015 16:27, Boris Ostrovsky wrote:
> On 10/20/2015 09:43 AM, Jan Beulich wrote:
>>>>> On 20.10.15 at 15:22, <boris.ostrovsky@oracle.com> wrote:
>>> The reason I think its this commit is that RAX, RDX and RCX look very
>>> much like arguments to xsetbv (which xstate_enable_boot_cpu() executes)
>>> and RAX value is 0x1f, which has two new bits that this commit defined.
>> That would be the two MPX related bits, yet us (luckily) white listing
>> leaf 7 in pv_cpuid(), it is quite easy to validate that we don't expose
>> this feature to PV(H) guests.
>
> Oh, so something like
>
> cpuid=['0x7:ebx=xxxxxxxxxxxxxxxxx0xxxxxxxxxxxxxx']
>
> (bit 14 as zero) for John to try then.
>
>
> -boris
>
>> Sadly the story is different for HVM
>> guests (where the leaf handling uses black listing), but the register
>> dump here clearly points to a PV guest (or Dom0).
>>
>> Jan
>>
>
Jan the dump is taken from serial connection to Dom0, it does crash
during boot.
I just tried with xen 4.6.0 and it booted properly without xsave=0.
Running gdb against /proc/kcore, with a x/10x 0xffffffff81d58fad i just
get null bytes, with both xen4.4.3 (xsave=0) and 4.6.0.
Tomorrow i will send you the gdb output and i will try to run it during
the boot process.
J.
next prev parent reply other threads:[~2015-10-21 0:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <562430E6.6010205@gmail.com>
[not found] ` <20151019075618.GA22488@gmail.com>
2015-10-19 10:16 ` PROBLEM: kernel panic xsave_init John Doe
2015-10-19 16:25 ` Boris Ostrovsky
2015-10-19 16:25 ` [Xen-devel] " Boris Ostrovsky
2015-10-20 9:51 ` Jan Beulich
2015-10-20 12:11 ` John Doe
2015-10-20 13:22 ` Boris Ostrovsky
2015-10-20 13:43 ` Jan Beulich
2015-10-20 13:43 ` [Xen-devel] " Jan Beulich
2015-10-20 14:27 ` Boris Ostrovsky
2015-10-20 14:27 ` [Xen-devel] " Boris Ostrovsky
2015-10-20 14:41 ` Jan Beulich
2015-10-20 14:41 ` Jan Beulich
2015-10-21 0:17 ` John Doe
2015-10-21 0:17 ` John Doe [this message]
2015-10-20 13:22 ` Boris Ostrovsky
2015-10-20 12:11 ` John Doe
2015-10-20 9:51 ` Jan Beulich
2015-10-19 10:16 ` John Doe
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=5626D97C.1060609@gmail.com \
--to=securef33d@gmail.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.org \
--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 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.