From: "Jan Beulich" <JBeulich@suse.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Xen 4.2 TODO / Release Plan
Date: Mon, 20 Aug 2012 12:06:08 +0100 [thread overview]
Message-ID: <50323640020000780009662A@nat28.tlf.novell.com> (raw)
In-Reply-To: <1345454240.28762.18.camel@zakaz.uk.xensource.com>
>>> On 20.08.12 at 11:17, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> * fix high change rate to CMOS RTC periodic interrupt causing
> guest wall clock time to lag (possible fix outlined, needs to be
> put in patch form and thoroughly reviewed/tested for unwanted
> side effects, Jan Beulich)
Patch was posted, but no comments or approval to commit so far.
Also, reportedly the patch only improves the situation, it doesn't
completely eliminate the problem. For the moment I'm out of ideas,
though, and hence would hope some others could help here.
Jan
next prev parent reply other threads:[~2012-08-20 11:06 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 9:17 Xen 4.2 TODO / Release Plan Ian Campbell
2012-08-20 11:06 ` Jan Beulich [this message]
[not found] ` <50338D02.8050009@amd.com>
[not found] ` <5033B0070200007800096B4D@nat28.tlf.novell.com>
[not found] ` <5034B907.7020506@amd.com>
2012-08-22 14:47 ` RTC patch Jan Beulich
2012-08-22 15:01 ` Christoph Egger
2012-08-22 15:13 ` Jan Beulich
2012-08-21 15:14 ` Xen 4.2 TODO / Release Plan Ren, Yongjie
2012-08-21 15:27 ` Ian Campbell
2012-08-21 15:49 ` Ren, Yongjie
2012-08-21 15:39 ` Ben Guthro
2012-08-21 16:08 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2012-08-28 10:06 Ian Campbell
2012-08-31 17:26 ` George Dunlap
2012-09-03 9:10 ` Ian Campbell
2012-08-31 17:36 ` George Dunlap
[not found] ` <CAFLBxZaDmZ8bTQzZ_CpQpTros9WFK7Q96v-1Y3zXXWLdciMXTw@mail.gmail.com>
2012-08-31 17:42 ` Konrad Rzeszutek Wilk
2012-09-02 4:46 ` Pasi Kärkkäinen
2012-09-03 9:09 ` Ian Campbell
2012-08-14 9:05 Ian Campbell
2012-08-14 9:52 ` Jan Beulich
2012-08-15 15:46 ` George Dunlap
2012-07-30 8:30 Ian Campbell
2012-08-03 10:09 ` Ian Campbell
2012-08-03 10:28 ` Keir Fraser
2012-08-03 10:30 ` Ian Campbell
2012-08-03 10:44 ` Jan Beulich
2012-08-06 17:06 ` Liu, Jinsong
2012-08-07 6:38 ` Jan Beulich
2012-08-07 7:50 ` Keir Fraser
2012-08-07 8:05 ` Jan Beulich
2012-08-07 8:10 ` Ian Campbell
2012-08-07 18:13 ` Liu, Jinsong
2012-08-08 6:37 ` Jan Beulich
2012-07-17 16:47 Ian Campbell
2012-07-17 16:51 ` Andrew Cooper
2012-06-12 13:00 Ian Campbell
2012-06-12 13:57 ` Jan Beulich
2012-06-12 14:05 ` Ian Campbell
2012-06-13 10:48 ` Stefano Stabellini
2012-06-20 15:25 ` Ian Campbell
2012-06-20 15:40 ` Jan Beulich
2012-06-20 15:47 ` Ian Jackson
2012-06-20 16:06 ` Jan Beulich
2012-06-20 15:50 ` Ian Campbell
2012-06-20 15:58 ` Ian Jackson
2012-06-20 15:46 ` Ian Jackson
2012-06-18 8:36 ` Roger Pau Monne
2012-06-18 12:19 ` Dario Faggioli
2012-05-21 11:47 Ian Campbell
2012-05-21 13:00 ` Pasi Kärkkäinen
2012-05-21 13:05 ` Ian Campbell
2012-05-21 13:32 ` Jan Beulich
2012-05-14 10:26 Ian Campbell
2012-05-14 11:14 ` Jan Beulich
2012-05-29 9:32 ` Ian Campbell
2012-05-29 10:10 ` Jan Beulich
2012-05-31 9:24 ` Olaf Hering
2012-05-31 9:37 ` Jan Beulich
2012-05-31 9:56 ` Stefano Stabellini
2012-05-31 21:43 ` Olaf Hering
2012-05-14 13:51 ` Dario Faggioli
2012-05-14 15:33 ` Ian Jackson
2012-05-14 15:43 ` Ian Campbell
2012-05-14 17:07 ` Dario Faggioli
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=50323640020000780009662A@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Campbell@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.