Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S936101AbcLOQyu convert rfc822-to-8bit (ORCPT <rfc822;w@1wt.eu>);
        Thu, 15 Dec 2016 11:54:50 -0500
Received: from prv-mh.provo.novell.com ([137.65.248.74]:36066 "EHLO
        prv-mh.provo.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752952AbcLOQys (ORCPT
        <rfc822;groupwise-linux-kernel@vger.kernel.org:5:1>);
        Thu, 15 Dec 2016 11:54:48 -0500
Message-Id: <5852D8A20200007800129CC6@prv-mh.provo.novell.com>
X-Mailer: Novell GroupWise Internet Agent 14.2.1 
Date: Thu, 15 Dec 2016 09:53:38 -0700
From: "Jan Beulich" <JBeulich@suse.com>
To: "Borislav Petkov" <bp@suse.de>
Cc: "xen-devel" <xen-devel@lists.xenproject.org>,
        "Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
        "Juergen Gross" <JGross@suse.com>,
        "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Can't boot as Xen dom0 due to commit fe055896
References: <73a4d64b-b139-6579-a560-92311641d6c7@suse.com>
 <20161215164635.thm7ruio2ddnxszw@pd.tnic>
In-Reply-To: <20161215164635.thm7ruio2ddnxszw@pd.tnic>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 439
Lines: 11

>>> On 15.12.16 at 17:46, <bp@suse.de> wrote:
> On Thu, Dec 15, 2016 at 05:12:04PM +0100, Juergen Gross wrote:
>> with today's kernel the system isn't coming up when booted as Xen dom0:
> 
> Remind me again pls, is dom0 even supposed to load microcode? Isn't the
> hypervisor supposed to apply microcode?

Yes, it's the hypervisor. Dom0 can at best hand the blob to it via
hypercall, but iirc upstream Linux doesn't make use of that.

Jan