From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
xen-devel@lists.xensource.com, Jed Smith <jed@linode.com>,
Jan Beulich <JBeulich@novell.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Re: [PATCH] x86: unconditionally mark TSC unstable under Xen
Date: Sun, 15 Aug 2010 16:40:14 -0700 [thread overview]
Message-ID: <4C687ADE.3020100@goop.org> (raw)
In-Reply-To: <AANLkTinc=w4mRGoCEumsNCfbUVOJbycaH4Omem5eB6th@mail.gmail.com>
On 08/15/2010 01:57 PM, Ævar Arnfjörð Bjarmason wrote:
> Hi all, I was wondering what the status on this issue was. Maybe I've
> missed something, but I've looked through the lkml and xen archives and
> I haven't found a re-rolled patch that addresses this issue.
>
> I'm not very familiar with this area (well, any area) of the kernel,
> but if there's something needed to push this forward I'd be happy to
> help with that, or if this is already being addressed somewhere else a
> pointer to where that is would be welcome.
A patch that fixes this is in mainline and all the supported stable
kernels. Itis "xen: drop xen_sched_clock in favour of using plain
wallclock time".
J
next prev parent reply other threads:[~2010-08-15 23:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 19:24 [PATCH] x86: unconditionally mark TSC unstable under Xen Jed Smith
2010-07-14 21:36 ` Jeremy Fitzhardinge
[not found] ` <alpine.DEB.2.00.1007151656380.21432@kaball-desktop 4C3F37A5.9050606@goop.org>
2010-07-14 22:29 ` Jed Smith
2010-07-15 14:23 ` Jed Smith
2010-07-15 15:57 ` Stefano Stabellini
2010-07-15 16:30 ` Jeremy Fitzhardinge
2010-07-15 16:40 ` Dan Magenheimer
2010-07-15 16:45 ` Jeremy Fitzhardinge
2010-07-15 17:14 ` Dan Magenheimer
2010-07-15 17:30 ` Jeremy Fitzhardinge
2010-07-15 17:48 ` Dan Magenheimer
2010-07-15 18:05 ` Jeremy Fitzhardinge
2010-08-15 20:57 ` Ævar Arnfjörð Bjarmason
2010-08-15 23:40 ` Jeremy Fitzhardinge [this message]
2010-08-16 1:27 ` Ævar Arnfjörð Bjarmason
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=4C687ADE.3020100@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.com \
--cc=avarab@gmail.com \
--cc=dan.magenheimer@oracle.com \
--cc=jed@linode.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 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.