<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>11e02702 - examples: fix pkg-config override</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#11e02702</link>
        <description>examples: fix pkg-config overrideMove pkg-config override to beginning in the Makefile to allowuse PKGCONF variable to detect the libdpdk availability.Fixes: fda34680eb9a (&quot;examples: remove legacy sections of makefiles&quot;)Cc: stable@dpdk.orgSigned-off-by: Jerin Jacob &lt;jerinj@marvell.com&gt;Acked-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Wed, 05 May 2021 14:25:25 +0000</pubDate>
        <dc:creator>Jerin Jacob &lt;jerinj@marvell.com&gt;</dc:creator>
    </item>
<item>
        <title>5a196330 - examples: warn about broken pkg-config</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#5a196330</link>
        <description>examples: warn about broken pkg-configSince the examples are designed to be built by end-users using Make, wecan detect and warn about broken pkg-config on the user&apos;s system as partof the build process.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Tue, 19 Jan 2021 13:03:24 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>bc8e3247 - examples: restore trace point</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#bc8e3247</link>
        <description>examples: restore trace pointBefore make removal, those examples were built with experimental flagfor tracepoints to be compiled in but the pkg-config part of thosemakefiles were missed.Fixes: 78d44153de8f (&quot;ethdev: add tracepoints&quot;)Cc: stable@dpdk.orgSigned-off-by: David Marchand &lt;david.marchand@redhat.com&gt;Acked-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Sat, 14 Nov 2020 09:05:33 +0000</pubDate>
        <dc:creator>David Marchand &lt;david.marchand@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>7157a9dc - examples: fix linking against specific drivers</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#7157a9dc</link>
        <description>examples: fix linking against specific driversSome example apps rely on driver-specific functionality and link explicitlyagainst those drivers. These apps need their makefiles updated to takeaccount of the renaming of the driver libs.Fixes: a20b2c01a7a1 (&quot;build: standardize component names and defines&quot;)Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Reviewed-by: David Marchand &lt;david.marchand@redhat.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Tue, 27 Oct 2020 17:19:53 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>5adbc4b8 - examples/vm_power: convert to pkg-config-based build</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#5adbc4b8</link>
        <description>examples/vm_power: convert to pkg-config-based buildConvert the makefiles to build using pkg-configrather than the old build system.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Thu, 03 Sep 2020 15:26:46 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>78d44153 - ethdev: add tracepoints</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#78d44153</link>
        <description>ethdev: add tracepointsAdd tracepoints at important and mandatory APIs for tracing support.Signed-off-by: Sunil Kumar Kori &lt;skori@marvell.com&gt;Acked-by: David Marchand &lt;david.marchand@redhat.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Wed, 22 Apr 2020 19:03:45 +0000</pubDate>
        <dc:creator>Sunil Kumar Kori &lt;skori@marvell.com&gt;</dc:creator>
    </item>
