Re: [PATCH v10 3/6] x86/ioreq server: Add device model wrappers for new DMOP

From: "Jan Beulich" <JBeulich@suse.com>
To: Paul Durrant <Paul.Durrant@citrix.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Yu Zhang <yu.c.zhang@linux.intel.com>
Cc: Ian Jackson <Ian.Jackson@citrix.com>,
	"zhiyuan.lv@intel.com" <zhiyuan.lv@intel.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v10 3/6] x86/ioreq server: Add device model wrappers for new DMOP
Date: Wed, 05 Apr 2017 03:38:52 -0600	[thread overview]
Message-ID: <58E4D74C020000780014D210@prv-mh.provo.novell.com> (raw)
In-Reply-To: <58E4B75B.80406@linux.intel.com>

>>> On 05.04.17 at 11:22, <yu.c.zhang@linux.intel.com> wrote:

> 
> On 4/5/2017 5:21 PM, Jan Beulich wrote:
>>>>> On 05.04.17 at 08:53, <yu.c.zhang@linux.intel.com> wrote:
>>> Or with other patches received "Reviewed by", we can just drop the
>>> useless code of this patch.
>>> Any suggestions?
>> Without the libxc wrapper, the new DMOP is effectively dead code
>> too. All or nothing, imo.
> 
> Thanks Jan. But I am confused. :(
> 
> Previously I thought the libxc needs to be updated together with 
> libxendevicemodel.
> But from Paul & Wei's reply, and previous commit from Paul, my new 
> understanding
> is that these libxc interfaces are only compatible code for old ones, 
> and libxendevicemodel
> can be triggered, without through libxc interfaces.
> 
> Is my new interpretation wrong?

Oops, I'm sorry, I still have to get used to the split. I indeed meant
"without the libxendevicemodel wrapper ..."

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel