From: Atom2 <ariel.atom2@web2web.at>
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: Wed, 12 Mar 2014 12:58:13 +0100 [thread overview]
Message-ID: <53204BD5.6090602@web2web.at> (raw)
In-Reply-To: <5320563102000078001232DE@nat28.tlf.novell.com>
Am 12.03.14 12:42, schrieb Jan Beulich:
>>>> On 12.03.14 at 12:14, Atom2 <ariel.atom2@web2web.at> wrote:
>> Am 12.03.14 09:20, schrieb Jan Beulich:
>> dmesg1 - that's the one where the update works
>> (XEN) Command line: placeholder ucode=-1 vga=gfx-1024x768x32 i915.mod |
>
> No notion of "loglvl=all" here.
That's because the output from sdiff is limited in width - so here you
go with the complete command line as reported by xl dmesg for the
ucode=1- case:
(XEN) Command line: placeholder ucode=-1 vga=gfx-1024x768x32
i915.modeset=1 loglvl=all guest_loglvl=all dom0_mem=4G,max:4G tmem=1 tm
em_compress=1 tmem_dedup=1 dom0_max_vcpus=8 dom0_vcpus_pin=true
cpufreq=xen cpuidle clocksource=hpet iommu=1 sched_credit_tsclice_ms
=5 bootscrub=0
>
>> dmesg2 - that's the one where the update doesn't work
>> | (XEN) Command line: placeholder ucode=scan vga=gfx-1024x768x32 i915.m
>
> Nor here.
And here for the ucode=scan case:
(XEN) Command line: placeholder ucode=scan vga=gfx-1024x768x32
i915.modeset=1 loglvl=all guest_loglvl=all dom0_mem=4G,max:4G tmem=1
tmem_compress=1 tmem_dedup=1 dom0_max_vcpus=8 dom0_vcpus_pin=true
cpufreq=xen cpuidle clocksource=hpet iommu=1 sched_credit_tsclice_
ms=5 bootscrub=0
>
> I also don't see what an i915 option has to do on the hypervisor
> command line - are you perhaps mixing up which options need to
> go where?
That may be a leftover from the install prior to xen - it shouldn't do
any harm though and I am more than happy to remove it; just in case you
find any other option that shouldn't be there just tell me, I am happy
to learn ...
>
> Jan
>
next prev parent reply other threads:[~2014-03-12 11:58 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
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 [this message]
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=53204BD5.6090602@web2web.at \
--to=ariel.atom2@web2web.at \
--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).