<item>
        <title>e9c65942 - examples: detect default build directory</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#e9c65942</link>
        <description>examples: detect default build directoryMost examples have in their makefiles a default RTE_TARGET directory to beused in case RTE_TARGET is not set. Rather than just using a hard-codeddefault, we can instead detect what the build directory is relative toRTE_SDK directory.This fixes a potential issue for anyone who continues to build using&quot;make install T=x86_64-native-linuxapp-gcc&quot; and skips setting RTE_TARGETexplicitly, instead relying on the fact that they were building in adirectory which corresponded to the example default path - which waschanged to &quot;x86_64-native-linux-gcc&quot; by commit 218c4e68c1d9 (&quot;mk: uselinux and freebsd in config names&quot;).Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Acked-by: Ferruh Yigit &lt;ferruh.yigit@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Wed, 27 Mar 2019 13:58:05 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>218c4e68 - mk: use linux and freebsd in config names</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#218c4e68</link>
        <description>mk: use linux and freebsd in config namesRather than using linuxapp and bsdapp everywhere, we can change things touse the, more readable, terms &quot;linux&quot; and &quot;freebsd&quot; in our build configs.Rather than renaming the configs we can just duplicate the existing oneswith the new names using symlinks, and use the new names exclusivelyinternally. [&quot;make showconfigs&quot; also only shows the new names to keep thelist short] The result is that backward compatibility is kept fully but anynew builds or development can be done using the newer names, i.e.  both&quot;make config T=x86_64-native-linuxapp-gcc&quot; and &quot;T=x86_64-native-linux-gcc&quot;work.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Wed, 06 Mar 2019 16:22:42 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>a63504a9 - examples/power: add JSON string handling</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#a63504a9</link>
        <description>examples/power: add JSON string handlingAdd JSON string handling to vm_power_manager for JSON strings receivedthrough the fifo. The format of the JSON strings are detailed in thenext patch, the vm_power_manager user guide documentation updates.This patch introduces a new dependency on Jansson, a C library forencoding, decoding and manipulating JSON data. To compile the sample appyou now need to have installed libjansson4 and libjansson-dev (these maybe named slightly differently depending on your Operating System)Signed-off-by: David Hunt &lt;david.hunt@intel.com&gt;Acked-by: Anatoly Burakov &lt;anatoly.burakov@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Wed, 17 Oct 2018 13:05:31 +0000</pubDate>
        <dc:creator>David Hunt &lt;david.hunt@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>4b1a631b - examples/vm_power: add oob monitoring functions</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#4b1a631b</link>
        <description>examples/vm_power: add oob monitoring functionsThis patch introduces the out-of-band (oob) core monitoringfunctions.The functions are similar to the channel manager functions.There are function to add and remove cores from thelist of cores being monitored. There is a function to initialisethe monitor setup, run the monitor thread, and exit the monitor.The monitor thread runs in it&apos;s own lcore, and is separatefunctionality to the channel monitor which is epoll based.THis thread is timer based. It loops through all monitored cores,calculates the branch ratio, scales up or down the core, thensleeps for an interval (~250 uS).The method it uses to read the branch counters is a pread on the/dev/cpu/x/msr file, so the &apos;msr&apos; kernel module needs to be loaded.Also, since the msr.h file has been made unavailable in recentkernels, we have #defines for the relevant MSRs included in thecode.The makefile has a switch for x86 and non-x86 platforms,and compiles stub function for non-x86 platforms.Signed-off-by: David Hunt &lt;david.hunt@intel.com&gt;Acked-by: Radu Nicolau &lt;radu.nicolau@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Fri, 13 Jul 2018 14:22:56 +0000</pubDate>
        <dc:creator>David Hunt &lt;david.hunt@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>99a968fa - examples/vm_power: add core list parameter</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#99a968fa</link>
        <description>examples/vm_power: add core list parameterAdd in the &apos;-l&apos; command line parameter (also --core-list)So the user can now pass --corelist=4,6,8-10 and it willexpand out to 4,6,8,9,10 using the parse function providedin parse.c (parse_set).This list of cores is then used to enable out-of-band monitoringto scale up and down these cores based on the ratio of branchhits versus branch misses. The ratio will be low when a pollloop is spinning with no packets being received, so the frequencywill be scaled down.Also , as part of this change, we introduce a core_info structwhich keeps information on each core in the system, and whetherwe&apos;re doing out of band monitoring on them.Signed-off-by: David Hunt &lt;david.hunt@intel.com&gt;Acked-by: Radu Nicolau &lt;radu.nicolau@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Fri, 13 Jul 2018 14:22:55 +0000</pubDate>
        <dc:creator>David Hunt &lt;david.hunt@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>fa47405c - ethdev: remove experimental flag of ports enumeration</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#fa47405c</link>
        <description>ethdev: remove experimental flag of ports enumerationThe basic operations for ports enumeration should not beconsidered as experimental in DPDK 18.05.The iterator RTE_ETH_FOREACH_DEV was introduced in DPDK 17.05.It uses the function the rte_eth_find_next_owned_by() to getonly ownerless ports. Its API can be considered stable.So the flag experimental is removed from rte_eth_find_next_owned_by().The flag experimental is removed from rte_eth_dev_count_avail()which is the new name of the old function rte_eth_dev_count().The flag experimental is set to rte_eth_dev_count_total()in the .c file for consistency with the declaration in the .h file.A lot of internal applications are fixed to not allow experimental API.Fixes: 8728ccf37615 (&quot;fix ethdev ports enumeration&quot;)Fixes: d9a42a69febf (&quot;ethdev: deprecate port count function&quot;)Fixes: e70e26861eaf (&quot;net/mvpp2: fix build&quot;)Signed-off-by: Thomas Monjalon &lt;thomas@monjalon.net&gt;Tested-by: David Marchand &lt;david.marchand@6wind.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Tue, 24 Apr 2018 02:15:11 +0000</pubDate>
        <dc:creator>Thomas Monjalon &lt;thomas@monjalon.net&gt;</dc:creator>
    </item>
