DPDK CI discussions
 help / color / Atom feed
From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	"ci@dpdk.org" <ci@dpdk.org>,  "Yao, Lei A" <lei.a.yao@intel.com>
Cc: "Xu, Qian Q" <qian.q.xu@intel.com>
Subject: Re: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May 7th
Date: Wed, 8 May 2019 02:08:04 +0000
Message-ID: <82F45D86ADE5454A95A89742C8D1410E40457018@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB78A6C32@IRSMSX108.ger.corp.intel.com>

> - For Intel, after binding drivers to VFIO for OVS tests, can't bind back to
> I40E/IXGBE. Jeremy will send details in email.

+ Lei in the loop. Lei, any comments for it? Thx. 

> -----Original Message-----
> From: ci [mailto:ci-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim
> Sent: Tuesday, May 7, 2019 9:27 PM
> To: ci@dpdk.org
> Subject: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday May 7th
> 
> Jeremy is working on setting up the OVS tests on the Intel and Mellanox
> machines. Issues have been encountered with both setups.
> - For Intel, after binding drivers to VFIO for OVS tests, can't bind back to
> I40E/IXGBE. Jeremy will send details in email.
> - For Mellanox, having issues trying to set up using VFIO. Jeremy will follow up
> with Ali and Thomas.
> 
> Testing is currently paused while Ali updates the Mellanox firmware. This will be
> done today and tests should restart after that.
> 
> There's a security issue if patches contains malicious code. Tests run on all
> servers with root permissions. Possible solutions include: stop running tests as
> root, run tests in containers, implement static analysis of patches prior to
> running. Ali will investigate and make a recommendation.

  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 13:27 O'Driscoll, Tim
2019-05-08  2:08 ` Xu, Qian Q [this message]
2019-05-08  2:22   ` Yao, Lei A
2019-05-08 20:07     ` Jeremy Plsek
2019-05-09  8:37       ` Xu, Qian Q

Reply instructions:

You may reply publically 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=82F45D86ADE5454A95A89742C8D1410E40457018@shsmsx102.ccr.corp.intel.com \
    --to=qian.q.xu@intel.com \
    --cc=ci@dpdk.org \
    --cc=lei.a.yao@intel.com \
    --cc=tim.odriscoll@intel.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

DPDK CI discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/ public-inbox