From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
daniel.kiper@oracle.com, david.vrabel@citrix.com,
Yang Z Zhang <yang.z.zhang@intel.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
boris.ostrovsky@oracle.com
Subject: Re: How many patches are missing in upstream Linux?
Date: Tue, 11 Mar 2014 13:38:28 -0400 [thread overview]
Message-ID: <20140311173828.GE14684@phenom.dumpdata.com> (raw)
In-Reply-To: <531F44BA0200007800122EE0@nat28.tlf.novell.com>
On Tue, Mar 11, 2014 at 04:15:38PM +0000, Jan Beulich wrote:
> >>> On 11.03.14 at 16:04, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:
> > On Mon, Mar 10, 2014 at 01:55:57PM -0700, Jeremy Fitzhardinge wrote:
> >>
> >> On 03/06/2014 11:26 AM, Konrad Rzeszutek Wilk wrote:
> >> > Being worked on are:
> >> > - EFI (Daniel Kiper, CC-ed)
> >>
> >> This has been a blocker for me. My new laptop is EFI booting, so I
> >> haven't been running Xen on it for the last few months. I don't have
> >> much time for deep work on it, but I'm happy to be a test subject.
> >>
> >> > - perf (Boris Ostrovsky, CC-ed).
> >> > - user mode accessible PV clock (Boris or me)
> >> I did have some work on this, but I don't remember how far it got. I
> >> think it stumbled on having a mechanism to allow usermode to detect it
> >> had switched physical cpus. Is this a continuation of my patches or a
> >> new attempt?
> >>
> >> > The maintainer is being <insert your own opinion here>:
> >> > - runtime microcode. What I had been told was to use the 'early
> >> > microcode' mechanism - which is now implemented and Xen can also scan
> >> > the initramfs to extract the microcode payload and apply it.
> >>
> >> I've never got that to work, but ucode=-1 with a microcode.dat multiboot
> >> modules works pretty well.
> >
> > Odd. It should be fairly easy with the newest version of dracut. Just
> > add this in your /etc/dracut.conf
> >
> > early_microcode="yes"
> >
> > and obviously in your grub.cfg (/etc/default/grub) add on the Xen command
> > line
> > GRUB_CMDLINE_XEN="scan=ucode"
>
> The other way around I think: "ucode=scan".
Right! Thanks for spotting that.
>
> Jan
>
next prev parent reply other threads:[~2014-03-11 17:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 5:21 How many patches are missing in upstream Linux? Zhang, Yang Z
2014-03-06 10:38 ` Jan Beulich
2014-03-06 13:47 ` Fabio Fantoni
2014-03-06 19:26 ` Konrad Rzeszutek Wilk
2014-03-06 19:36 ` David Vrabel
2014-03-06 19:39 ` Konrad Rzeszutek Wilk
2014-03-07 1:35 ` Zhang, Yang Z
2014-03-07 1:49 ` Zhang, Yang Z
2014-03-07 9:16 ` Jan Beulich
2014-03-10 20:55 ` Jeremy Fitzhardinge
2014-03-11 15:04 ` Konrad Rzeszutek Wilk
2014-03-11 16:15 ` Jan Beulich
2014-03-11 17:38 ` Konrad Rzeszutek Wilk [this message]
2014-03-11 17:38 ` Atom2
2014-03-11 17:53 ` Konrad Rzeszutek Wilk
2014-03-11 18:35 ` Atom2
2014-03-11 20:33 ` Konrad Rzeszutek Wilk
2014-03-12 1:00 ` Atom2
2014-03-12 8:20 ` Jan Beulich
2014-03-12 11:14 ` Atom2
2014-03-12 11:42 ` Jan Beulich
2014-03-12 11:58 ` Atom2
2014-03-12 13:50 ` Konrad Rzeszutek Wilk
2014-03-12 15:09 ` Atom2
2014-03-12 16:30 ` Konrad Rzeszutek Wilk
2014-03-11 13:32 ` Ian Campbell
2014-03-11 15:09 ` 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=20140311173828.GE14684@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=daniel.kiper@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xenproject.org \
--cc=yang.z.zhang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).