From: David Vrabel <david.vrabel@citrix.com>
To: Imre Palik <imrep.amz@gmail.com>,
<xen-devel@lists.xenproject.org>,
David Vrabel <david.vrabel@citrix.com>
Cc: "Palik, Imre" <imrep@amazon.de>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>,
Anthony Liguori <aliguori@amazon.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Xen-devel] [PATCH] xen-time: decreasing the rating of the xen clocksource below that of the tsc clocksource for dom0's
Date: Tue, 20 Jan 2015 19:21:01 +0000 [thread overview]
Message-ID: <54BEAA9D.5090303@citrix.com> (raw)
In-Reply-To: <1421136862-15083-1-git-send-email-imrep.amz@gmail.com>
On 13/01/15 08:14, Imre Palik wrote:
> From: "Palik, Imre" <imrep@amazon.de>
>
> In Dom0's the use of the TSC clocksource (whenever it is stable enough to
> be used) instead of the Xen clocksource should not cause any issues, as
> Dom0 VMs never live-migrated. The TSC clocksource is somewhat more
> efficient than the Xen paravirtualised clocksource, thus it should have
> higher rating.
>
> This patch decreases the rating of the Xen clocksource in Dom0s to 275.
> Which is half-way between the rating of the TSC clocksource (300) and the
> hpet clocksource (250).
Applied to devel/for-linus-3.20, thanks.
David
next prev parent reply other threads:[~2015-01-20 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 8:14 [PATCH] xen-time: decreasing the rating of the xen clocksource below that of the tsc clocksource for dom0's Imre Palik
2015-01-13 9:52 ` David Vrabel
2015-01-13 9:52 ` [Xen-devel] " David Vrabel
2015-01-13 15:42 ` Boris Ostrovsky
2015-01-13 15:42 ` [Xen-devel] " Boris Ostrovsky
2015-01-13 16:07 ` David Vrabel
2015-01-13 16:17 ` Boris Ostrovsky
2015-01-13 16:33 ` Boris Ostrovsky
2015-01-14 14:21 ` Boris Ostrovsky
2015-01-14 14:21 ` [Xen-devel] " Boris Ostrovsky
2015-01-13 16:33 ` Boris Ostrovsky
2015-01-13 16:17 ` Boris Ostrovsky
2015-01-13 16:07 ` David Vrabel
2015-01-20 19:21 ` David Vrabel [this message]
2015-01-20 19:21 ` David Vrabel
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=54BEAA9D.5090303@citrix.com \
--to=david.vrabel@citrix.com \
--cc=aliguori@amazon.com \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=imrep.amz@gmail.com \
--cc=imrep@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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.