From: jes@sgi.com
To: kvm-ia64@vger.kernel.org
Subject: [patch 0/4] KVM/ia64 SN2 RTC backed ITC emulation
Date: Wed, 25 Feb 2009 16:38:51 +0000 [thread overview]
Message-ID: <20090225163851.288440214@sgi.com> (raw)
This set of patches switches KVM to use the SN2 RTC clock source as
backing for the ITC emulation, as the ITC isn't synchronized on SN2.
The RTC is a memory mapped register which needs to be mapped into the
address space of the VMM module, and also accessed from the kernel. I
could try and split the changes into seperate files, but I honestly
thing it would cause more clutter than doing it this way.
With this change I can boot 64 vcpus on ia64 at stable boot times,
with the ITC backed ITC emulation, the boot would regularly hang for
minutes because time would suddenly go backwards.
Let me know what you think - this patch set is against Avi's tree as
of earlier today.
Cheers,
Jes
next reply other threads:[~2009-02-25 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 16:38 jes [this message]
2009-02-27 14:58 ` [patch 0/4] KVM/ia64 SN2 RTC backed ITC emulation Zhang, Xiantao
2009-03-10 10:20 ` Avi Kivity
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=20090225163851.288440214@sgi.com \
--to=jes@sgi.com \
--cc=kvm-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).