Signed-off-by: Jason Wang
---
include/uapi/linux/virtio_config.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/uapi/linux/virtio_config.h
b/include/uapi/linux/virtio_config.h
index 1196e1c1d4f6..2698e069ed9e 100644
--- a/include/uapi/linux/virtio_config.h
+++
Hi:
This series implement basic in order feature support for
vhost_net. This feature requires both driver and device to use
descriptors in order which can simplify the implementation and
optimizaton for both side. The series also implement a simple
optimization that avoid read available ring.
This makes vhost_net to support in order feature. This is as simple as
use datacopy path when it was negotiated. An alternative is not to
advertise in order when zerocopy is enabled which tends to be
suboptimal consider zerocopy may suffer from e.g HOL issues.
Signed-off-by: Jason Wang
---
Device use descriptors table in order, so there's no need to read
index from available ring. This eliminate the cache contention on
available ring completely.
Virito-user + vhost_kernel + XDP_DROP on 2.60GHz Broadwell
Before /After
SMAP on: 4.8Mpps 5.3Mpps(+10%)
SMAP off: 6.6Mpps
Add support to read the voltage look up table and populate OPP for all
corresponding CPUS for consumers like the energy model could use the
frequency and voltage from the OPP tables.
Tested-by: Matthias Kaehlcke
Signed-off-by: Taniya Das
---
drivers/cpufreq/qcom-cpufreq-hw.c | 33
On 1/8/2019 5:32 AM, Matthias Kaehlcke wrote:
Hi Taniya.
On Mon, Dec 24, 2018 at 12:29:18AM +0530, Taniya Das wrote:
Could you help validating with the patch below?
...
diff --git a/drivers/cpufreq/qcom-cpufreq-hw.c
b/drivers/cpufreq/qcom-cpufreq-hw.c
index 7559b87..23338b2 100644
---
Hi Mason,
On Tue, Jan 8, 2019 at 5:17 AM Mason Yang wrote:
> Add a driver for Renesas R-Car Gen3 RPC-IF SPI controller.
>
> Signed-off-by: Mason Yang
Thanks for your patch!
> --- /dev/null
> +++ b/drivers/spi/spi-renesas-rpc.c
> +static void rpc_spi_mem_set_prep_op_cfg(struct spi_device
On 09/01/2019 18:25, Benjamin Herrenschmidt wrote:
> On Wed, 2019-01-09 at 17:32 +1100, Alexey Kardashevskiy wrote:
>> I have just moved the "Mellanox Technologies MT27700 Family
>> [ConnectX-4]" from garrison to firestone machine and there it does not
>> produce an EEH, with the same kernel
"user_buf->length" is in user space, and copied in twice. The second
copy is after it passes the security check. If a user program races to
change user_buf->length in user space, the data fetched in the second
copy may invalidate the security check. The fix avoids the double-fetch
issue by using
On 2019/1/7, 9:41 PM, "Brian Starkey" wrote:
Hi James,
A few minor comments.
On Mon, Dec 24, 2018 at 08:58:46AM +, james qian wang (Arm Technology
China) wrote:
> D71 consists of a number of Register Blocks, every Block controls a
> specific HW function,
On 09/01/2019 18:24, Benjamin Herrenschmidt wrote:
> On Wed, 2019-01-09 at 15:53 +1100, Alexey Kardashevskiy wrote:
>> "A PCI completion timeout occurred for an outstanding PCI-E transaction"
>> it is.
>>
>> This is how I bind the device to vfio:
>>
>> echo vfio-pci >
On Wed, Jan 09, 2019 at 08:05:21AM +0100, Stephan Mueller wrote:
> Am Mittwoch, 9. Januar 2019, 07:58:28 CET schrieb James Bottomley:
>
> Hi James,
>
> > On Wed, 2019-01-09 at 07:45 +0100, Stephan Mueller wrote:
> > > Am Mittwoch, 9. Januar 2019, 01:44:31 CET schrieb James Bottomley:
> > >
> >
Adding Peter,
is this the same problem that you reported me today?
Can you test Zha Bins patch?
Christian
On 08.01.2019 09:07, Zha Bin wrote:
> The vsock core only supports 32bit CID, but the Virtio-vsock spec define
> CID (dst_cid and src_cid) as u64 and the upper 32bits is reserved as
> zero.
Le mar. 8 janv. 2019 à 20:30, Sam Ravnborg a écrit :
I just notice the a typo in the title of the commit message reply ->rely ?
>
> drmP.h was the only header file in the past and a lot
> of files rely on that drmP.h defines everything.
> The goal is to one day to delete drmP.h and
> as a step
This patch adds the device nodes of ARM Performance Monitor Uint
for mt8173.
Signed-off-by: Seiya Wang
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
On Tue, Jan 08, 2019 at 02:24:53PM -0500, Sasha Levin wrote:
> From: Nikolaj Fogh
>
> [ Upstream commit 6abd837104a3a8e1cda64fc4d7675f6c3ece9d8b ]
>
> Improve baud-rate generation by using rounding-to-closest instead of
> truncation in divisor calculation.
>
> Results have been verified by
The NXP's Vybryd vf610 can work as a SPI slave device (the CS and clock
signals are provided by master).
It is possible to specify a single device to work in that mode. As we do
use DMA for transferring data, the RX channel must be prepared for
incoming data.
Moreover, in slave mode we just set a
On Wed, Jan 2, 2019 at 3:08 PM Dmitry Vyukov wrote:
>
> On Fri, Dec 28, 2018 at 10:09 PM Linus Torvalds
> wrote:
> >
> > On Fri, Dec 28, 2018 at 1:43 AM Dmitry Vyukov wrote:
> > >
> > > > Nobody reads the kernel mailing list directly - there's just too much
> > > > traffic.
> > >
> > > As the
On 1/8/2019 5:43 PM, Kalle Valo wrote:
Kangjie Lu writes:
usb_register() may fail, so let's check its status and issue an error
message if it fails.
Signed-off-by: Kangjie Lu
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c | 6 +-
The title prefix should be "brcmfmac: "
On 2019-01-09 13:07, Michal Hocko wrote:
On Wed 09-01-19 11:28:52, Arun KS wrote:
On 2019-01-08 23:43, Michal Hocko wrote:
> On Tue 08-01-19 09:56:09, Alexander Duyck wrote:
> > On Fri, 2019-01-04 at 10:31 +0530, Arun KS wrote:
> [...]
> > > static int online_pages_range(unsigned long
The snd_byt_cht_es8316_mc_remove() use the platform drvdata as a type
of 'struct byt_cht_es8316_private', but snd_byt_cht_es8316_mc_probe() set
it to 'struct snd_soc_card', fix to pass correct platform drvdata to
platform_set_drvdata().
Fixes: 0d3e91da0750 ("ASoC: Intel: bytcht_es8316: Add
On 2019-01-08 13:19:47 [-0600], Scott Wood wrote:
> > We
> > do it for rtmutex because !RT does it for mutex.
> > Now I can't remember why this was skipped for a rw_sem since it is
> > performed for !RT as part of the schedule() invocation.
>
> Without this we were seeing XFS hangs on our
On Tue, Jan 08, 2019 at 06:11:11PM -0800, r...@google.com wrote:
> From: Roman Kiryanov
>
> A driver for the Goldfish Android emulator that occupies
> address space to use it with the memory sharing device
> on the QEMU side. The memory sharding device allocates
> subranges and populate them
On Tue, Jan 08, 2019 at 10:21:52AM -0600, Gustavo A. R. Silva wrote:
> One of the more common cases of allocation size calculations is finding the
> size of a structure that has a zero-sized array at the end, along with memory
> for some number of elements for that array. For example:
>
> struct
Thanks Mark for review.
On 1/7/2019 11:57 PM, Mark Brown wrote:
On Mon, Dec 24, 2018 at 02:32:13PM +0530, Rohit kumar wrote:
From: Ajit Pandey
Platform DAI component probe is not called if it is not
present in component list during sound card registration.
Check if component is registered
On Tue, 8 Jan 2019 16:30:24 -0600
Bjorn Helgaas wrote:
> Hi,
>
> I want to update the PCI Kconfig labels so they're more consistent and
> useful to users, something like the patch below. IIUC, the items
> below are all IBM-related; please correct me if not.
>
> I'd also like to expand (or
From: Sri Krishna chowdary
kmemleak detects allocated objects as leaks if not accessed for
default scan time. The memory allocated using avc_alloc_node
is freed using rcu mechanism when nodes are reclaimed or on
avc_flush. So, there is no real leak here and kmemleak_scan
detects it as a leak
The SSD130x OLED display reset signal is active low. Now the reset
sequence is implemented in such a way that users are forced to
define reset-gpios as GPIO_ACTIVE_HIGH in DT to make the reset work.
Do not hard code the active-low sequence into the driver but instead
allow the user to specify the
The reset signal of the SSD1306 OLED display is actually active-low.
Adapt the DT to reflect the real world.
Reviewed-by: Rob Herring
Acked-by: Alexandre Belloni
Signed-off-by: Michal Vokáč
---
Changes in v2 resend:
- Add Acked-by from Alexandre.
Changes from v1:
- Add R-by from Rob
Hi all,
this is my third attempt to fix the ssd1307fb OLED driver reset. In the
second attempt [1] Rob suggested to take different aproach. That is to
apply what was originaly part of the first round and eventually merged
but reverted later on [2][3].
The last patch in this series is a fixup for
There was a bug in reset signal generation in ssd1307fb OLED driver.
The display needs an active-low reset signal but the driver produced
the correct sequence only if the GPIO used for reset was specified as
GPIO_ACTIVE_HIGH.
Now as the OLED driver is fixed it is also necessarry to implement
a
Andrea Arcangeli writes:
> Hello,
>
> On Tue, Jan 08, 2019 at 10:21:09AM +0530, Aneesh Kumar K.V wrote:
>> @@ -187,41 +149,25 @@ static long mm_iommu_do_alloc(struct mm_struct *mm,
>> unsigned long ua,
>> goto unlock_exit;
>> }
>>
>> +ret = get_user_pages_cma_migrate(ua,
The reset-active-low property has been removed brom the binding a while
ago. So remove it from the examples as well.
Fixes: 519b4db ("fbdev: ssd1307fb: Remove reset-active-low from the DT binding
document")
Reviewed-by: Rob Herring
Reviewed-by: Alexandre Belloni
Signed-off-by: Michal Vokáč
On Wed 09-01-19 13:58:50, Arun KS wrote:
> On 2019-01-09 13:07, Michal Hocko wrote:
> > On Wed 09-01-19 11:28:52, Arun KS wrote:
> > > On 2019-01-08 23:43, Michal Hocko wrote:
> > > > On Tue 08-01-19 09:56:09, Alexander Duyck wrote:
> > > > > On Fri, 2019-01-04 at 10:31 +0530, Arun KS wrote:
> > >
Andrew Morton writes:
> On Tue, 8 Jan 2019 10:21:06 +0530 "Aneesh Kumar K.V"
> wrote:
>
>> ppc64 use CMA area for the allocation of guest page table (hash page table).
>> We won't
>> be able to start guest if we fail to allocate hash page table. We have
>> observed
>> hash table allocation
On Tue, Jan 08, 2019 at 11:43:19PM -0500, Qian Cai wrote:
> ==
> WARNING: possible circular locking dependency detected
> 5.0.0-rc1+ #60 Not tainted
> --
> read_all/7952 is trying to acquire
Hello,
Here are four various fixes for venus driver.
Comments are welcome!
regards,
Stan
Stanimir Varbanov (4):
venus: firmware: check fw size against DT memory region size
venus: core: corect maximum hardware load for sdm845
venus: core: correct frequency table for sdm845
venus:
This corrects clock frequency table rates to be in sync
with video clock controller frequency table.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/core.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git
The zero timestap is really a valid so not sure why I discarded it. Fix
that mistake by drop the code which checks for zero timestamp.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/helpers.c | 3 ---
1 file changed, 3 deletions(-)
diff --git
By historical reasons we defined firmware memory size to be 6MB even
that the firmware size for all supported Venus versions is 5MBs. Correct
that by compare the required firmware size returned from mdt loader and
the one provided by DT reserved memory region. We proceed further if the
required
This corects maximum hardware load constant in per SoC resources
for sdm845 aka Venus v4.
Signed-off-by: Stanimir Varbanov
---
drivers/media/platform/qcom/venus/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/platform/qcom/venus/core.c
On 2019-01-08 18:39:15 [-0600], Scott Wood wrote:
> On Thu, 2018-12-13 at 17:44 +0100, Sebastian Andrzej Siewior wrote:
> > Commit "x86/mm/pat: Disable preemption around __flush_tlb_all()" added a
> > warning if __flush_tlb_all() is invoked in preemptible context. On !RT
> > the warning does not
From: Ajit Pandey
DAI component probe is not called if it is not present
in component list during sound card registration.
Check if component is available in component list for
platform and cpu dai before soundcard registration.
Signed-off-by: Ajit Pandey
Signed-off-by: Rohit kumar
---
This is a pure cleanup patch, it doesn't affect runtime.
On Tue, Jan 08, 2019 at 02:25:24PM -0500, Sasha Levin wrote:
> From: Mauro Carvalho Chehab
>
> [ Upstream commit e4d7b113fdccde1acf8638c5879f2a450d492303 ]
>
> A common mistake is to assume that initializing a var with:
> struct
FYI, we noticed the following commit (built with gcc-7):
commit: 3ad20fe393b31025bebfc2d76964561f65df48aa ("binder: implement binderfs")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
in testcase: trinity
with following parameters:
runtime: 300s
Hi Corentin,
Thanks for the review,
Please find my response inline.
> -Original Message-
> From: Corentin Labbe [mailto:clabbe.montj...@gmail.com]
> Sent: Monday, January 7, 2019 3:43 PM
> To: Kalyani Akula
> Cc: herb...@gondor.apana.org.au; da...@davemloft.net; linux-
>
On 09-01-19, 13:37, Taniya Das wrote:
> @@ -98,6 +107,8 @@ static int qcom_cpufreq_hw_read_lut(struct device *dev,
You are only using this "dev" parameter for dev_dbg(), instead of that
pass cpu_dev pointer.
> table[i].frequency = CPUFREQ_ENTRY_INVALID;
> }
On Tue, 08 Jan 2019 09:40:06 -0700
Alex Williamson wrote:
> The below referenced commit adds a test for integer overflow, but in
> doing so prevents the unmap ioctl from ever including the last page of
> the address space. Subtract one to compare to the last address of the
> unmap to avoid the
On 09.01.2019 00:08, Uwe Kleine-König wrote:
> On Tue, Jan 08, 2019 at 09:21:34AM +, claudiu.bez...@microchip.com wrote:
>> Hi Uwe,
>>
>> On 08.01.2019 00:10, Uwe Kleine-König wrote:
>>> Hello Claudiu,
>>>
>>> On Mon, Jan 07, 2019 at 09:30:55AM +, claudiu.bez...@microchip.com
>>> wrote:
Changes in v10:
* Updated level bindings to include opp-level as an
optional property using operating-points-v2, no new
compatible for the OPP table
* Updated the dev_pm_opp_get_level() helper as per
suggestions from Viresh
Changes in v9:
* Updated qcom-opp bindings to be generic and usable
On some SoCs (especially from Qualcomm and MediaTek) an OPP
node needs to describe an additional level/corner value
that is then communicated to a remote microprocessor by the CPU, which
then takes some actions (like adjusting voltage values across variousi
rails) based on the value passed.
Add
Add rpmpd device node and its OPP table
Signed-off-by: Rajendra Nayak
Signed-off-by: Viresh Kumar
Reviewed-by: Ulf Hansson
Reviewed-by: Stephen Boyd
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 34 +++
1 file changed, 34 insertions(+)
diff --git
Add DT bindings to describe the rpm/rpmh power domains found on Qualcomm
Technologies, Inc. SoCs. These power domains communicate a performance
state to RPM/RPMh, which then translates it into corresponding voltage on a
PMIC rail.
Signed-off-by: Rajendra Nayak
Signed-off-by: Viresh Kumar
Now that the OPP bindings are updated to include an optional
'opp-level' property, add support to parse it from device tree
and store it as part of dev_pm_opp structure.
Also add and export an helper 'dev_pm_opp_get_level()' that can be
used to get the level value read from device tree when
The Power domains for corners just pass the performance state set by the
consumers to the RPM (Remote Power manager) which then takes care
of setting the appropriate voltage on the corresponding rails to
meet the performance needs.
We add all power domain data needed on msm8996 here. This driver
Add support for the .set_performace_state() and .opp_to_performance_state()
callbacks in the rpmpd driver.
Signed-off-by: Rajendra Nayak
Signed-off-by: Viresh Kumar
Reviewed-by: Ulf Hansson
Reviewed-by: Stephen Boyd
---
drivers/soc/qcom/rpmpd.c | 35 +++
1
Specify the active + sleep and active-only MX power domains as
the parents of the corresponding CX power domains. This will ensure that
performance state requests on CX automatically generate equivalent requests
on MX power domains.
This is used to enforce a requirement that exists for various
The RPMh power domain driver aggregates the corner votes from various
consumers for the ARC resources and communicates it to RPMh.
With RPMh we use 2 different numbering space for corners, one used
by the clients to express their performance needs, and another used
to communicate to RPMh
Add the DT node for the rpmhpd powercontroller.
Signed-off-by: Rajendra Nayak
Acked-by: Viresh Kumar
Reviewed-by: Stephen Boyd
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 51
1 file changed, 51 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
calculate_sizes() could be called in several places
like (red_zone/poison/order/store_user)_store() while
random_seq remains unchanged.
If random_seq is not NULL in calculate_sizes(), re-randomize it.
Signed-off-by: Peng Wang
---
mm/slub.c | 9 +
1 file changed, 9 insertions(+)
diff
On 09-01-19, 14:34, Rajendra Nayak wrote:
> On some SoCs (especially from Qualcomm and MediaTek) an OPP
> node needs to describe an additional level/corner value
> that is then communicated to a remote microprocessor by the CPU, which
> then takes some actions (like adjusting voltage values across
> One of the more common cases of allocation size calculations is finding the
> size of a structure that has a zero-sized array at the end, along with memory
> for some number of elements for that array. For example:
>
> struct foo {
> int stuff;
> void *entry[];
> };
...
>
Hi,
On 02.01.2019 0:39, Jiri Olsa wrote:
> On Mon, Dec 24, 2018 at 03:23:13PM +0300, Alexey Budankov wrote:
>
> SNIP
>
>> @@ -2143,6 +2152,8 @@ int cmd_record(int argc, const char **argv)
>> if (verbose > 0)
>> pr_info("nr_cblocks: %d\n", rec->opts.nr_cblocks);
>>
>> +
Hi,
On 02.01.2019 0:39, Jiri Olsa wrote:
> On Mon, Dec 24, 2018 at 03:24:36PM +0300, Alexey Budankov wrote:
>>
>> Allocate and bind AIO user space buffers to the memory nodes
>> that mmap kernel buffers are bound to.
>>
>> Signed-off-by: Alexey Budankov
>> ---
>> Changes in v2:
>> - implemented
Hi,
On 02.01.2019 0:39, Jiri Olsa wrote:
> On Mon, Dec 24, 2018 at 03:24:36PM +0300, Alexey Budankov wrote:
>
> SNIP
>
>> +#else
>> +static void perf_mmap__aio_alloc(void **data, size_t len)
>> +{
>> +*data = malloc(len);
>> +}
>> +
>> +static void perf_mmap__aio_free(void **data, size_t
When multiple instances of pcf857x chips are present, a fix up
message [1] is printed during the probe of the 2nd and later
instances.
The issue is that the driver is using the same irq_chip data
structure between multiple instances.
Fix this by allocating the irq_chip data structure per
8250_omap driver uses clock-frequency DT property to obtain functional
clk frequency. This is not ideal as users need to calculate functional
clk frequency offline and populate it in DT.
Therefore add support to obtain functional clock frequency using clk
APIs when clock-frequency DT property is
This series adds support obtain clk frequency of functional clk via
clocks phandle instead of hard coding it in DT as part of
clock-frequency DT parameter. This eliminates need to calculate
frequency offline and populate it.
Vignesh R (3):
serial: 8250_omap: Drop check for of_node
8250_omap is DT only driver so dev->of_node always exists. Drop check
for existence of valid dev->of_node to simplify omap8250_probe().
Signed-off-by: Vignesh R
---
drivers/tty/serial/8250/8250_omap.c | 63 +
1 file changed, 28 insertions(+), 35 deletions(-)
diff
Document clocks property used to pass phandle to functional clk.
Signed-off-by: Vignesh R
---
Documentation/devicetree/bindings/serial/omap_serial.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/serial/omap_serial.txt
On 09-01-19, 14:34, Rajendra Nayak wrote:
> Now that the OPP bindings are updated to include an optional
> 'opp-level' property, add support to parse it from device tree
> and store it as part of dev_pm_opp structure.
> Also add and export an helper 'dev_pm_opp_get_level()' that can be
> used to
Hi,
On 02.01.2019 0:41, Jiri Olsa wrote:
> On Mon, Dec 24, 2018 at 03:24:36PM +0300, Alexey Budankov wrote:
>
> SNIP
>
>> +static void perf_mmap__aio_free(void **data, size_t len __maybe_unused)
>> +{
>> +zfree(data);
>> +}
>> +
>> +static void perf_mmap__aio_bind(void *data __maybe_unused,
Hi,
On 02.01.2019 0:39, Jiri Olsa wrote:
> On Mon, Dec 24, 2018 at 03:27:17PM +0300, Alexey Budankov wrote:
>
> SNIP
>
>> diff --git a/tools/perf/util/mmap.c b/tools/perf/util/mmap.c
>> index 742fa9a8e498..a2095e4eda4b 100644
>> --- a/tools/perf/util/mmap.c
>> +++ b/tools/perf/util/mmap.c
>> @@
Hi,
On 02.01.2019 0:39, Jiri Olsa wrote:
> On Mon, Dec 24, 2018 at 03:27:17PM +0300, Alexey Budankov wrote:
>>
>> Build node cpu masks for mmap data buffers. Apply node cpu
>> masks to tool thread every time it references data buffers
>> cross node or cross cpu.
>>
>> Signed-off-by: Alexey
Hi Kishon,
On 05/12/18 17:03, Roger Quadros wrote:
> Hi Kishon,
>
> This series extends omap-usb2 PHY driver to be used
> for AM654 USB2 PHY.
Any comments on this series? If it looks fine, could you please
queue this for -next. Thanks.
cheers,
-roger
>
> cheers,
> -roger
>
> Roger Quadros
The AD5674R/AD5679R are low power, 16-channel, 12-/16-bit buffered voltage
output digital-to-analog converters (DACs). They include a 2.5 V internal
reference (enabled by default).
These devices are very similar to AD5684R/AD5686R, except that they have 16
channels.
Signed-off-by: Mircea
Hi,
On 02.01.2019 0:39, Jiri Olsa wrote:
> On Mon, Dec 24, 2018 at 03:28:33PM +0300, Alexey Budankov wrote:
>>
>> Implement --affinity=node|cpu option for the record mode defaulting
>> to system affinity mask bouncing.
>>
>> Signed-off-by: Alexey Budankov
>> ---
>>
Hi,
On 02.01.2019 0:39, Jiri Olsa wrote:
> On Mon, Dec 24, 2018 at 03:28:33PM +0300, Alexey Budankov wrote:
>>
>> Implement --affinity=node|cpu option for the record mode defaulting
>> to system affinity mask bouncing.
>>
>> Signed-off-by: Alexey Budankov
>> ---
>>
Hi,
On 02.01.2019 0:39, Jiri Olsa wrote:
> On Mon, Dec 24, 2018 at 03:28:33PM +0300, Alexey Budankov wrote:
>>
>> Implement --affinity=node|cpu option for the record mode defaulting
>> to system affinity mask bouncing.
>>
>> Signed-off-by: Alexey Budankov
>> ---
>>
Hi Lee,
On 9/1/19 8:25, Lee Jones wrote:
> On Tue, 08 Jan 2019, Enric Balletbo Serra wrote:
>> Missatge de Lee Jones del dia dv., 21 de des.
>> 2018 a les 16:39:
>>>
>>> On Wed, 12 Dec 2018, Enric Balletbo i Serra wrote:
>>>
Hi,
This is another patchset to try to cleanup a bit
There are some mirror changes in kobject_uevent.c.
Btw, this is v5 for the patchset.2/2 was fixed by v1-v4,but 1/2 was marked
V2 :(.
Bo YU (2):
kobject: to repalce printk with pr_* style
kobject: drop newline from msg string
lib/kobject_uevent.c | 9 -
1 file changed, 4
Repalce printk with pr_warn in kobject_synth_uevent and replace
printk with pr_err in uevent_net_init to make both consistent with
other code in kobject_uevent.c
Signed-off-by: Bo YU
---
Changes in V2:
Improve the commit log, doing as the patch did.
---
lib/kobject_uevent.c | 5 ++---
1 file
There is currently a missing terminating newline in non-switch case
match when msg == NULL
Signed-off-by: Bo YU
---
Changes in V4:
Recovery originly declaration, requested by Greg.
Change in V3:
Improve the commit log, requested by Rafael.
Changes in V2:
Drop newline from msg according to
It has been observed that trace reading thread runs on the same hw thread
most of the time during perf record sampling collection. This scheduling
layout leads up to 30% profiling overhead in case when some cpu intensive
workload fully utilizes a large server system with NUMA. Overhead usually
Hi
Here are some patches to improve the exported call graph, primarily to deal
with x86 retpolines.
Adrian Hunter (6):
perf tools: Fix split_kallsyms_for_kcore for trampoline symbols
perf thread-stack: Tidy thread_stack__push_cp() usage
perf thread-stack: Tidy
Make thread_stack__no_call_return() more readable by adding more local
variables.
Signed-off-by: Adrian Hunter
---
tools/perf/util/thread-stack.c | 35 +-
1 file changed, 17 insertions(+), 18 deletions(-)
diff --git a/tools/perf/util/thread-stack.c
Improve thread_stack__no_call_return() to better handle 'returns' that do
not match the stack i.e. 'no call'. See code comments for details.
The example below shows how retpolines are affected:
Example:
$ cat simple-retpoline.c
__attribute__((noinline)) int bar(void)
{
return -1;
}
int
On Wed, Jan 9, 2019 at 10:17 AM Bo YU wrote:
>
> Repalce printk with pr_warn in kobject_synth_uevent and replace
> printk with pr_err in uevent_net_init to make both consistent with
> other code in kobject_uevent.c
>
> Signed-off-by: Bo YU
Reviewed-by: Rafael J. Wysocki
>
> ---
> Changes in
On 2019-01-08 8:25 p.m., Sasha Levin wrote:
> From: Nicholas Kazlauskas
>
> [ Upstream commit 520f08df45fbe300ed650da786a74093d658b7e1 ]
>
> When variable refresh rate is active [...]
Variable refresh rate (FreeSync) support is only landing in 5.0,
therefore this fix isn't needed in older
On 1/9/2019 2:39 PM, Viresh Kumar wrote:
On 09-01-19, 14:34, Rajendra Nayak wrote:
On some SoCs (especially from Qualcomm and MediaTek) an OPP
node needs to describe an additional level/corner value
that is then communicated to a remote microprocessor by the CPU, which
then takes some
On Tue, Jan 08, 2019 at 08:02:05PM +0200, Andy Shevchenko wrote:
> New quirk enforces search for GPIO based on its type.
> Note, supplied index in the mapping table must be 0.
Can you document this where you define the new flag so new users do not
need go through git history?
Otherwise looks
The compiler might optimize a call/ret combination by making it a jmp.
However the thread-stack does not presently cater for that, so that such
control flow is not visible in the call graph. Make it visible by recording
on the stack a branch to the start of a different symbol. Note, that means
x86 retpoline functions pollute the call graph by showing up everywhere
there is an indirect branch, but they do not really mean anything. Make
changes so that the default retpoline functions will no longer appear in
the call graph. Note this only affects the call graph, since all the
original
Kallsyms symbols do not have a size, so the size becomes the distance to
the next symbol. Consequently the recently added trampoline symbols end up
with large sizes because the trampolines are some distance from one another
and the main kernel map. However, symbols that end outside their map can
If 'cp' is checked in thread_stack__push_cp() a number of error checks can
be removed, reducing code size and improving readability.
Signed-off-by: Adrian Hunter
---
tools/perf/util/thread-stack.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff --git
On Wed, Jan 9, 2019 at 10:17 AM Bo YU wrote:
>
> There is currently a missing terminating newline in non-switch case
> match when msg == NULL
>
> Signed-off-by: Bo YU
I have given you an R-by for this one already, so why haven't you added it here?
Reviewed-by: Rafael J. Wysocki
> ---
>
On 09-01-19, 14:50, Rajendra Nayak wrote:
> Sure, does this seem fine?
>
> - opp-level: A value representing the performance level of the device,
> expressed as a 32-bit big-endian integer.
Not sure if you need to specify endian-ness here.
> I assume the changelog mentioning the motivation
On 1/9/2019 2:42 PM, Viresh Kumar wrote:
On 09-01-19, 14:34, Rajendra Nayak wrote:
Now that the OPP bindings are updated to include an optional
'opp-level' property, add support to parse it from device tree
and store it as part of dev_pm_opp structure.
Also add and export an helper
On Wed, Jan 9, 2019 at 8:38 AM Eric Biggers wrote:
>
> From: Eric Biggers
>
> kset_get_ownership() is only used in lib/kobject.c, so make it 'static'.
>
> Signed-off-by: Eric Biggers
Reviewed-by: Rafael J. Wysocki
> ---
> lib/kobject.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Add documentation to describe Xilinx ZynqMP SHA3 driver
bindings.
Signed-off-by: Kalyani Akula
---
.../devicetree/bindings/crypto/zynqmp-sha.txt | 12
1 files changed, 12 insertions(+), 0 deletions(-)
create mode 100644
1 - 100 of 1253 matches
Mail list logo
