From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: Linux 3.11 and the future...
Date: Fri, 7 Jun 2013 13:03:52 -0400
Message-ID: <20130607170352.GA3730@phenom.dumpdata.com>
References: <20130605201909.GA17062@phenom.dumpdata.com>
	<51B058B102000078000DBCA3@nat28.tlf.novell.com>
	<20130606130710.GB20784@konrad-lan.dumpdata.com>
	<51B0A76502000078000DBE29@nat28.tlf.novell.com>
	<20130607135845.GG25649@phenom.dumpdata.com>
	<51B21BD802000078000DC42D@nat28.tlf.novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <51B21BD802000078000DC42D@nat28.tlf.novell.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: Jan Beulich <JBeulich@suse.com>
Cc: Benjamin.Guthro@citrix.com, andrew.cooper3@citrix.com, Daniel Kiper <daniel.kiper@oracle.com>, stefan.bader@canonical.com, xen-devel <xen-devel@lists.xen.org>, david.vrabel@citrix.com
List-Id: xen-devel@lists.xenproject.org

On Fri, Jun 07, 2013 at 04:43:52PM +0100, Jan Beulich wrote:
> >>> On 07.06.13 at 15:58, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > On Thu, Jun 06, 2013 at 02:14:45PM +0100, Jan Beulich wrote:
> >> Imo this is not a viable option - we shouldn't start peeking into the
> >> second module (which Linux uses as initrd, but which other OSes
> >> may use for other purposes) - so far this is just a binary blob to the
> >> hypervisor.
> >> 
> > 
> > I was under the impression that the code you introduced for microcode 
> > loading
> > was doing that exactly. Granted it would only peek if told to. Perhaps that
> > code can be expanded to scan the blob for cpio image of microcode in 
> > whatever it was told to look at?
> 
> No, this is a separate (usually third) grub module, containing just
> the raw microcode data (in the same format that otherwise would
> get passed down from Dom0 via hypercall).

Correct. What I was thinking would be beneficial is extend the code
such that if the user wishes - it could scan one of the grub modules
for a signature and if so, extract the relevant microcode from the
cpio image. Then apply it.

> 
> Jan
>