From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id C4314A04EF;
	Mon, 25 May 2020 09:52:38 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id E38951D6F1;
	Mon, 25 May 2020 09:52:37 +0200 (CEST)
Received: from mail-il1-f193.google.com (mail-il1-f193.google.com
 [209.85.166.193]) by dpdk.org (Postfix) with ESMTP id 20E3C1D6A4
 for <dev@dpdk.org>; Mon, 25 May 2020 09:52:37 +0200 (CEST)
Received: by mail-il1-f193.google.com with SMTP id w18so16505224ilm.13
 for <dev@dpdk.org>; Mon, 25 May 2020 00:52:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=CgSAFk+1+hpcLALkY0Z0zctMs99tjYYi5KJzqCAl+FA=;
 b=R3j2s5xleMaWSnYi2sX7ICrqQ87wgv7GAG0GtBz+DsCHkC1JqPN1Q+8ghcSG6ci6y7
 sQMUW7YJ4LRN0mkLoHXHbDLGgX/k6g991UxkGOxO1uRdCWobxXkRa6VEBScQdogERvs5
 AiBCM+8mjLJfUJLejbt3ZbclwoHVPwHMAjtbQGOqHEW7cQDdwPcskXp+3cgUM9QSViov
 MYetRjG+oz9qkrw5TwTQbUmz8tk8DwjpccAYp8wShrXngimkrBXKH3qrjDbLJZx6CUBo
 MDk0LnTWdT7EWXe49P9rMr/mgB47m0Q0fm6ezywreiGdyV6he/dRHVnJXA7lvlnrBG9M
 dtTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=CgSAFk+1+hpcLALkY0Z0zctMs99tjYYi5KJzqCAl+FA=;
 b=SeqdmxjFhA+7D7PMZPCbVOrochKSoHaf+Tm/xLckn7jvv+460yGQrm4JJwMSF0PoSv
 D77tNdYrLzK6jL5IYOCPkXVYMsH67IGVqkBiO213Bt6k5a4wcjznTunizwiudrKRL6/l
 T6/RvIoI2pmfojcjRD+vMYJXyqI6fpW42iP1pSyDDmNQ9Su0XZ7Dk2VgkBEgprqsuH2r
 nCD7j1fjKwsyYd5WAzRqZtYhVQw+VM6jKnL8gw+C+snrP5nag58FxEfOMJIj+Z1Mor1V
 UVMM84egvpTVEcb/UsOYlnawWmGqmC9fOGX4BRV/9V+SQ21GgjEKKXTD2Hu4acWIRg6l
 SWIw==
X-Gm-Message-State: AOAM532q62XtS6xkNnpFoUSHFXJI0su+H9wmrJE2w3ekyCFPSuYM4klA
 7yu/HJbRJLJNEiGHqOtjqlVx0jvTUAUVUttwKXE=
X-Google-Smtp-Source: ABdhPJyM4lyc28qSO125LTXkcWRJKbFbox7Ag+bO+V4Xw42+TmsIBN54F41EpAclEjcG80F2U0D2uyOTQUySw+L0EWk=
X-Received: by 2002:a92:d188:: with SMTP id z8mr22066806ilz.60.1590393156244; 
 Mon, 25 May 2020 00:52:36 -0700 (PDT)
MIME-Version: 1.0
References: <20200523140750.3967959-1-jerinj@marvell.com>
 <20200525054606.4187060-1-jerinj@marvell.com>
 <25d32839-a0e9-5d47-1354-a330c5d49831@redhat.com>
In-Reply-To: <25d32839-a0e9-5d47-1354-a330c5d49831@redhat.com>
From: Jerin Jacob <jerinjacobk@gmail.com>
Date: Mon, 25 May 2020 13:22:20 +0530
Message-ID: <CALBAE1NODqvZS3Dwe=6D0qFOrAZHLUj8ccVFBkTcFfKSE7=OeA@mail.gmail.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: Jerin Jacob <jerinj@marvell.com>, dpdk-dev <dev@dpdk.org>,
 Ray Kinsella <mdr@ashroe.eu>, 
 Neil Horman <nhorman@tuxdriver.com>, John McNamara <john.mcnamara@intel.com>, 
 Marko Kovacevic <marko.kovacevic@intel.com>,
 Thomas Monjalon <thomas@monjalon.net>, 
 David Marchand <david.marchand@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [dpdk-dev] [PATCH v2] doc: announce the removal of legacy
	virtio support
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Mon, May 25, 2020 at 1:03 PM Maxime Coquelin
<maxime.coquelin@redhat.com> wrote:
>
> Hi Jerrin,

Hi Maxime,

>
> I think what was agreed wasn't to remove Legacy Virtio support,
> but instead remove support for probing legacy Virtio devices when they
> are not bound to any Kernel drivers.
>
> It should still be possible to use these legacy Virtio devices when
> bound to VFIO or UIO.

I was not aware that legacy virtio can be used with VFIO or UIO.
I will send the v3.

>
> Regards,
> Maximle
>
> On 5/25/20 7:46 AM, jerinj@marvell.com wrote:
> > From: Jerin Jacob <jerinj@marvell.com>
> >
> > The legacy virtio feature is not architecture agnostics.
> > It relies on x86 IO port scheme support for its working.
> >
> > The legacy virtio is only the consumer of RTE_KDRV_NONE in DPDK PCI
> > subsystem. Legacy virtio removal will also optimize DPDK PCI enumeration
> > management as it does not need to probe RTE_KDRV_NONE based
> > devices anymore.
> >
> > Legacy virtio feature removal is planned in the v20.11 release.
> >
> > More details at http://patches.dpdk.org/patch/69351/
> >
> > Cc: maxime.coquelin@redhat.com
> > Cc: david.marchand@redhat.com
> > Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> > ---
> >  doc/guides/rel_notes/deprecation.rst | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> > index cf8b1eb7b..79a03432c 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -107,3 +107,11 @@ Deprecation Notices
> >    Python 2 support will be completely removed in 20.11.
> >    In 20.08, explicit deprecation warnings will be displayed when running
> >    scripts with Python 2.
> > +
> > +* virtio: The legacy virtio feature is not architecture agnostics.
> > +  It relies on x86 IO port scheme support for its working.
> > +  The legacy virtio is only the consumer of RTE_KDRV_NONE in DPDK PCI subsystem.
> > +  Legacy virtio removal will also optimize DPDK PCI enumeration management as
> > +  it does not need to probe RTE_KDRV_NONE based devices anymore.
> > +  Legacy virtio feature removal is planned in the v20.11 release.
> > +  More details at http://patches.dpdk.org/patch/69351/
> >
>