All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: srostedt@redhat.com
Cc: xen-devel <xen-devel@lists.xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	David Vrabel <david.vrabel@citrix.com>,
	linux-kernel@vger.kernel.org
Subject: Xen 32-bit PV regression
Date: Thu, 03 Apr 2014 23:23:07 -0400	[thread overview]
Message-ID: <533E259B.4030507@oracle.com> (raw)

Steven,

Looks like commit 198d208df (x86: Keep thread_info on thread stack in 
x86_32) broke Xen's 32-bit PV guests.

I poked a little at it and it seems that at least the ifdef in 
xen_cpu_up() needs to be adjusted to set up kernel_stack --- that allows 
CPUs to get going. This is not enough though (not particularly 
surprisingly) and we die a little later with #GPF in xen_iret.

-boris

             reply	other threads:[~2014-04-04  3:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04  3:23 Boris Ostrovsky [this message]
2014-04-04  3:55 ` Xen 32-bit PV regression Boris Ostrovsky
2014-04-04  3:55 ` Boris Ostrovsky
  -- strict thread matches above, loose matches on Subject: below --
2014-04-04  3:23 Boris Ostrovsky

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=533E259B.4030507@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srostedt@redhat.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.