From: James Smart <James.Smart@Emulex.Com>
To: "Mukker, Atul" <Atul.Mukker@lsi.com>
Cc: Drew <drew.kay@gmail.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: Recommended HBA management interfaces
Date: Tue, 21 Jul 2009 10:59:17 -0400 [thread overview]
Message-ID: <4A65D7C5.8050101@emulex.com> (raw)
In-Reply-To: <6C678488C5CEE74F813A4D1948FD2DC7A99EFF96@cosmail02.lsi.com>
There's some interesting dichotomies in this question/response:
Drivers exist :
1) Within the ESX kernel for physical hardware, with ESX leveraging the api's
from the linux kernel/midlayer/etc in order to pick up linux drivers for
device support in their kernel/hypervisor. This was my discussion area.
Management of this area wants to happen via VMware-based paradigms.
2) Within a guest OS for : a) emulated hardware or b) direct pci function
passthru to the guest os.
3) VMware emulates a LSI adapter as a guest-os-to-hypervisor abstraction point
(e.g 2a). Thus LSI drivers could/can exist in both ESX and in the Guest OS
simultaneously, and if the guest is running linux, both driver instances are
effectively the linux driver. Atul/LSI is trying very hard to make the one
linux driver work in both environments.
Hope this helps.
-- james s
Mukker, Atul wrote:
> We _are_ talking about the "optimized" driver :-)
>
>> -----Original Message-----
>> From: linux-scsi-owner@vger.kernel.org [mailto:linux-scsi-
>> owner@vger.kernel.org] On Behalf Of Drew
>> Sent: Tuesday, July 21, 2009 9:49 AM
>> To: linux-scsi@vger.kernel.org
>> Subject: Re: Recommended HBA management interfaces
>>
>>> VMware attempts to emulate the linux driver/midlayer api's, but
>> emulation is done
>>> in their own way, with their own semantics, for their own purposes..
>> Anyone
>>> that believes they just drop a linux driver into vmware and it works w/o
>>> change has a screw loose.
>> I must confess to some confusion James. I thought that VMware emulates
>> hardware and that outside of optimized drivers they don't get involved
>> in the higher layers of the guest OS.
>>
>>
>> --
>> Drew
>>
>> "Nothing in life is to be feared. It is only to be understood."
>> --Marie Curie
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-07-21 14:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 13:16 Recommended HBA management interfaces Mukker, Atul
2009-07-17 15:35 ` Brian King
2009-07-20 16:28 ` Mukker, Atul
2009-07-20 16:57 ` James Smart
2009-07-20 18:03 ` Mukker, Atul
2009-07-20 19:08 ` James Smart
2009-07-20 20:33 ` Mukker, Atul
2009-07-21 12:29 ` James Smart
2009-07-21 13:38 ` Mukker, Atul
2009-07-21 13:48 ` Drew
2009-07-21 13:58 ` Mukker, Atul
2009-07-21 14:59 ` James Smart [this message]
2009-07-21 16:27 ` Drew
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=4A65D7C5.8050101@emulex.com \
--to=james.smart@emulex.com \
--cc=Atul.Mukker@lsi.com \
--cc=drew.kay@gmail.com \
--cc=linux-scsi@vger.kernel.org \
/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.