From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xensource.com
Subject: Re: how hypervisor separates assembly instructions
Date: Fri, 14 Oct 2011 16:52:45 +0100 [thread overview]
Message-ID: <4E985ACD.3020808@citrix.com> (raw)
In-Reply-To: <CALKraObo-k_QiE1RAVP0B=buQdAET-tF7e=zJRS-NXny=kVZMg@mail.gmail.com>
On 14/10/11 16:43, Tapas Mishra wrote:
> As far as my understanding goes a CPU gets Assembly instructions to work
The CPU reads computer opcode from memory. (Assembly instructions are
the name for the mnemonics, not the binary representation which the CPU
actually runs)
> and
> upon those instructions it works. These assembly instructions come
> from the OS running on top of bare metal.
Not really. All programs are just opcode which the CPU can run. OS's
are the same as regular programs in this regard.
> I have some understanding of hypercalls.
> So what does a hypercall implement that it is able to separate the
> different Assembly instructions
> coming from different Guest OSeS or in other words how does the
> hypervisor separates the Assembly instructions which should be run for
> different Guest OSeS running on top of hypervisor.I want to know it
> technically not theoretically.
The hypervisor "separates" different operating systems in the same way
that regular operating systems separate different processes.
> --
> ------------------------------
>
> Tapas
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next prev parent reply other threads:[~2011-10-14 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALKraOZKGQjWag0Jk1-xZ_9o9Xh1N8pwBhdEhXOAT_dWpQA66Q@mail.gmail.com>
2011-10-14 15:43 ` how hypervisor separates assembly instructions Tapas Mishra
2011-10-14 15:52 ` Andrew Cooper [this message]
2011-10-15 0:23 ` Tapas Mishra
2011-10-17 14:39 ` Ian Jackson
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=4E985ACD.3020808@citrix.com \
--to=andrew.cooper3@citrix.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.