All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <ijc@hellion.org.uk>
Cc: maximilian attems <maks@stro.at>,
	debian-kernel@lists.debian.org,
	David Vrabel <david.vrabel@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Current state of Xen microcode (Was: Re: uploading 3.16~rc5-1~exp1)
Date: Tue, 15 Jul 2014 10:59:34 -0400	[thread overview]
Message-ID: <20140715145934.GM3403@laptop.dumpdata.com> (raw)
In-Reply-To: <1405414412.1389.5.camel@kazak.uk.xensource.com>

On Tue, Jul 15, 2014 at 09:53:32AM +0100, Ian Campbell wrote:
> Adding xen-devel and some of the Linux maints,
> 
> On Mon, 2014-07-14 at 23:22 +0200, maximilian attems wrote:
> > I will upload tomorrow Tuesday around 22h00 UT to experimental.
> > 
> > There are two TODOS concerning the not yet forwarded Debian patches:
> > - cgroups
> > - xen microcode
> > 
> > 
> > I consider both not a blocker, but would be happy if Xen guys could
> > have a look for what is needed.
> 
> The xen microcode patches which maks is referring to are these:
> http://anonscm.debian.org/viewvc/kernel/dists/trunk/linux/debian/patches/features/all/xen/
> which are a forward port of Jeremy's old microcode_xen.ko driver.

They are also at my branch
http://git.kernel.org/cgit/linux/kernel/git/konrad/xen.git/log/?h=stable/misc

Hm, I should rebase them at some point.
> 
> I've not been keeping up on Xen x86 microcode stuff these days but I
> think we don't need this any more with modern Xen since we can parse the
> microcode blob off the front of the initrd, is that right?

Right. And best of it, the support for that is in dracut so
it automatically can happen (thought you still need to add
'ucode=scan' in the /etc/default/grub.cfg in the GRUB_CMDLINE_XEN
parameter) and also in /etc/dracut.conf add 'early_microcode=yes'.

> 
> (this is predicated on Xen 4.4 hitting unstable, which is underway)

unstable == Debian unstable?

> 
> Thanks,
> Ian.
> 

  reply	other threads:[~2014-07-15 14:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140714212213.GC18075@stro.at>
2014-07-15  8:53 ` Current state of Xen microcode (Was: Re: uploading 3.16~rc5-1~exp1) Ian Campbell
2014-07-15 14:59   ` Konrad Rzeszutek Wilk [this message]
2014-07-15 15:06     ` Ian Campbell
     [not found]     ` <1405436760.28874.1.camel@kazak.uk.xensource.com>
2014-07-15 15:35       ` Konrad Rzeszutek Wilk
2014-07-15 15:43         ` Ian Campbell
2014-07-15 17:53         ` Ben Hutchings
     [not found]         ` <1405446784.2453.49.camel@deadeye.wl.decadent.org.uk>
2014-07-15 18:08           ` Konrad Rzeszutek Wilk
2014-07-23 14:59     ` Jan Beulich
2014-08-04 14:07       ` Konrad Rzeszutek Wilk
2014-08-04 14:40         ` Jan Beulich
2014-08-04 15:02           ` Konrad Rzeszutek Wilk

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=20140715145934.GM3403@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=debian-kernel@lists.debian.org \
    --cc=ijc@hellion.org.uk \
    --cc=maks@stro.at \
    --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.