All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Que <qwejohn@gmail.com>
To: "Petersson, Mats" <mats.petersson@amd.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Domain0/Domain 1 and ring1 (x86) - tracing question
Date: Tue, 16 Aug 2005 10:30:25 -0400	[thread overview]
Message-ID: <ada605fb0508160730552d375a@mail.gmail.com> (raw)
In-Reply-To: <C3077285E500D5118C7300508BB3D9170C10BCFD@ukfsxmta.amd.com>

Hello,

Thanks !

This makes clear things a bit. 

However, I had grepped under the linux-2.6-xen-sparse tree and 
saw only one occurrence of  BOOT_CS , in that
linux-2.6-xen-sparse/include/asm-xen/asm-i386/segment.h.

I had also grepped under the "xen" (hypervisor) subtree and did not 
find and also under linux-2.6.12-xen0/arch/xen and did not find any
occurrence of  BOOT_CS.

(There is of course in linux-2.6.12-xen0/arch/xen/i386/boot/setup.S , 
but this seems unrelevant in our case).

I am probably missing something;
 Any ideas ? 

Regards,
John

On 8/16/05, Petersson, Mats <mats.petersson@amd.com> wrote:
> There's a #define in arch-x86_32.h that defines FLAT_KERNEL_[CDS]S to
> FLAT_RING1_[CDS]S. FLAT_RING1_[CDS]S is the entry in GDT for a CPL=1
> (ring 1) code/data/stack[1] segment selector.
> It is then used in various places to set up the registers used by the
> actual kernel, for example the file
> linux-2.6-xen-sparse/include/asm-xen/asm-i386/segment.h is using the
> KERNEL_CS to give the BOOT_CS to the Linux kernel.
> 
> [1] Stack segment is actually using the same selector as the data
> segment.
> 
> --
> Mats
> 
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of John Que
> > Sent: 16 August 2005 11:59
> > To: xen-devel@lists.xensource.com
> > Subject: [Xen-devel] Domain0/Domain 1 and ring1 (x86) -
> > tracing question
> >
> > Hello,
> > As I understand the Hypervisor should run in Ring 0 of the
> > x86 , and the domains (Domain0 and DomainU) should work in Ring 1.
> >
> > I was a bit curious where in the code this assiging of Ring 0
> > to Xen and Ring 1 to dom0/domU is done ?
> > I had tried to look under arch/xen/i386 and didn't find.
> >
> > Is it in the assembler *.S files ?
> >
> > Regards,
> > John
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
> 
>

  reply	other threads:[~2005-08-16 14:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-16 11:14 Domain0/Domain 1 and ring1 (x86) - tracing question Petersson, Mats
2005-08-16 14:30 ` John Que [this message]
2005-08-18 10:27   ` John Que
  -- strict thread matches above, loose matches on Subject: below --
2005-08-18 10:39 Petersson, Mats
2005-08-18 11:54 ` John Que
2005-08-16 10:59 John Que

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=ada605fb0508160730552d375a@mail.gmail.com \
    --to=qwejohn@gmail.com \
    --cc=mats.petersson@amd.com \
    --cc=xen-devel@lists.xensource.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 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.