All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: tsuraan <tsuraan@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: AHCI?
Date: Sun, 05 Apr 2009 18:39:55 +0300	[thread overview]
Message-ID: <49D8D0CB.70908@redhat.com> (raw)
In-Reply-To: <84fb38e30904050753n361bd112i54b58202ab84be15@mail.gmail.com>

tsuraan wrote:
>> No plan that I know of.  Is the LSI scsi device not supported by Solaris?
>>     
>
> Yeah, there was a short thread about it last July
> (http://www.mail-archive.com/kvm@vger.kernel.org/msg01633.html).  The
> jist of it is that 64-bit OpenSolaris no longer supports the 53c895a
> SCSI controller.  According to that thread, the 53c1010 is what VMWare
> uses, and OpenSolaris still uses that.
>
>   

I see.  That sucks.

> I don't really understand how a VM exposes a virtual device to a
> hosted OS, but I assume that it involves looking at a driver for a
> piece of hardware and then writing some code that emulates the
> behaviour expected by that driver?  

The best way is to look at the device spec and write the emulation to 
conform to that.

> I would think AHCI would be a
> great way to go, if that's the case, since it would be an actual
> implementation of a standard instead of an arbitrary card.  Does kvm
> use the qemu source for its drivers, or is there a separate source
> tree for it now?  

We use the qemu source (we have our own branch, but it's very close to 
qemu upstream).


-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-04-05 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05  3:30 AHCI? tsuraan
2009-04-05 11:50 ` AHCI? Avi Kivity
2009-04-05 14:53   ` AHCI? tsuraan
2009-04-05 15:39     ` Avi Kivity [this message]
2009-04-05 15:54       ` AHCI? tsuraan
2009-04-05 15:56         ` AHCI? Avi Kivity
2009-04-05 16:15           ` AHCI? tsuraan

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=49D8D0CB.70908@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=tsuraan@gmail.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.