<item>
        <title>8728ccf3 - fix ethdev ports enumeration</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#8728ccf3</link>
        <description>fix ethdev ports enumerationSome DPDK applications wrongly assume these requirements:    - no hotplug, i.e. ports are never detached    - all allocated ports are available to the applicationSuch application iterates over ports by its own mean.The most common pattern is to request the port count andassume ports with index in the range [0..count[ can be used.There are three consequences when using such wrong design:    - new ports having an index higher than the port count won&apos;t be seen    - old ports being detached (RTE_ETH_DEV_UNUSED) can be seen as ghosts    - failsafe sub-devices (RTE_ETH_DEV_DEFERRED) will be seen by the applicationSuch mistake will be less common with growing hotplug awareness.All applications and examples inside this repository - except testpmd -must be fixed to use the iterator RTE_ETH_FOREACH_DEV.Signed-off-by: Thomas Monjalon &lt;thomas@monjalon.net&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Thu, 05 Apr 2018 15:33:20 +0000</pubDate>
        <dc:creator>Thomas Monjalon &lt;thomas@monjalon.net&gt;</dc:creator>
    </item>
<item>
        <title>22119c45 - examples: use pkg-config in makefiles</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#22119c45</link>
        <description>examples: use pkg-config in makefilesChange the example app Makefiles to query if DPDK is installed andregistered using pkg-config. If so, build directly using pkg-config info,otherwise fall back to using the original build system with RTE_SDK andRTE_TARGETThis commit changes the makefiles for the basic examples, i.e. those whichdo not have multiple subdirectories underneath the main examples dir.Examples not covered are:* ethtool* multi_process* performance-thread* quota_watermark* netmap_compat* server_node_efd* vm_power_managerSigned-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Reviewed-by: Luca Boccassi &lt;bluca@debian.org&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Mon, 09 Oct 2017 13:13:16 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>0eba4ade - examples: put app name and sources at top of makefiles</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#0eba4ade</link>
        <description>examples: put app name and sources at top of makefilesReorder the text in the makefiles, so that the app name and the sourcefiles are listed first. This then will allow them to be shared later in acombined makefile building with pkg-config and RTE_SDK-based build system.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;Reviewed-by: Luca Boccassi &lt;bluca@debian.org&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Mon, 25 Sep 2017 16:28:49 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>3998e2a0 - examples: use SPDX tag for Intel copyright files</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#3998e2a0</link>
        <description>examples: use SPDX tag for Intel copyright filesReplace the BSD license header with the SPDX tag for fileswith only an Intel copyright on them.Signed-off-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Tue, 19 Dec 2017 15:49:02 +0000</pubDate>
        <dc:creator>Bruce Richardson &lt;bruce.richardson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>f14791a8 - examples/vm_power_mgr: add policy to channels</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#f14791a8</link>
        <description>examples/vm_power_mgr: add policy to channelsSigned-off-by: Nemanja Marjanovic &lt;nemanja.marjanovic@intel.com&gt;Signed-off-by: Rory Sexton &lt;rory.sexton@intel.com&gt;Signed-off-by: David Hunt &lt;david.hunt@intel.com&gt;Reviewed-by: Santosh Shukla &lt;santosh.shukla@caviumnetworks.com&gt;Acked-by: Konstantin Ananyev &lt;konstantin.ananyev@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Wed, 11 Oct 2017 16:18:51 +0000</pubDate>
        <dc:creator>Rory Sexton &lt;rory.sexton@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>e5140f52 - examples/vm_power_manager: fix libvirt dependency check</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#e5140f52</link>
        <description>examples/vm_power_manager: fix libvirt dependency checkvm_power_manager utilize libvirt API virDomainGetVcpuPinInfo toretrieve domU vcpu information. This API is implemented from version 0.9.3.Suse11 SP3 32bit default libvirt version is 0.8.8.examples/vm_power_manager/channel_manager.c:channel_manager.c:117:3: error: implicit declaration of function&apos;virDomainGetVcpuPinInfo&apos;Check and skip it from examples or raise an error when trying to compilewithout libvirt or with a too old libvirt.Fixes: e8ae9b662 (&quot;examples/vm_power: channel manager and monitor in host&quot;)Signed-off-by: Marvin Liu &lt;yong.liu@intel.com&gt;Signed-off-by: Thomas Monjalon &lt;thomas.monjalon@6wind.com&gt;Acked-by: Bruce Richardson &lt;bruce.richardson@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Mon, 11 Apr 2016 08:50:31 +0000</pubDate>
        <dc:creator>Marvin Liu &lt;yong.liu@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>2e099bc5 - examples/vm_power: fix split of compiler and linker options</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#2e099bc5</link>
        <description>examples/vm_power: fix split of compiler and linker optionsThe argument -lvirt is a linker parameter, not a CFLAG.Signed-off-by: Olivier Matz &lt;olivier.matz@6wind.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Wed, 17 Dec 2014 12:55:24 +0000</pubDate>
        <dc:creator>Olivier Matz &lt;olivier.matz@6wind.com&gt;</dc:creator>
    </item>
<item>
        <title>8db653ff - examples/vm_power: vm power management application</title>
        <link>http://172.16.0.5:8080/history/dpdk/examples/vm_power_manager/Makefile#8db653ff</link>
        <description>examples/vm_power: vm power management applicationFor launching CLI thread and Monitor thread and initialisingresources.Requires a minimum of two lcores to run, additional cores specified by eal coremask are not used.Signed-off-by: Alan Carew &lt;alan.carew@intel.com&gt;Signed-off-by: Pablo de Lara &lt;pablo.de.lara.guarch@intel.com&gt;

            List of files:
            /dpdk/examples/vm_power_manager/Makefile</description>
        <pubDate>Tue, 25 Nov 2014 16:18:05 +0000</pubDate>
        <dc:creator>Alan Carew &lt;alan.carew@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
