From mboxrd@z Thu Jan 1 00:00:00 1970 From: Malcolm Crossley Subject: Re: [PATCH v2] libxl: Add AHCI support for upstream qemu Date: Thu, 25 Jun 2015 13:03:45 +0100 Message-ID: <558BEE21.7090403@citrix.com> References: <1435050935-3094-1-git-send-email-fabio.fantoni@m2r.biz> <1435227693.32500.25.camel@citrix.com> <558BE2BC.2090304@m2r.biz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <558BE2BC.2090304@m2r.biz> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Fabio Fantoni , Ian Campbell 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 List-Id: xen-devel@lists.xenproject.org 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 :)