virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: changing definition of paravirt_ops.iret
Date: Tue, 22 May 2007 01:08:42 +0100	[thread overview]
Message-ID: <4652348A.1020003@goop.org> (raw)
In-Reply-To: <4651E6CF.9010001@vmware.com>

Zachary Amsden wrote:
> Strongly nacked.  If you need %fs and a free register, just push / pop
> them yourself.  We use push / pop to get %eax free for IRET in the VMI
> ROM. 

Yeah, it doesn't interact nicely with either the error_code or the nmi
stack switch thing.

    J

      reply	other threads:[~2007-05-22  0:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-21 16:27 changing definition of paravirt_ops.iret Jeremy Fitzhardinge
2007-05-21 16:46 ` Chris Wright
2007-05-21 16:53   ` Jeremy Fitzhardinge
2007-05-21 18:37 ` Zachary Amsden
2007-05-22  0:08   ` Jeremy Fitzhardinge [this message]

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=4652348A.1020003@goop.org \
    --to=jeremy@goop.org \
    --cc=chrisw@sous-sol.org \
    --cc=ebiederm@xmission.com \
    --cc=virtualization@lists.osdl.org \
    --cc=zach@vmware.com \
    /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).