From: Heng Qi <hengqi@linux.alibaba.com>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, virtualization@lists.linux.dev,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Jason Wang <jasowang@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Simon Horman <horms@kernel.org>, Brett Creeley <bcreeley@amd.com>,
Ratheesh Kannoth <rkannoth@marvell.com>,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [PATCH net-next v8 0/4] ethtool: provide the dim profile fine-tuning channel
Date: Wed, 17 Apr 2024 16:04:17 +0800 [thread overview]
Message-ID: <29266e64-5810-417d-9a01-ad01e86a70d3@linux.alibaba.com> (raw)
In-Reply-To: <CAL+tcoAS81uW_aikoWrDhO-qF-aFD5rU4GsEAy2hHbC9ex2q5w@mail.gmail.com>
在 2024/4/17 下午2:52, Jason Xing 写道:
> On Wed, Apr 17, 2024 at 2:35 PM Heng Qi <hengqi@linux.alibaba.com> wrote:
>>
>>
>> 在 2024/4/17 上午10:53, Jason Xing 写道:
>>> Hello Jakub,
>>>
>>> On Wed, Apr 17, 2024 at 10:30 AM Jakub Kicinski <kuba@kernel.org> wrote:
>>>> On Wed, 17 Apr 2024 10:22:52 +0800 Heng Qi wrote:
>>>>> Have you encountered compilation problems in v8?
>>>> Yes, please try building allmodconfig:
>>>>
>>>> make allmodconfig
>>>> make ..
>>>>
>>>> there's many drivers using this API, you gotta build the full kernel..
>>>>
>>> About compiling the kernel, I would like to ask one question: what
>>> parameters of 'make' do you recommend just like the netdev/build_32bit
>>> [1] does?
>> Hi Jason,
>>
>> I founded and checked the use of nipa[1] made from Kuba today. I used
>> run.sh in the ./nipa/docker
>> directory locally to run full compilation.
>> If there are additional errors or warnings after applying our own
>> patches than before, we will be given
>> information in the results directory.
>>
>> [1] https://github.com/linux-netdev/nipa/tree/main
> Great! Thanks for the information:) I'll try it locally.
To update more information, I checked the source code of nipa.
All its test items are located at:
1. nipa/tests/patch, such as build_32bit, build_allmodconfig_war
2. nipa/tests/series, such as fixes_present
We can edit the "include" and "exclude" items of [tests] section
in the nipa/docker/nipa.config file to specify the specific items we
want to test.
Regards,
Heng
>
> Thanks,
> Jason
>
>> Thanks.
>>
>>> If I run the normal 'make' command without parameters, there is no
>>> warning even if the file is not compiled. If running with '-Oline -j
>>> 16 W=1 C=1', it will print lots of warnings which makes it very hard
>>> to see the useful information related to the commits I just wrote.
>>>
>>> I want to build and then print all the warnings which are only related
>>> to my patches locally, but I cannot find a good way :(
>>>
>>> [1]: https://netdev.bots.linux.dev/static/nipa/845020/13631720/build_32bit/stderr
>>>
>>> Thanks,
>>> Jason
prev parent reply other threads:[~2024-04-17 8:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 12:29 [PATCH net-next v8 0/4] ethtool: provide the dim profile fine-tuning channel Heng Qi
2024-04-16 12:29 ` [PATCH net-next v8 1/4] linux/dim: move useful macros to .h file Heng Qi
2024-04-16 12:29 ` [PATCH net-next v8 2/4] ethtool: provide customized dim profile management Heng Qi
2024-04-16 12:29 ` [PATCH net-next v8 3/4] virtio-net: refactor dim initialization/destruction Heng Qi
2024-04-16 12:29 ` [PATCH net-next v8 4/4] virtio-net: support dim profile fine-tuning Heng Qi
2024-04-17 0:38 ` [PATCH net-next v8 0/4] ethtool: provide the dim profile fine-tuning channel Jakub Kicinski
2024-04-17 2:22 ` Heng Qi
2024-04-17 2:29 ` Jakub Kicinski
2024-04-17 2:53 ` Jason Xing
2024-04-17 6:35 ` Heng Qi
2024-04-17 6:52 ` Jason Xing
2024-04-17 8:04 ` Heng Qi [this message]
Reply instructions:
You may reply publicly 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=29266e64-5810-417d-9a01-ad01e86a70d3@linux.alibaba.com \
--to=hengqi@linux.alibaba.com \
--cc=aleksander.lobakin@intel.com \
--cc=bcreeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jasowang@redhat.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).