All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerone Young <jyoung5@us.ibm.com>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel <xen-devel@lists.sourceforge.net>,
	ian.pratt@cl.cam.ac.uk
Subject: RE: x86-64 Xen development
Date: Thu, 03 Mar 2005 13:12:25 -0600	[thread overview]
Message-ID: <1109877145.6787.10.camel@thinkpad> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017303646D6D@scsmsx402.amr.corp.intel.com>

Sounds awesome! I'll be looking into supporting 32-bit apps. I am also
getting the current tool ready for x86-64 to be able to lauch 64-bit
domains.

Supporting 32-bit apps (as well as 32bit domains) are going to require
an ioctl conversion layer as some syscall conversion stuff. Not 100%
sure yet on how things are going to be just yet. I'll figure something
out and get back to the list.


On Thu, 2005-03-03 at 09:03 -0800, Nakajima, Jun wrote:
> Ian Pratt wrote:
> >> 	What is Intel's status on x86-64 work for Xen? Do require any
> >> assistance on any remaining work to get Xen x86-64 enabled? We want
> >> to have more public discussion on x86-64 Xen development.
> > 
> > Jun,
> > 
> > Please can you post the x86_64 dom0 domain builder so that Jerone can
> > get to work on the user space builder.
> > 
> > Are there any fixes we need to do to x86_64 xen? Have you an ETA on
> > the dom0 checkin?
> 
> Ian,
> 
> I'm shooting the next week, in a week or so. We've been making steady
> progress despite _numerous_ minor issus/problems. Jerone, it would be
> helpful if you take a look at 32-bit apps support (i.e. what does it
> take for us to support those in xenolinux64) because we are not
> proactively looking at the area at this point.
> 
> There are a couple of minor fixes required in the hypervisor. For
> example, check_descriptor() in arch/x86/x86-64/mm.c needs to shift bits
> when comparing the value.  
> /* The guest can only safely be executed in ring 3. */
>     if ( ((b & _SEGMENT_DPL) >> 13) !=  3) {
>                 goto bad;
>     }
> I'll send patches this week.
> 
> Jun
> 
> 
-- 
Jerone Young
Open Virtualization
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-03 19:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03 17:03 x86-64 Xen development Nakajima, Jun
2005-03-03 19:12 ` Jerone Young [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-03 19:47 Ian Pratt
2005-03-03 11:26 Ian Pratt
2005-03-03 12:00 ` Keir Fraser
2005-03-03  2:34 Jerone Young

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=1109877145.6787.10.camel@thinkpad \
    --to=jyoung5@us.ibm.com \
    --cc=ian.pratt@cl.cam.ac.uk \
    --cc=jun.nakajima@intel.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.