virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
	Ian Campbell <Ian.Campbell@XenSource.com>,
	Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: Xen status
Date: Wed, 13 Sep 2006 18:59:15 -0700	[thread overview]
Message-ID: <20060914015915.GP10348@sequoia.sous-sol.org> (raw)
In-Reply-To: <45088D19.5070801@goop.org>

* Jeremy Fitzhardinge (jeremy@goop.org) wrote:
> Well, the PDA stuff took a bit longer to settle down than I would have 
> hoped, but it seems fairly sound now.
> 
> I just committed the changes needed to make Xen happy with the PDA, 
> which means making sure an appropriate GDT is set up early enough.
> 
> I also seem to have avoided most of the APIC issues under Xen by simply 
> making the cpuid not report the presence of an APIC.
> 
> With these in place, things are getting fairly far, but not to 
> usermode.  It often gets as far as trying to mount root, but it fails; I 
> haven't investigated that yet.  But it also frequently crashes before 
> then, depending on when it gets an interrupt.  I'm trying to work out 
> what's happening here, but the symptom is eip == 0x00000001 (!).

Haven't seen that one.

> Chris, what local hacks do you have in your tree?

Essentially all the local hacks I have are for debugging.  There was
one bit which was just for apic clock setup.  But the symptom w/out
that was a hang, not a crash.  They're also on a remote machine that
has apparently died.  Re-tooling locally ATM.

thanks,
-chris

  parent reply	other threads:[~2006-09-14  1:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 22:58 Xen status Jeremy Fitzhardinge
2006-09-14  0:30 ` Zachary Amsden
2006-09-14  1:59 ` Chris Wright [this message]
2006-09-14  6:35   ` 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=20060914015915.GP10348@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=Ian.Campbell@XenSource.com \
    --cc=jeremy@goop.org \
    --cc=virtualization@lists.osdl.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).