public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Wade Hampton <whampton@staffnet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.3, VMWare, 2 VMs
Date: Mon, 9 Apr 2001 18:50:08 MET-1	[thread overview]
Message-ID: <47CA75C62D7@vcnet.vc.cvut.cz> (raw)

On  9 Apr 01 at 12:03, Wade Hampton wrote:

> Is anyone having problems with running more than
> 1 VM on 2.4.3.  I have crashed my host O/S several
> times when I try to start two VMs.  Currently,
> I don't have an oops or other info to report, but
> I did see a post on the vmware list about 2.4.3 SMP
> and VMWARE.

As I already answered on VMware newsgroups:

VMware's 2.0.3 vmmon module uses save_flags() + cli()
in poll() fops, and after this cli() it calls
spin_lock() :-( It is not safest thing to do.
But it should not cause reboot. You should get

/dev/vmmon: 11 wait for global VM lock XX

and now dead machine with disabled interrupts...

As all other callers of HostIF_GlobalVMLock() hold
big kernel lock, easiest thing to do is to add
lock_kernel()/unlock_kernel() around LinuxDriver_Poll()
body.

Removing whole save_flags/cli is for sure much better,
but it is still in my queue (if you are looking into vmmon
driver, then whole poll mess is there to get wakeup on 
next jiffy, and not on next + one...).
                                        Petr Vandrovec
                                        vandrove@vc.cvut.cz
                                        

             reply	other threads:[~2001-04-09 16:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-09 18:50 Petr Vandrovec [this message]
2001-04-09 17:14 ` 2.4.3, VMWare, 2 VMs Wade Hampton
  -- strict thread matches above, loose matches on Subject: below --
2001-04-09 16:03 Wade Hampton

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=47CA75C62D7@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=whampton@staffnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox