9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] I/O load crashes Qemu
Date: Fri, 13 Jun 2008 17:40:52 -0700	[thread overview]
Message-ID: <20080614004052.9F76C5B46@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Fri, 13 Jun 2008 19:52:22 EDT." <d614a29f3bddcce459fb02541e361093@quanstro.net>

On Fri, 13 Jun 2008 19:52:22 EDT erik quanstrom <quanstro@quanstro.net>  wrote:
> > You don't need this sort of code in a virtualizable processor.
> > See for example
> >   http://en.wikipedia.org/wiki/Popek_and_Goldberg_virtualization_requiremen
> ts
>
> i'm not convinced that the illusion that the virtualized environment
> is in every way equivalent to the bare iron is always useful or worth
> the effort.  why should a virtualized operating system need to worry
> about what nic the machine has?

Well the URL was more to get the point across.  Whether your
virtual OS uses simplified virtual devices or emulated real
devices, you shouldn't have to emulate each instruction in
software!

I won't argue with "worth the effort" but it can be useful
(e.g. running dusty decks, debugging etc).

My argument is more that real device intefaces should be
designed to make virtualization efficient.

> for example vmware doesn't provide this sort of virtualized environment.
> it provides the same virtual network card interface regardless of
> what hardware the machine has.

It is doable but it took them years to get there and provide
good efficiency.  May be even more years that VM/370?!



  reply	other threads:[~2008-06-14  0:40 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13  1:54 Venkatesh Srinivas
2008-06-13  2:01 ` Pietro Gagliardi
2008-06-13  3:38   ` Lorenzo Fernando Bivens de la Fuente
2008-06-13  3:38     ` Lorenzo Fernando Bivens de la Fuente
2008-06-13  4:00     ` Venkatesh Srinivas
2008-06-13  8:08       ` sqweek
2008-06-13 10:41         ` Bruce Ellis
2008-06-13 11:47           ` Rodolfo kix García 
2008-06-13 19:05           ` Bakul Shah
2008-06-13 20:03             ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 20:33               ` Charles Forsyth
2008-06-13 20:30                 ` erik quanstrom
2008-06-13 20:58                   ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 23:52                     ` erik quanstrom
2008-06-14  0:40                       ` Bakul Shah [this message]
2008-06-13 20:35                 ` Charles Forsyth
2008-06-13 23:01                 ` Bakul Shah
2008-06-13 23:26                   ` Pietro Gagliardi
2008-06-13 23:36                     ` Bakul Shah
2008-06-13 23:42                     ` Lorenzo Fernando Bivens de la Fuente
2008-06-13 23:52                       ` Uriel
2008-06-17 10:51             ` matt
2008-06-13 12:57   ` stefanha
2008-06-13 12:22 ` Fazlul Shahriar
2008-06-14  0:39 erik quanstrom
2008-06-14  1:24 ` Bakul Shah
2008-06-14  4:58   ` Bruce Ellis
2008-06-14  5:30     ` Iruata Souza
2008-06-14 12:53     ` erik quanstrom
2008-06-14 15:14       ` Iruata Souza
2008-06-14 14:15   ` erik quanstrom
2008-06-15  0:01     ` Bakul Shah

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=20080614004052.9F76C5B46@mail.bitblocks.com \
    --to=bakul+plan9@bitblocks.com \
    --cc=9fans@9fans.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).