From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 78920C300 for ; Tue, 2 Jun 2015 05:27:25 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP; 01 Jun 2015 20:27:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,537,1427785200"; d="scan'208";a="580403545" Received: from pgsmsx101.gar.corp.intel.com ([10.221.44.78]) by orsmga003.jf.intel.com with ESMTP; 01 Jun 2015 20:27:23 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by PGSMSX101.gar.corp.intel.com (10.221.44.78) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 2 Jun 2015 11:27:21 +0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.109]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.180]) with mapi id 14.03.0224.002; Tue, 2 Jun 2015 11:27:20 +0800 From: "He, Shaopeng" To: "Liu, Jijiang" , Stephen Hemminger , Thomas Monjalon Thread-Topic: [dpdk-dev] [PATCH] fm10k: support XEN domain0 Thread-Index: AQHQju0R4dHaa4L0okWP5aPaWkV2Cp19MduAgANNWICAAix6AA== Date: Tue, 2 Jun 2015 03:27:19 +0000 Message-ID: References: <1431680162-13704-1-git-send-email-shaopeng.he@intel.com> <20150515165733.7d5571e3@urahara> <1ED644BD7E0A5F4091CF203DAFB8E4CC0575760E@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <1ED644BD7E0A5F4091CF203DAFB8E4CC0575760E@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH] fm10k: support XEN domain0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2015 03:27:25 -0000 Hi Stephen, Do you see any problem of preventing your patch of "xen: allow choosing dom= 0 support at runtime" into upcoming 2.1 release? It will be better that fm1= 0k's XEN support can base on your modifications, and I will rework this fm1= 0k patch. But in case your patch cannot make it into 2.1, to enable users to use fm10= k with XEN domain0 in next release, should we enable this function by using= current approach first? Thanks, --Shaopeng -----Original Message----- From: Liu, Jijiang=20 Sent: Monday, May 18, 2015 10:23 AM To: Stephen Hemminger; He, Shaopeng; Thomas Monjalon Cc: dev@dpdk.org Subject: RE: [dpdk-dev] [PATCH] fm10k: support XEN domain0 Hi guys, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger > Sent: Saturday, May 16, 2015 7:58 AM > To: He, Shaopeng > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] fm10k: support XEN domain0 >=20 > On Fri, 15 May 2015 16:56:02 +0800 > Shaopeng He wrote: >=20 > > fm10k was failing to run in XEN domain0, as the physical memory for=20 > > DMA should be allocated and translated in a different way for XEN=20 > > domain0. So > > rte_memzone_reserve_bounded() should be used for DMA memory=20 > > allocation, and rte_mem_phy2mch() should be used for DMA memory=20 > > address translation to support running fm10k PMD in XEN domain0. > > > > Signed-off-by: Shaopeng He >=20 > I agree with Thomas that this code has spread everywhere and should be=20 > in a common spot. >=20 > Also, we discovered as part of the Xen net-front driver that it should=20 > be a runtime determination, not a config option! I also agree that it should be in a common spot. But it had better to apply the following Stephen's patch first. If so, Sha= openg just use the common function in the patch, which would be good. =20 http://dpdk.org/ml/archives/dev/2015-March/014992.html