* how hypervisor separates assembly instructions
[not found] <CALKraOZKGQjWag0Jk1-xZ_9o9Xh1N8pwBhdEhXOAT_dWpQA66Q@mail.gmail.com>
@ 2011-10-14 15:43 ` Tapas Mishra
2011-10-14 15:52 ` Andrew Cooper
0 siblings, 1 reply; 4+ messages in thread
From: Tapas Mishra @ 2011-10-14 15:43 UTC (permalink / raw)
To: Xen List
As far as my understanding goes a CPU gets Assembly instructions to work and
upon those instructions it works. These assembly instructions come
from the OS running on top of bare metal.
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.
--
------------------------------
Tapas
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how hypervisor separates assembly instructions
2011-10-14 15:43 ` how hypervisor separates assembly instructions Tapas Mishra
@ 2011-10-14 15:52 ` Andrew Cooper
2011-10-15 0:23 ` Tapas Mishra
0 siblings, 1 reply; 4+ messages in thread
From: Andrew Cooper @ 2011-10-14 15:52 UTC (permalink / raw)
To: xen-devel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how hypervisor separates assembly instructions
2011-10-14 15:52 ` Andrew Cooper
@ 2011-10-15 0:23 ` Tapas Mishra
2011-10-17 14:39 ` Ian Jackson
0 siblings, 1 reply; 4+ messages in thread
From: Tapas Mishra @ 2011-10-15 0:23 UTC (permalink / raw)
To: xen-devel
On Fri, Oct 14, 2011 at 9:22 PM, Andrew Cooper
<andrew.cooper3@citrix.com> wrote:
> The hypervisor "separates" different operating systems in the same way
> that regular operating systems separate different processes.
>
Hi,
thanks for your message I want to understand this last 2 lines in
detail.As how does the hypervisor separates different OS and things
"run."
--
------------------------------
Tapas
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how hypervisor separates assembly instructions
2011-10-15 0:23 ` Tapas Mishra
@ 2011-10-17 14:39 ` Ian Jackson
0 siblings, 0 replies; 4+ messages in thread
From: Ian Jackson @ 2011-10-17 14:39 UTC (permalink / raw)
To: Tapas Mishra; +Cc: xen-devel
Tapas Mishra writes ("Re: [Xen-devel] how hypervisor separates assembly instructions"):
> thanks for your message I want to understand this last 2 lines in
> detail.As how does the hypervisor separates different OS and things
> "run."
I think your questions would best be dealt with by you attending a
basic course in computer architecture. If you aren't already on one,
that is.
In any case xen-devel is not the appropriate please for this
conversation, I'm afraid. Please would others not respond; it may
seem helpful, but actually it just attracts more inappropriate
questions, particularly at this time of year.
Ian.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-10-17 14:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
2011-10-15 0:23 ` Tapas Mishra
2011-10-17 14:39 ` Ian Jackson
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.