From: Malcolm Crossley <malcolm.crossley@citrix.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>,
Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xensource.com, wei.liu2@citrix.com,
Stefano.Stabellini@eu.citrix.com, George.Dunlap@eu.citrix.com,
Ian.Jackson@eu.citrix.com, Paul.Durrant@citrix.com,
anthony.perard@citrix.com
Subject: Re: [PATCH v2] libxl: Add AHCI support for upstream qemu
Date: Thu, 25 Jun 2015 13:03:45 +0100 [thread overview]
Message-ID: <558BEE21.7090403@citrix.com> (raw)
In-Reply-To: <558BE2BC.2090304@m2r.biz>
On 25/06/15 12:15, Fabio Fantoni wrote:
> Il 25/06/2015 12:21, Ian Campbell ha scritto:
>> On Tue, 2015-06-23 at 11:15 +0200, Fabio Fantoni wrote:
>>> Usage:
>>> ahci=0|1 (default=0)
>> I think a global rather than per disk option is OK (I can't think why a
>> user would want to mix and match) but maybe we should consider using an
>> enum (with values ide and ahci, defaulting to ide in libxl) so that we
>> can add support for whatever fancy new disk controller everyone is using
>> in 5 years time?
>
> ahci was added 4 years ago in qemu and I don't know of newer similar tecnology, in the case of enum
> probably shold be more generic for include more future possibility or I'm wrong? in that case what
> can be the name?
> @stabellini and other developer: any advice about this?
You may want to support nvme device interface as well. This would be the newer similar technology
you are referring to :)
prev parent reply other threads:[~2015-06-25 12:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 9:15 [PATCH v2] libxl: Add AHCI support for upstream qemu Fabio Fantoni
2015-06-23 11:32 ` Stefano Stabellini
2015-06-25 10:21 ` Ian Campbell
2015-06-25 11:15 ` Fabio Fantoni
2015-06-25 11:58 ` Stefano Stabellini
2015-06-25 12:18 ` Ian Campbell
2015-06-26 7:55 ` Fabio Fantoni
2015-06-25 12:03 ` Malcolm Crossley [this message]
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=558BEE21.7090403@citrix.com \
--to=malcolm.crossley@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=fabio.fantoni@m2r.biz \
--cc=ian.campbell@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xensource.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.