From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>,
IanCampbell <Ian.Campbell@citrix.com>,
"stefano.stabellini@eu.citrix.com"
<stefano.stabellini@eu.citrix.com>
Subject: Re: [hybrid]: hang in update_wall_time
Date: Wed, 21 Mar 2012 11:08:48 -0700 [thread overview]
Message-ID: <20120321110848.1978c48d@mantra.us.oracle.com> (raw)
In-Reply-To: <4F6859AB0200007800079895@nat28.tlf.novell.com>
On Tue, 20 Mar 2012 09:19:23 +0000
"Jan Beulich" <JBeulich@suse.com> wrote:
> >>> On 20.03.12 at 02:30, Mukesh Rathor <mukesh.rathor@oracle.com>
...
> Your Dom0 hasn't possibly played with the HPET, and Xen at the same
> time is using the HPET as clock source? (Preventing this is rather
> difficult, as the HPET memory space - iirc - is just 1k, so excluding
> Dom0 access to the full page isn't easily possible. Consequently, Xen
> so far has been relying on Dom0 to not get in the way.)
Pretty close. I debugged it finally, and the problem was the hybrid
writing to the HPET while xen was using it. This was happening because
ACPI was not properly initialized, and created a ripple effect where
hpet_virt_address was set. In PV, it's not set and so hpet_late_init()
bails.
Anyways, I fixed it, and now to next one caused by proper
initialization of ACPI... :).
thanks,
Mukesh
next prev parent reply other threads:[~2012-03-21 18:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 1:30 [hybrid]: hang in update_wall_time Mukesh Rathor
2012-03-20 9:19 ` Jan Beulich
2012-03-21 18:08 ` Mukesh Rathor [this message]
2012-03-20 12:39 ` Stefano Stabellini
2012-03-20 19:08 ` Mukesh Rathor
2012-03-21 10:42 ` Stefano Stabellini
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=20120321110848.1978c48d@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=stefano.stabellini@eu.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 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 NNTP newsgroup(s).