All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Wei Liu <wei.liu2@citrix.com>, Olaf Hering <olaf@aepfle.de>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH v1] xl: show full value of cpu_khz in xl info output
Date: Fri, 18 May 2018 12:01:49 +0200	[thread overview]
Message-ID: <27b832d9-2e61-757a-cbb5-5918fbd0a35a@suse.com> (raw)
In-Reply-To: <20180517143131.esp4q7a6agcy2b7a@citrix.com>

On 17/05/18 16:31, Wei Liu wrote:
> On Thu, May 17, 2018 at 04:25:58PM +0200, Olaf Hering wrote:
>> Am Tue,  3 Apr 2018 13:14:11 +0200
>> schrieb Olaf Hering <olaf@aepfle.de>:
>>
>>> The exact value of cpu_khz can only be obtained via 'xl dmesg', and
>>> therefore can be lost after some time. 'xl info' truncates the value to
>>> full MHz. Adjust the output to show the full khz value.
>>> This helps the host admin to track how a host has calibrated itself. The
>>> value of cpu_khz is used during live migration for the decision if
>>> access to TSC should be emualted.
>>
>> I just found this in my backlog of unapplied patches.
>> Any word on this change?
> 
> Acked-by: Wei Liu <wei.liu2@citrix.com>
> 
> Sorry I missed this one.
> 
> CC Juergen, I think this should be in 4.11.

Release-acked-by: Juergen Gross <jgross@suse.com>


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

      reply	other threads:[~2018-05-18 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-03 11:14 [PATCH v1] xl: show full value of cpu_khz in xl info output Olaf Hering
2018-05-17 14:25 ` Olaf Hering
2018-05-17 14:31   ` Wei Liu
2018-05-18 10:01     ` Juergen Gross [this message]

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=27b832d9-2e61-757a-cbb5-5918fbd0a35a@suse.com \
    --to=jgross@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=olaf@aepfle.de \
    --cc=wei.liu2@citrix.com \
    --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.