All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Chris Wright <chrisw@sous-sol.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	Ian Campbell <Ian.Campbell@XenSource.com>
Subject: Re: Xen status
Date: Wed, 13 Sep 2006 17:30:12 -0700	[thread overview]
Message-ID: <4508A294.3090200@vmware.com> (raw)
In-Reply-To: <45088D19.5070801@goop.org>

Jeremy Fitzhardinge 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 (!).

Bad patches?  I put code in vmi.c to patch IRET and SYSEXIT EIPs to 0x1 
and 0x2, respectively, once upon a time.  Maybe it migrated over to you 
somehow?

  reply	other threads:[~2006-09-14  0:30 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 [this message]
2006-09-14  1:59 ` Chris Wright
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=4508A294.3090200@vmware.com \
    --to=zach@vmware.com \
    --cc=Ian.Campbell@XenSource.com \
    --cc=chrisw@sous-sol.org \
    --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 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.