All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: x86-64 32bit applications support discussion
Date: Mon, 14 Mar 2005 11:02:27 -0600	[thread overview]
Message-ID: <1110819748.5379.60.camel@thinkpad> (raw)

	This thread is intended for discussion of 32bit application support
under x86-64 virtual domains. To all reading this is for development
purposes (x86-64 support is not done yet).
	
	I've been actively looking into 32bit application support for the
x86-64 Virutal Domains. I do have a question that I wanted to bring to
the list to start the discussion.

	Since the virtual domain & applications are all running in ring 3. Does
the hypervisor need to know how to tell the CPU when and when not to go
into compatibility mode to  run running 32bit applications properly
under virtual domains? As you may know while under Long mode you have
two sub modes: 64-bit mode & compatibility (for 32bit stuff). The
problem I see is that since we are in Long Mode the virutal domain needs
to tell CPU to go into the sub mode compatibility mode for it's 32
applications but does not have the access to do so. I'm not sure the
best way of going about this (new hypercall?) ?
	

-- 
Jerone Young
IBM Linux Technology Center
jyoung5@us.ibm.com
512-838-1157 (T/L: 678-1157)



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-03-14 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14 17:02 Jerone Young [this message]
2005-03-14 17:20 ` x86-64 32bit applications support discussion Kurt Garloff
2005-03-14 17:30   ` Kip Macy
  -- strict thread matches above, loose matches on Subject: below --
2005-03-14 21:59 Nakajima, Jun

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=1110819748.5379.60.camel@thinkpad \
    --to=jyoung5@us.ibm.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.