On 18/01/2018 16:32, Paolo Bonzini wrote:
> On 18/01/2018 14:48, Peter Zijlstra wrote:
>> From: Ashok Raj
>>
>> Add MSR passthrough for MSR_IA32_PRED_CMD and place branch predictor
>> barriers on switching between VMs to avoid inter VM specte-v2 attacks.
>>
>> [peterz: rebase and changelog rewrite
From: Kalle Valo
Date: Fri, 19 Jan 2018 10:59:33 +0200
> a pull request to net-next tree for 4.16. This should be the last pull
> request in this cycle, unless Linus releases -rc9 of course. Only few
> patches so should be an easy one. Please let me know if there are any
> problems.
Pulled, than
On 1/19/2018 9:11 AM, Greg Kroah-Hartman wrote:
> On Fri, Jan 19, 2018 at 09:03:52AM -0600, Tom Lendacky wrote:
>> On 1/15/2018 4:47 PM, Gabriel C wrote:
>>> On 11.01.2018 19:33, Borislav Petkov wrote:
On Wed, Jan 10, 2018 at 01:25:45PM -0600, Tom Lendacky wrote:
> This patch series addres
UBSAN=y fails to build with new GCC/clang:
arch/x86/kernel/head64.o: In function `sanitize_boot_params':
arch/x86/include/asm/bootparam_utils.h:37: undefined reference to
`__ubsan_handle_type_mismatch_v1'
because Clang and GCC 8 slightly changed ABI for 'type mismatch' errors.
Compiler n
Similarly to type mismatch checks, new GCC 8.x and Clang also
changed for ABI for returns_nonnull checks. While we can update our
code to conform the new ABI it's more reasonable to just remove it.
Because it's just dead code, we don't have any single user of
returns_nonnull attribute in the whole
Hi Greentime,
On Fri, Jan 19, 2018 at 4:18 PM, Greentime Hu wrote:
> 2018-01-19 22:52 GMT+08:00 Arnd Bergmann :
>> On Fri, Jan 19, 2018 at 3:32 PM, Greentime Hu wrote:
>>> 2018-01-18 19:02 GMT+08:00 Arnd Bergmann :
On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote:
> From: Greentime
Indentation is one TAB and 7 spaces instead of 2 TABs.
Fixes: 3cf385713460eb2b ("ARM: 8256/1: driver coamba: add device binding path
'driver_override'")
Signed-off-by: Geert Uytterhoeven
---
drivers/amba/bus.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/amba/
Hi Russell,
This patch series contains improvements to driver_override handling in
the AMBA bus driver, including two bugfixes that are based on similar
fixes for the PCI and platform buses.
Thanks!
Geert Uytterhoeven (4):
ARM: amba: Make driver_override output consistent with other bu
When printing the driver_override parameter when it is 4095 and 4094
bytes long, the printing code would access invalid memory because we
need count + 1 bytes for printing.
Cfr. commits 4efe874aace57dba ("PCI: Don't read past the end of sysfs
"driver_override" buffer") and bf563b01c2895a4b ("drive
For AMBA devices with unconfigured driver override, the
"driver_override" sysfs virtual file is empty, while it contains
"(null)" for platform and PCI devices.
Make AMBA consistent with other buses by dropping the test for a NULL
pointer.
Note that contrary to popular belief, sprintf() handles NU
The driver_override implementation is susceptible to a race condition
when different threads are reading vs storing a different driver
override. Add locking to avoid this race condition.
Cfr. commits 6265539776a0810b ("driver core: platform: fix race
condition with driver_override") and 9561475db
On Fri 19-01-18 07:24:08, Shakeel Butt wrote:
[...]
> Thanks for the explanation. Another query, we do not call
> drain_all_stock() in mem_cgroup_resize_limit() but memory_max_write()
> does call drain_all_stock(). Was this intentional or missed
> accidentally?
I think it is just an omission. I wo
On Fri, Jan 19, 2018 at 03:20:13PM +, Bart Van Assche wrote:
> On Fri, 2018-01-19 at 15:26 +0800, Ming Lei wrote:
> > Please see queue_delayed_work_on(), hctx->run_work is shared by all
> > scheduling, once blk_mq_delay_run_hw_queue(100ms) returns, no new
> > scheduling can make progress during
On Fri, Jan 19, 2018 at 09:27:47AM -0600, Tom Lendacky wrote:
> On 1/19/2018 9:11 AM, Greg Kroah-Hartman wrote:
> > On Fri, Jan 19, 2018 at 09:03:52AM -0600, Tom Lendacky wrote:
> >> On 1/15/2018 4:47 PM, Gabriel C wrote:
> >>> On 11.01.2018 19:33, Borislav Petkov wrote:
> On Wed, Jan 10, 2018
2018-01-19 23:29 GMT+08:00 Geert Uytterhoeven :
> Hi Greentime,
>
> On Fri, Jan 19, 2018 at 4:18 PM, Greentime Hu wrote:
>> 2018-01-19 22:52 GMT+08:00 Arnd Bergmann :
>>> On Fri, Jan 19, 2018 at 3:32 PM, Greentime Hu wrote:
2018-01-18 19:02 GMT+08:00 Arnd Bergmann :
> On Mon, Jan 15, 201
Hi Greentime,
On Fri, Jan 19, 2018 at 4:35 PM, Greentime Hu wrote:
> 2018-01-19 23:29 GMT+08:00 Geert Uytterhoeven :
>> On Fri, Jan 19, 2018 at 4:18 PM, Greentime Hu wrote:
>>> 2018-01-19 22:52 GMT+08:00 Arnd Bergmann :
On Fri, Jan 19, 2018 at 3:32 PM, Greentime Hu wrote:
> 2018-01-18
Hi Andy,
On 18/01/18 10:43, Sudeep Holla wrote:
> We need to call of_node_put() for device nodes obtained with
> of_find_node_by_path().
>
> Fixes: 3aa0582fdb82 ("of: platform: populate /firmware/ node from
> of_platform_default_populate_init()")
> Reported-by: Loys Ollivier
> Cc: Rob Herring
On Fri, Jan 19, 2018 at 04:35:24PM +0100, Greg Kroah-Hartman wrote:
> On Fri, Jan 19, 2018 at 09:27:47AM -0600, Tom Lendacky wrote:
> > On 1/19/2018 9:11 AM, Greg Kroah-Hartman wrote:
> > > On Fri, Jan 19, 2018 at 09:03:52AM -0600, Tom Lendacky wrote:
> > >> On 1/15/2018 4:47 PM, Gabriel C wrote:
>
On Fri, Jan 19, 2018 at 09:27:47AM -0600, Tom Lendacky wrote:
> On 1/19/2018 9:11 AM, Greg Kroah-Hartman wrote:
> > On Fri, Jan 19, 2018 at 09:03:52AM -0600, Tom Lendacky wrote:
> >> On 1/15/2018 4:47 PM, Gabriel C wrote:
> >>> On 11.01.2018 19:33, Borislav Petkov wrote:
> On Wed, Jan 10, 2018
On Fri, Jan 19, 2018 at 08:24:06AM -0700, Jens Axboe wrote:
> On 1/19/18 12:26 AM, Ming Lei wrote:
> > On Thu, Jan 18, 2018 at 09:02:45PM -0700, Jens Axboe wrote:
> >> On 1/18/18 7:32 PM, Ming Lei wrote:
> >>> On Thu, Jan 18, 2018 at 01:11:01PM -0700, Jens Axboe wrote:
> On 1/18/18 11:47 AM, B
From: Paul Burton
Document a binding for the MIPS Cluster Power Controller (CPC) that
allows the device tree to specify where the CPC registers are located.
Signed-off-by: Paul Burton
Signed-off-by: Aleksandar Markovic
Reviewed-by: Rob Herring
---
Documentation/devicetree/bindings/power/mti,
From: Paul Burton
Reading mips_cpc_base value from the DT allows each platform to
define it according to its needs. This is especially convenient
for MIPS_GENERIC kernel where this kind of information should be
determined in runtime.
Use mti,mips-cpc compatible string with just a reg property to
From: Aleksandar Markovic
v3->v4:
- documentation patch now contains updating of MAINTAINERS file
- rebased to the latest code
v2->v3:
- changed documentation file location from
devicetree/bindings/misc to devicetree/bindings/power
- minor commit message improvements
On Fri, Jan 19, 2018 at 03:55:28PM +0100, Arnd Bergmann wrote:
> On 32-bit architectures, resource_size_t is usually 'unsigned int' or
> 'unsigned long' but not 'unsigned long long', so we get a warning
> about printing the wrong data:
>
> drivers/ntb/test/ntb_perf.c: In function 'perf_setup_peer_
* Pavel Machek [180118 22:04]:
> On Tue 2018-01-02 20:42:36, Sebastian Reichel wrote:
> > Hi,
> >
> > On Tue, Jan 02, 2018 at 01:59:48PM +0100, Pavel Machek wrote:
> > >
> > > This adds support for volume up/down keys in the dts.
> > >
> > > Signed-off-by: Pavel Machek
> >
> > Reviewed-by: Se
On axg, the rate of the mpll is stuck as if sdm value was 4 and could not
change (expect for mpll2 strangely). Looking at the vendor kernel, it
turns out a new magic bit from the undocumented HHI_PLL_TOP_MISC register
is required.
Setting this bit solves the problem and the mpll rates are back to
Hi Steven,
On Fri, Jan 19, 2018 at 10:03:53AM -0500, Steven Rostedt wrote:
> On Fri, 19 Jan 2018 14:53:05 +0530
> Pavan Kondeti wrote:
>
> > I am seeing "spinlock already unlocked" BUG for rd->rto_lock on a 4.9
> > stable kernel based system. This issue is observed only after
> > inclusion of th
As per Linus suggestion, this take doesn't limit the number of occurences
per jiffy anymore but instead defers a vector to workqueues as soon as
it gets re-enqueued on IRQ tail.
No tunable here, so testing should be easier.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
On Fri, 19 Jan 2018 09:48:22 +
Shameerali Kolothum Thodi wrote:
> > > +static void vfio_iommu_iova_resv_refresh(struct vfio_iommu *iommu)
> > > +{
> > > + struct vfio_domain *d;
> > > + struct vfio_group *g;
> > > + struct vfio_iova *node, *tmp;
> > > + struct iommu_resv_region *resv, *resv_ne
Some softirq vectors can be more CPU hungry than others. Especially
networking may sometimes deal with packet storm and need more CPU than
IRQ tail can offer without inducing scheduler latencies. In this case
the current code defers to ksoftirqd that behaves nicer. Now this nice
behaviour can be ba
Softirqs are currently allowed to execute as much pending work as needed
as long as it doesn't overrun 10 iterations or 2 ms. The rest of the
pending work is deferred to ksoftirqd beyond that limit.
In fact 2 ms is a very high threshold that shouldn't be reachable after
only 10 iterations. And jus
Ksoftirqd only remains to implement threaded IRQs. Convert it to
existing per-vector workqueues to avoid code duplication.
Suggested-by: Linus Torvalds
Suggested-by: Paolo Abeni
Signed-off-by: Frederic Weisbecker
Cc: Dmitry Safonov
Cc: Eric Dumazet
Cc: Linus Torvalds
Cc: Peter Zijlstra
Cc:
One more step toward converting ksoftirqd to per vector workqueues.
Suggested-by: Paolo Abeni
Suggested-by: Linus Torvalds
Signed-off-by: Frederic Weisbecker
Cc: Dmitry Safonov
Cc: Eric Dumazet
Cc: Linus Torvalds
Cc: Peter Zijlstra
Cc: Andrew Morton
Cc: David Miller
Cc: Hannes Frederic So
On Fri, Jan 19, 2018 at 04:15:33AM +, Van De Ven, Arjan wrote:
> there is no such guarantee. Some of the IBRS implementations will
> actually flush rather than disable, or flush parts and disable other
> parts.
To me it helps in order to memorize the spec to understand why the
spec is the way
On 1/19/18 8:40 AM, Ming Lei wrote:
Where does the dm STS_RESOURCE error usually come from - what's exact
resource are we running out of?
>>>
>>> It is from blk_get_request(underlying queue), see
>>> multipath_clone_and_map().
>>
>> That's what I thought. So for a low queue depth underlyi
On Fri, 2018-01-19 at 23:16 +0800, jianchao.wang wrote:
> Hi Tariq
>
> Very sad that the crash was reproduced again after applied the patch.
>
> --- a/drivers/net/ethernet/mellanox/mlx4/en_rx.c
> +++ b/drivers/net/ethernet/mellanox/mlx4/en_rx.c
> @@ -252,6 +252,7 @@ static inline bool mlx4_en_is_
On 01/18/2018 02:36 PM, Paul Moore wrote:
On Thu, Jan 18, 2018 at 4:58 PM, Mark Salyzyn wrote:
general protection fault: [#1] PREEMPT SMP KASAN
CPU: 1 PID: 14233 Comm: syz-executor2 Not tainted 4.4.112-g5f6325b #28
. . .
[] selinux_socket_setsockopt+0x4d/0x80
security/selinux/hooks.c:4338
Commit-ID: 6f41c34d69eb005e7848716bbcafc979b35037d5
Gitweb: https://git.kernel.org/tip/6f41c34d69eb005e7848716bbcafc979b35037d5
Author: Thomas Gleixner
AuthorDate: Thu, 18 Jan 2018 16:28:26 +0100
Committer: Thomas Gleixner
CommitDate: Fri, 19 Jan 2018 16:31:28 +0100
x86/mce: Make machi
Commit-ID: 98f0fceec7f84d80bc053e49e596088573086421
Gitweb: https://git.kernel.org/tip/98f0fceec7f84d80bc053e49e596088573086421
Author: zhenwei.pi
AuthorDate: Thu, 18 Jan 2018 09:04:52 +0800
Committer: Thomas Gleixner
CommitDate: Fri, 19 Jan 2018 16:31:29 +0100
x86/pti: Document fix wr
Commit-ID: 3f7d875566d8e79c5e0b2c9a413e91b2c29e0854
Gitweb: https://git.kernel.org/tip/3f7d875566d8e79c5e0b2c9a413e91b2c29e0854
Author: Andi Kleen
AuthorDate: Wed, 17 Jan 2018 14:53:28 -0800
Committer: Thomas Gleixner
CommitDate: Fri, 19 Jan 2018 16:31:30 +0100
x86/retpoline: Optimize
Commit-ID: 736e80a4213e9bbce40a7c050337047128b472ac
Gitweb: https://git.kernel.org/tip/736e80a4213e9bbce40a7c050337047128b472ac
Author: Masami Hiramatsu
AuthorDate: Fri, 19 Jan 2018 01:14:21 +0900
Committer: Thomas Gleixner
CommitDate: Fri, 19 Jan 2018 16:31:28 +0100
retpoline: Introdu
Dear RT Folks,
I'm pleased to announce the 3.8.13.13-rt24 stable release.
This release is just an update to the new stable 3.8.13.13 version
and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stabl
Commit-ID: c86a32c09f8ced67971a2310e3b0dda4d1749007
Gitweb: https://git.kernel.org/tip/c86a32c09f8ced67971a2310e3b0dda4d1749007
Author: Masami Hiramatsu
AuthorDate: Fri, 19 Jan 2018 01:15:20 +0900
Committer: Thomas Gleixner
CommitDate: Fri, 19 Jan 2018 16:31:29 +0100
kprobes/x86: Disab
Commit-ID: c1804a236894ecc942da7dc6c5abe209e56cba93
Gitweb: https://git.kernel.org/tip/c1804a236894ecc942da7dc6c5abe209e56cba93
Author: Masami Hiramatsu
AuthorDate: Fri, 19 Jan 2018 01:14:51 +0900
Committer: Thomas Gleixner
CommitDate: Fri, 19 Jan 2018 16:31:28 +0100
kprobes/x86: Black
On Fri, 19 Jan 2018 21:14:30 +0530
Pavan Kondeti wrote:
> Yeah, it should work. I will give it a try and send the patch
> for review.
Add a comment above the assignment saying something to the effect:
/* Due to CPU hotplug, rq->rd could possibly change */
-- Steve
This changeset is a collection of fixes and clean-up around the pll clock
provider. This has been triggered by the discussion around the ethernet
clock on the axg [0].
On the axg the rate reported by the fixed_pll is off by 8Mhz, which leads
the internal mux of the ethernet driver to pick an mpll2
Make sure the rate param table is available before using it.
Some read-only plls don't provide it, which is ok since the
table is not used by read-only clocks. R/W clocks are supposed
to provide it, but it does not hurt check it.
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/clk-pll.c | 10
The fixed_pll of gxbb and gxl also has a fractional parameter. This has
not been a problem so far because the fractional part is actually set
to 0 on these platforms, so the rate remains correct when it is ignored.
Still, it is better represent the pll the way it is, so add the frac
parameter now
The fixed_pll also has a fractional part. On axg s400 board, without
this parameter, the calculated rate is off by ~8Mhz (0,4%). The fixed_pll
being the root of the peripheral clock tree, this error is propagated to
the rest of the clocks
Adding the definition of the parameter fixes the problem
F
The rate of the parent should not be multiplied by 2 when the pll has a
fractional part. This is making the rate calculation of the gxl_hdmi_pll
wrong (and others as well). This multiplication is specific
to the hdmi_pll of gxbb and is most likely due to a multiplier sitting
in front of this partic
The hdmi pll used in the gxl family is actually different from the gxbb
one. The register layout is completely different, which explain why the
hdmi pll rate has always been rubbish on the gxl family.
Adding the correct register field is the first part of the fix to get a
correct rate out the hdmi
Em Fri, Jan 19, 2018 at 08:24:56AM -0700, Mathieu Poirier escreveu:
> On 19 January 2018 at 08:12, Jiri Olsa wrote:
> > On Fri, Jan 19, 2018 at 11:58:19AM -0300, Arnaldo Carvalho de Melo wrote:
> >> Em Thu, Jan 18, 2018 at 03:27:43PM +0100, Jiri Olsa escreveu:
> >> > On Thu, Jan 18, 2018 at 11:14:
Some meson plls, such as the hdmi pll, are using a 3rd od parameter,
which is yet another "power of 2" post divider. Add it to fix the
calculation of the hdmi_pll rate
Fixes: 738f66d3211d ("clk: gxbb: add AmLogic GXBB clk controller driver")
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/clk
Use the fractional part width in the calculation instead of 12, which
happens to be the witdh right now. This is safer in case the field width
ever change in the future
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/clk-pll.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
The pll driver performs the rate calculation in Mhz, which adds an
unnecessary rounding down to the Mhz of the rate. Use 64bits long
integers to perform this calculation safely on meson8b and perform the
calculation in Hz instead
Fixes: 7a29a869434e ("clk: meson: Add support for Meson clock contro
Read-only plls don't need param table to recalculate the rate.
Providing them with a param table is just a waste of memory.
Remove the useless tables from sys_pll on gxbb and axg.
Signed-off-by: Jerome Brunet
---
drivers/clk/meson/axg.c | 94
dr
On 01/19/2018 05:54 PM, Andrey Konovalov wrote:
> diff --git a/scripts/Makefile.kasan b/scripts/Makefile.kasan
> index dbbd4382f15a..db473309f136 100644
> --- a/scripts/Makefile.kasan
> +++ b/scripts/Makefile.kasan
> @@ -39,4 +39,7 @@ else
> endif
>
> CFLAGS_KASAN += $(call cc-option, -fsani
On 1/19/2018 9:35 AM, Greg Kroah-Hartman wrote:
> On Fri, Jan 19, 2018 at 09:27:47AM -0600, Tom Lendacky wrote:
>> On 1/19/2018 9:11 AM, Greg Kroah-Hartman wrote:
>>> On Fri, Jan 19, 2018 at 09:03:52AM -0600, Tom Lendacky wrote:
On 1/15/2018 4:47 PM, Gabriel C wrote:
> On 11.01.2018 19:33,
On 2018-01-19 19:49, Stefan Roese wrote:
On 19.01.2018 12:10, Oza Pawandeep wrote:
Clients such as pciehp, dpc are using pcie_wait_link_active, which
waits
till the link becomes active or inactive.
Made generic function and moved it to drivers/pci/pci.c
Signed-off-by: Oza Pawandeep
diff --g
On Fri 2018-01-12 14:55:13, Jason Baron wrote:
> Hi,
>
> While using livepatch, I found that when doing cumulative patches, if a
> patched
> function is completed reverted by a subsequent patch (back to its original
> state)
> livepatch does not revert the funtion to its original state. Specifi
On Thursday 18 January 2018 16:44:08 Pali Rohár wrote:
> On Thursday 18 January 2018 14:59:50 Marco Martin wrote:
> > - if (!sparse_keymap_report_event(priv->input_dev, event, 1, true))
> > + if (event == 0xCC) {
> > + input_report_switch(priv->input_dev, SW_TABLET_MODE, 1);
> > +
Hi Arnd,
On 2018/1/19 15:06, Arnd Bergmann wrote:
> On Tue, Jan 16, 2018 at 5:10 PM, Timur Tabi wrote:
>> On 01/16/2018 09:45 AM, shiju.j...@huawei.com wrote:
>>>
>>> Enable ACPI APEI MEMORY FAILURE option for ARM64,
>>> so that memory errors will be handled.
>>>
>>> Signed-off-by: Shiju Jose
>>
On Wed, Jan 10, 2018 at 9:22 PM, Robert Jarzmik wrote:
> Arnd Bergmann writes:
>
>> Without this tag, we get a build warning:
>>
>> WARNING: modpost: missing MODULE_LICENSE() in arch/arm/mach-pxa/tosa-bt.o
>>
>> For completeness, I'm also adding author and description fields.
>>
>> Signed-off-by:
2018-01-19 16:56 GMT+01:00 Tom Lendacky :
> On 1/19/2018 9:35 AM, Greg Kroah-Hartman wrote:
>> On Fri, Jan 19, 2018 at 09:27:47AM -0600, Tom Lendacky wrote:
>>> On 1/19/2018 9:11 AM, Greg Kroah-Hartman wrote:
On Fri, Jan 19, 2018 at 09:03:52AM -0600, Tom Lendacky wrote:
> On 1/15/2018 4:47
On Fri, Jan 19, 2018 at 11:24:13AM +0200, Heikki Krogerus wrote:
> Hi,
>
> On Fri, Jan 19, 2018 at 09:01:24AM +, shufan_lee(?|) wrote:
> > Hi Heikki,
> >
> > For example, the flow of tcpci_init is a little bit different.
> > In tcpci_init, there are more parameters need to be set for
On Sat, 6 Jan 2018 11:12:46 +0530
Ravi Bangoria wrote:
> Recently, how the pointers being printed with %p has been changed
> by commit ad67b74d2469 ("printk: hash addresses printed with %p").
> This is causing a regression while showing offset in the
> uprobe_events file. Instead of %p, use %px
On Fri, Jan 19, 2018 at 08:48:55AM -0700, Jens Axboe wrote:
> On 1/19/18 8:40 AM, Ming Lei wrote:
> Where does the dm STS_RESOURCE error usually come from - what's exact
> resource are we running out of?
> >>>
> >>> It is from blk_get_request(underlying queue), see
> >>> multipath_clone_a
On Fri, 2018-01-19 at 23:33 +0800, Ming Lei wrote:
> On Fri, Jan 19, 2018 at 03:20:13PM +, Bart Van Assche wrote:
> > On Fri, 2018-01-19 at 15:26 +0800, Ming Lei wrote:
> > > Please see queue_delayed_work_on(), hctx->run_work is shared by all
> > > scheduling, once blk_mq_delay_run_hw_queue(100
On Fri, 2018-01-19 at 16:25 +0100, Paolo Bonzini wrote:
> Without retpolines, KVM userspace is not protected from the guest
> poisoning the BTB, because there is no IBRS-barrier on the vmexit
> path.
> So there are two more IBPBs that are needed if retpolines are
> enabled:
>
> 1) in kvm_sched_out
> -Original Message-
> From: platform-driver-x86-ow...@vger.kernel.org [mailto:platform-driver-x86-
> ow...@vger.kernel.org] On Behalf Of Pali Rohár
> Sent: Friday, January 19, 2018 10:01 AM
> To: Dmitry Torokhov
> Cc: linux-kernel@vger.kernel.org; mj...@srcf.ucam.org; dvh...@infradead.org
Ram Pai writes:
> Currently the architecture specific code is expected to
> display the protection keys in smap for a given vma.
> This can lead to redundant code and possibly to divergent
> formats in which the key gets displayed.
>
> This patch changes the implementation. It displays
hi,
I noticed slow perf report on my system and found some
issues described in patches. However I haven't got much
time for testing.. please review/test carefully ;-)
thanks,
jirka
---
tools/lib/symbol/kallsyms.c | 8 ++--
tools/perf/util/machine.c | 6 --
tools/perf/util/machine.h
Current kallsyms__parse uses hex2u64, which gives
no indication of error. Using strtoul to checkup
on failed attempt to parse the number and stop the
rest of the kallsyms__parse processing early.
Link: http://lkml.kernel.org/n/tip-djqwni3p6lgctf6o7xhhw...@git.kernel.org
Signed-off-by: Jiri Olsa
-
Current perf report is real slow on newer kernels,
with following commit:
c0f3ea158939 ("stop using '%pK' for /proc/kallsyms pointer values")
which prevent pointers in /proc/kallsyms, in case
kernel.perf_event_paranoid=2.
That makes perf to fail in finding kernel map details,
and keep parsing i
The following changes since commit b2cd1df66037e7c4697c7e40496bf7e4a5e16a2d:
Linux 4.15-rc7 (2018-01-07 14:22:41 -0800)
are available in the git repository at:
ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-fixes
for you to fetch changes up to b7563e2796
On Fri, Jan 19 2018 at 10:48am -0500,
Jens Axboe wrote:
> On 1/19/18 8:40 AM, Ming Lei wrote:
> Where does the dm STS_RESOURCE error usually come from - what's exact
> resource are we running out of?
> >>>
> >>> It is from blk_get_request(underlying queue), see
> >>> multipath_clone_and
> I removed the blank line at EOF,
> then applied to linux-kbuild/misc.
This script for the semantic patch language is using the at sign within string
literals for Python code.
It is nice when this character seems to work also with the current software.
How does its usage fit to the following inf
> On Jan 19, 2018, at 9:54 AM, Arnd Bergmann wrote:
>
> There is now only one caller left for svcxdr_dupstr() and this is inside
> of an #ifdef, so we can get a warning when the option is disabled:
>
> fs/nfsd/nfs4xdr.c:241:1: error: 'svcxdr_dupstr' defined but not used
> [-Werror=unused-func
From: Frederic Weisbecker
Date: Fri, 19 Jan 2018 16:46:11 +0100
> For now, vectors that get re-enqueued trigger ksoftirqd but they are
> going to be handled by per-vector workqueues on subsequent patches.
Frederic, first of all, thanks for doing all of this work.
So this "get requeued" conditio
On Fri, Jan 19, 2018 at 02:45:38PM +0900, Sergey Senozhatsky wrote:
> On (01/18/18 10:02), Andi Kleen wrote:
> > Dave Young writes:
> > > printk("%sHardware name: %s\n",
> > > log_lvl, dump_stack_arch_desc_str);
> > > + if (kexec_crash_loaded())
> > > + printk("%
On Fri, 19 Jan 2018, SF Markus Elfring wrote:
> > I removed the blank line at EOF,
> > then applied to linux-kbuild/misc.
>
> This script for the semantic patch language is using the at sign within string
> literals for Python code.
>
> It is nice when this character seems to work also with the
On 1/19/18 9:05 AM, Ming Lei wrote:
> On Fri, Jan 19, 2018 at 08:48:55AM -0700, Jens Axboe wrote:
>> On 1/19/18 8:40 AM, Ming Lei wrote:
>> Where does the dm STS_RESOURCE error usually come from - what's exact
>> resource are we running out of?
>
> It is from blk_get_request(underly
On Fri, Jan 19, 2018 at 5:01 PM, Wei Xu wrote:
> Hi Arnd,
>
> On 2018/1/19 15:06, Arnd Bergmann wrote:
>> On Tue, Jan 16, 2018 at 5:10 PM, Timur Tabi wrote:
>>> On 01/16/2018 09:45 AM, shiju.j...@huawei.com wrote:
Enable ACPI APEI MEMORY FAILURE option for ARM64,
so that memory err
On 2018-01-19 19:47, Sinan Kaya wrote:
On 1/19/2018 6:10 AM, Oza Pawandeep wrote:
+++ b/drivers/pci/pcie/pcie-dpc.c
@@ -150,37 +150,9 @@ static void dpc_wait_link_inactive(struct dpc_dev
*dpc)
struct pci_dev *pdev = dpc->dev->port;
struct device *dev = &dpc->dev->device;
On Fri, Jan 19, 2018 at 5:36 AM, Benjamin Poirier
wrote:
> On 2018/01/19 17:59, Benjamin Poirier wrote:
>> On 2018/01/18 07:51, Alexander Duyck wrote:
>> > On Wed, Jan 17, 2018 at 10:50 PM, Benjamin Poirier
>> > wrote:
>> > > It was reported that emulated e1000e devices in vmware esxi 6.5 Build
On 1/19/18 9:13 AM, Mike Snitzer wrote:
> On Fri, Jan 19 2018 at 10:48am -0500,
> Jens Axboe wrote:
>
>> On 1/19/18 8:40 AM, Ming Lei wrote:
>> Where does the dm STS_RESOURCE error usually come from - what's exact
>> resource are we running out of?
>
> It is from blk_get_request(u
i.MX7ULP Clock functions are under joint control of the System
Clock Generation (SCG) modules, Peripheral Clock Control (PCC)
modules, and Core Mode Controller (CMC)1 blocks
Note IMX7ULP has two clock domains: M4 and A7. This binding doc
is only for A7 clock domain.
Cc: Rob Herring
Cc: Mark Rutl
Seeking your kind assistance
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
On Fri, Jan 19, 2018 at 09:19:24AM -0700, Jens Axboe wrote:
> On 1/19/18 9:05 AM, Ming Lei wrote:
> > On Fri, Jan 19, 2018 at 08:48:55AM -0700, Jens Axboe wrote:
> >> On 1/19/18 8:40 AM, Ming Lei wrote:
> >> Where does the dm STS_RESOURCE error usually come from - what's exact
> >> resource
On Fri, Jan 19, 2018 at 8:08 AM, David Woodhouse wrote:
> On Fri, 2018-01-19 at 16:25 +0100, Paolo Bonzini wrote:
>> Without retpolines, KVM userspace is not protected from the guest
>> poisoning the BTB, because there is no IBRS-barrier on the vmexit
>> path.
>> So there are two more IBPBs that a
On Fri, Jan 19, 2018 at 11:15:33AM -0500, Chuck Lever wrote:
>
>
> > On Jan 19, 2018, at 9:54 AM, Arnd Bergmann wrote:
> >
> > There is now only one caller left for svcxdr_dupstr() and this is inside
> > of an #ifdef, so we can get a warning when the option is disabled:
> >
> > fs/nfsd/nfs4xdr
On 1/19/18 9:26 AM, Ming Lei wrote:
> On Fri, Jan 19, 2018 at 09:19:24AM -0700, Jens Axboe wrote:
>> On 1/19/18 9:05 AM, Ming Lei wrote:
>>> On Fri, Jan 19, 2018 at 08:48:55AM -0700, Jens Axboe wrote:
On 1/19/18 8:40 AM, Ming Lei wrote:
Where does the dm STS_RESOURCE error usually com
Hi,
I'm sending this pull request exceptionally early, since I'll be
traveling from tomorrow for a few weeks. I'll (hopefully) have the
net access during my vacation, but better to prepare than sorry, so it
be here.
thanks,
Takashi
===
Linus,
please pull sound updates for 4.16-rc1 from:
On Fri, Jan 19, 2018 at 1:55 AM, Joerg Roedel wrote:
> Hey Andy,
>
> On Wed, Jan 17, 2018 at 10:10:23AM -0800, Andy Lutomirski wrote:
>> On Wed, Jan 17, 2018 at 1:18 AM, Joerg Roedel wrote:
>
>> > Just read up on vm86 mode control transfers and the stack layout then.
>> > Looks like I need to che
Hi, Arnd:
2018-01-18 18:11 GMT+08:00 Arnd Bergmann :
> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote:
>
> I had not looked at this patch in enough detail earlier, sorry about
> that. It should be
> easy enough to fix though.
>
>> +#ifdef CONFIG_VGA_CONSOLE
>> +struct screen_info screen_info
On Fri, Jan 19, 2018 at 09:27:46AM -0700, Jens Axboe wrote:
> On 1/19/18 9:26 AM, Ming Lei wrote:
> > On Fri, Jan 19, 2018 at 09:19:24AM -0700, Jens Axboe wrote:
> >> On 1/19/18 9:05 AM, Ming Lei wrote:
> >>> On Fri, Jan 19, 2018 at 08:48:55AM -0700, Jens Axboe wrote:
> On 1/19/18 8:40 AM, Min
On Fri, Jan 19, 2018 at 5:34 PM, Greentime Hu wrote:
> Hi, Arnd:
>
> 2018-01-18 18:11 GMT+08:00 Arnd Bergmann :
>> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote:
>>
>> I had not looked at this patch in enough detail earlier, sorry about
>> that. It should be
>> easy enough to fix though.
>>
On 1/19/18 9:37 AM, Ming Lei wrote:
> On Fri, Jan 19, 2018 at 09:27:46AM -0700, Jens Axboe wrote:
>> On 1/19/18 9:26 AM, Ming Lei wrote:
>>> On Fri, Jan 19, 2018 at 09:19:24AM -0700, Jens Axboe wrote:
On 1/19/18 9:05 AM, Ming Lei wrote:
> On Fri, Jan 19, 2018 at 08:48:55AM -0700, Jens Axbo
On Thu, Jan 18, 2018 at 02:48:18PM +0100, Peter Zijlstra wrote:
> @@ -1216,7 +1218,8 @@ static bool __grow_static_block(struct o
>
> switch (insn->type) {
> case INSN_JUMP_UNCONDITIONAL:
> - /* mark this instruction, terminate this section */
> + /* follow the
> So it works, but you are complaining anyway?
I dare to point a contradiction out between two information sources
once more.
Is this SmPL script really working in intended way already?
> I guess the conclusion is that it woks in strings (which are pretty
> universal) and not in comments (which
301 - 400 of 703 matches
Mail list logo
