Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: <bp@suse.de>
Cc: <konrad.wilk@oracle.com>, <x86@kernel.org>,
	<gregkh@linuxfoundation.org>, <david.vrabel@citrix.com>,
	<stable@vger.kernel.org>, <rshendershot@mchsi.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3.17 100/141] x86, microcode: Fix accessing dis_ucode_ldr on 32-bit
Date: Wed, 26 Nov 2014 19:13:02 -0800 (PST)	[thread overview]
Message-ID: <b4d424e6-81b2-4b21-ab2f-3d403a455f57@default> (raw)


----- bp@suse.de wrote:

> On Wed, Nov 26, 2014 at 07:39:26AM -0500, boris ostrovsky wrote:
> > https://lkml.org/lkml/2014/11/25/973 is all I have right now.
> 
> Ok, so the Code: section from this splat says:
> 
>   25:   55                      push   %ebp
>   26:   89 e5                   mov    %esp,%ebp
>   28:   83 ec 08                sub    $0x8,%esp
>   2b:*  80 3d c0 ee 97 01 00    cmpb   $0x0,0x197eec0           <--
> trapping instruction
>   32:   89 1c 24                mov    %ebx,(%esp)
>   35:   89 74 24 04             mov    %esi,0x4(%esp)
>   39:   74 12                   je     0x4d
>   3b:   8b 1c 24                mov    (%esp),%ebx
>   3e:   8b                      .byte 0x8b
>   3f:   74                      .byte 0x74
> 
> which I can correlate to the dis_ucode_ldr test here:
> 
>         .loc 1 134 0
>         .loc 1 137 0
>         cmpb    $0, dis_ucode_ldr+1073741824    #, *_11
>         je      .L46    #,
> 
> 
> so we must be faulting when accessing that dis_ucode_ldr thing. But
> you
> said that accessing it through its virtual address doesn't fix the
> issue
> either. Which is very very strange...


I was confusing you: accessing dis_ucode_ldr by virtual address does work on PV. But we then fail later, in load_ucode_intel_ap(), because it also tries to use __pa_nodebug() which can't be used by PV.

So if accessing dis_ucode_ldr by virtual address is acceptable (although I don't think it is?) then we can stick dis_ucode_ldr=1 into xen_start_kernel() and then things look OK.

A better solution may be to replace cpuid in x86_guest() with 'return pv_info.paravirt_enabled' (or paravirt_enabled(), I guess). I gave it a quick spin (32-bit only) and it seems to work. I'll see how my overnight tests behave.

-boris


             reply	other threads:[~2014-11-27  3:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  3:13 Boris Ostrovsky [this message]
2014-11-27  9:12 ` [PATCH 3.17 100/141] x86, microcode: Fix accessing dis_ucode_ldr on 32-bit Borislav Petkov
2014-11-27 16:21   ` Konrad Rzeszutek Wilk
2014-11-27 16:36     ` Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2014-11-27 23:33 Boris Ostrovsky
2014-11-27 17:14 Boris Ostrovsky
2014-11-27 17:20 ` Borislav Petkov
2014-11-19 20:50 [PATCH 3.17 000/141] 3.17.4-stable review Greg Kroah-Hartman
2014-11-19 20:52 ` [PATCH 3.17 100/141] x86, microcode: Fix accessing dis_ucode_ldr on 32-bit Greg Kroah-Hartman
2014-11-25 18:12   ` Boris Ostrovsky
2014-11-25 18:24     ` Borislav Petkov
2014-11-25 18:43       ` Boris Ostrovsky
2014-11-25 18:43         ` Borislav Petkov
2014-11-25 18:55           ` Boris Ostrovsky
2014-11-25 19:03             ` Borislav Petkov
2014-11-25 19:23               ` Boris Ostrovsky
2014-11-25 19:08             ` Borislav Petkov
2014-11-25 19:28               ` Boris Ostrovsky
2014-11-25 20:26                 ` Borislav Petkov
2014-11-25 20:36                   ` Konrad Rzeszutek Wilk
2014-11-25 21:17                     ` Borislav Petkov
2014-11-25 21:59                       ` Boris Ostrovsky
2014-11-25 22:18                         ` Borislav Petkov
2014-11-26  5:00                           ` Boris Ostrovsky
2014-11-26 10:55                             ` Borislav Petkov
2014-11-26 12:39                               ` boris ostrovsky
2014-11-26 14:44                                 ` Borislav Petkov
2014-11-25 18:45     ` Greg Kroah-Hartman
2014-11-25 18:47       ` Borislav Petkov
2014-11-25 18:50       ` Boris Ostrovsky

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=b4d424e6-81b2-4b21-ab2f-3d403a455f57@default \
    --to=boris.ostrovsky@oracle.com \
    --cc=bp@suse.de \
    --cc=david.vrabel@citrix.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rshendershot@mchsi.com \
    --cc=stable@vger.kernel.org \
    --cc=x86@kernel.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