From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Shriram Rajagopalan <rshriram@gmail.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org,
stable@kernel.org
Subject: Re: [Xen-devel] [PATCH] xen: ensure timer tick is resumed even on CPU driving the resume
Date: Thu, 20 May 2010 11:14:14 -0700 [thread overview]
Message-ID: <4BF57BF6.9000208@goop.org> (raw)
In-Reply-To: <AANLkTimc7ErLqUi4VKRztjAi6TNrv0Ooarc20OjFolkc@mail.gmail.com>
On 05/20/2010 10:42 AM, Shriram Rajagopalan wrote:
> I know this is a long shot but is there an equivalent piece of code in
> the 2.6.18.8-xen kernel where this patch could be applied ? Assuming
> that the 2.6.18 also has a similar bug.
Very unlikely. Time is completely different in 2.6.18-xen.
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Shriram Rajagopalan <rshriram@gmail.com>
Cc: stable@kernel.org, xen-devel@lists.xensource.com,
Ian Campbell <ian.campbell@citrix.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xen: ensure timer tick is resumed even on CPU driving the resume
Date: Thu, 20 May 2010 11:14:14 -0700 [thread overview]
Message-ID: <4BF57BF6.9000208@goop.org> (raw)
In-Reply-To: <AANLkTimc7ErLqUi4VKRztjAi6TNrv0Ooarc20OjFolkc@mail.gmail.com>
On 05/20/2010 10:42 AM, Shriram Rajagopalan wrote:
> I know this is a long shot but is there an equivalent piece of code in
> the 2.6.18.8-xen kernel where this patch could be applied ? Assuming
> that the 2.6.18 also has a similar bug.
Very unlikely. Time is completely different in 2.6.18-xen.
J
next prev parent reply other threads:[~2010-05-20 18:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1274283134.14939.205.camel@zakaz.uk.xensource.com>
2010-05-19 15:36 ` [PATCH] xen: ensure timer tick is resumed even on CPU driving the resume Ian Campbell
2010-05-19 15:36 ` Ian Campbell
2010-05-19 18:02 ` [Xen-devel] " Jeremy Fitzhardinge
2010-05-20 17:42 ` Shriram Rajagopalan
2010-05-20 18:14 ` Jeremy Fitzhardinge [this message]
2010-05-20 18:14 ` Jeremy Fitzhardinge
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=4BF57BF6.9000208@goop.org \
--to=jeremy@goop.org \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rshriram@gmail.com \
--cc=stable@kernel.org \
--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.