From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id B1120A2E1B for ; Tue, 3 Sep 2019 10:06:24 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D87991C25A; Tue, 3 Sep 2019 10:06:23 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 493201C23A for ; Tue, 3 Sep 2019 10:06:22 +0200 (CEST) Received: from mail-ua1-f69.google.com (mail-ua1-f69.google.com [209.85.222.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 96573811BF for ; Tue, 3 Sep 2019 08:06:21 +0000 (UTC) Received: by mail-ua1-f69.google.com with SMTP id k3so1990822uan.13 for ; Tue, 03 Sep 2019 01:06:21 -0700 (PDT) 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=CtdX9Db6aUK7q/wnHhMQjq5t/cD6Yo+zJmY7wV//Fz8=; b=GOpR0KZdQIPuSfJGUGogv+4GvWcjZ0g/Nyz2VaOJQTG1J7SGrLNwut4EgbvLrWArV/ /VmizKoO7EtLJAOIubqKs2KtOHrt9SF0TLKXwT0WxFHNTmie2eG2J2Qj9H7rlOfu3tJT Z/HSO0EH+T1s4Dph/+R7eZsITOhfsqL+NTflnyfRUUhziWt08yZoIbwrMcGDsc+tETsQ qYiJ6Uf/5K6NUWI2T/JVot/l0o+VQ1DFAWIXcpGoUBh+iDBmshn/Z3/7VIcx32kZv4yV Xgs2Gkpp74IxSg0+5dxtdbWR21X5Y8fgT4i+z9Aq4ItGoS6JC6rwmRw90RxdOU1VKx30 xnAA== X-Gm-Message-State: APjAAAUaXmDz0lupqxg71jnP8ZsPyuLb3/2u83Vv4PrlKWMmT7JSd1Es qx1LZ57hxfG7uHsScK8G0jb8gymgU0D/QKSPBJBpVKrcIeQZBqmyymi+GOkfBoHOo3v/gvQOReT JHpPIQ9/zJh8D0PI6buE= X-Received: by 2002:a67:f558:: with SMTP id z24mr17569771vsn.141.1567497980890; Tue, 03 Sep 2019 01:06:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqwmqqVzg6BDKaBSevEIxj/hyYpw449U2FXdk88BrjpDxtr0TCgFcGlV2nMMC5EcSQG9KRUNEDbvKJ/nUImX628= X-Received: by 2002:a67:f558:: with SMTP id z24mr17569762vsn.141.1567497980652; Tue, 03 Sep 2019 01:06:20 -0700 (PDT) MIME-Version: 1.0 References: <1566214919-32250-1-git-send-email-david.marchand@redhat.com> <1811fc39-c6ca-682e-2840-534078c9a7e4@intel.com> In-Reply-To: <1811fc39-c6ca-682e-2840-534078c9a7e4@intel.com> From: David Marchand Date: Tue, 3 Sep 2019 10:06:09 +0200 Message-ID: To: Ferruh Yigit Cc: dev Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH 00/11] Fixing log levels for dynamically loaded drivers X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Mon, Sep 2, 2019 at 4:17 PM Ferruh Yigit wrote: > > On 8/19/2019 12:41 PM, David Marchand wrote: > > All (but the Solarflare net driver) drivers currently do not care about > > the log level the user might have passed at init time. > > Is this comment for the shared libraries? > Because otherwise drivers set loglevel during initialization and init time > setting should be reflected to the logtypes before devices probed. Indeed, the issue is seen when building drivers as shared libraries. -- David Marchand