Re: [PATCH v4 0/2] cpufreq: Add sunxi nvmem based CPU scaling driver

On 17-04-19, 10:31, Maxime Ripard wrote: > On Wed, Apr 17, 2019 at 07:38:30AM +0530, Viresh Kumar wrote: > > On 16-04-19, 11:52, Yangtao Li wrote: > > > Add sunxi nvmem based CPU scaling driver, refers to qcom-cpufreq-kryo. > > > > > > Yangtao Li (2): > > > cpufreq: Add sunxi nvmem based CPU

Re: IOMMU Page faults when running DMA transfers from PCIe device

Am Dienstag, 16. April 2019, 17:33:07 CEST schrieb Jerome Glisse: > On Mon, Apr 15, 2019 at 06:04:11PM +0200, Patrick Brunner wrote: > > Dear all, > > > > I'm encountering very nasty problems regarding DMA transfers from an > > external PCIe device to the main memory while the IOMMU is enabled,

Re: [PATCH v1 2/4] clone: add CLONE_PIDFD

On Wed, Apr 17, 2019 at 04:22:54PM +0200, Oleg Nesterov wrote: > On 04/16, Christian Brauner wrote: > > > > + if (clone_flags & CLONE_PIDFD) { > > + retval = pidfd_create(pid, ); > > + if (retval < 0) > > + goto bad_fork_free_pid; > > + pidfd =

[tip:x86/irq] x86/irq/64: Remove stack overflow debug code

Commit-ID: 117ed45485413b1977bfc638c32bf5b01d53c62b Gitweb: https://git.kernel.org/tip/117ed45485413b1977bfc638c32bf5b01d53c62b Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 18:00:08 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:41:48 +0200 x86/irq/64: Remove

[tip:x86/irq] x86/irq/64: Remap the IRQ stack with guard pages

Commit-ID: 18b7a6bef62de1d598fbff23b52114b7775ecf00 Gitweb: https://git.kernel.org/tip/18b7a6bef62de1d598fbff23b52114b7775ecf00 Author: Andy Lutomirski AuthorDate: Sun, 14 Apr 2019 18:00:07 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:40:57 +0200 x86/irq/64: Remap

[tip:x86/irq] x86/irq/64: Split the IRQ stack into its own pages

Commit-ID: e6401c13093173aad709a5c6de00cf8d692ee786 Gitweb: https://git.kernel.org/tip/e6401c13093173aad709a5c6de00cf8d692ee786 Author: Andy Lutomirski AuthorDate: Sun, 14 Apr 2019 18:00:06 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:37:02 +0200 x86/irq/64: Split

Re: [PATCH v1 2/4] clone: add CLONE_PIDFD

On 04/16, Christian Brauner wrote: > > + if (clone_flags & CLONE_PIDFD) { > + retval = pidfd_create(pid, ); > + if (retval < 0) > + goto bad_fork_free_pid; > + pidfd = retval; > + } ... > + if (clone_flags & CLONE_PIDFD) { > +

[tip:x86/irq] x86/irq/64: Init hardirq_stack_ptr during CPU hotplug

Commit-ID: 0ac26104208450d35c4e68754ce0c67b3a4d7802 Gitweb: https://git.kernel.org/tip/0ac26104208450d35c4e68754ce0c67b3a4d7802 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 18:00:05 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:34:21 +0200 x86/irq/64: Init

Re: [PATCH V2 2/2] arm64/mm: Enable memory hot remove

On Wed, Apr 17, 2019 at 03:28:18PM +0530, Anshuman Khandual wrote: > On 04/15/2019 07:18 PM, Mark Rutland wrote: > > On Sun, Apr 14, 2019 at 11:29:13AM +0530, Anshuman Khandual wrote: > >> Memory removal from an arch perspective involves tearing down two different > >> kernel based mappings i.e

[tip:x86/irq] x86/irq/32: Handle irq stack allocation failure proper

Commit-ID: 66c7ceb47f628c8bd4f84a6d01c2725ded6a342d Gitweb: https://git.kernel.org/tip/66c7ceb47f628c8bd4f84a6d01c2725ded6a342d Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 18:00:04 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:31:42 +0200 x86/irq/32: Handle

Hello My Beloved One, i need your assistance

Dear Friend, I came across your e-mail contact prior a private search while in need of your assistance. My name is Aisha Gaddafi a single Mother and a Widow with three Children. I am the only biological Daughter of late Libyan President (Late Colonel Muammar Gaddafi). I have investment funds

[tip:x86/irq] x86/irq/64: Rename irq_stack_ptr to hardirq_stack_ptr

Commit-ID: 758a2e312228410f2f5092ade558109e93dc3ee8 Gitweb: https://git.kernel.org/tip/758a2e312228410f2f5092ade558109e93dc3ee8 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 18:00:02 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:27:10 +0200 x86/irq/64: Rename

Re: [PATCH 05/12] dma-buf: add explicit buffer pinning

On Tue, Apr 16, 2019 at 08:38:34PM +0200, Christian König wrote: > Add optional explicit pinning callbacks instead of implicitly assume the > exporter pins the buffer when a mapping is created. > > Signed-off-by: Christian König Don't we need this together with the invalidate callback and the

[tip:x86/irq] x86/irq/32: Invoke irq_ctx_init() from init_IRQ()

Commit-ID: 451f743a64e1cf979f5fe21a1b2a015feb559f72 Gitweb: https://git.kernel.org/tip/451f743a64e1cf979f5fe21a1b2a015feb559f72 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 18:00:03 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:30:12 +0200 x86/irq/32: Invoke

[tip:x86/irq] x86/irq/32: Rename hard/softirq_stack to hard/softirq_stack_ptr

Commit-ID: a754fe2b76d1d6bce7069657bba975034f3ad961 Gitweb: https://git.kernel.org/tip/a754fe2b76d1d6bce7069657bba975034f3ad961 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 18:00:01 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:24:18 +0200 x86/irq/32: Rename

[PATCH v4] x86/PCI: fix a memory leak bug

In pcibios_irq_init(), the PCI IRQ routing table 'pirq_table' is firstly found through pirq_find_routing_table(). If the table is not found and 'CONFIG_PCI_BIOS' is defined, the table is then allocated in pcibios_get_irq_routing_table() using kmalloc(). In the following execution, if the I/O APIC

[tip:x86/irq] x86/irq/32: Make irq stack a character array

Commit-ID: 231c4846b106d526fa212b02b37447d3f2fcc99d Gitweb: https://git.kernel.org/tip/231c4846b106d526fa212b02b37447d3f2fcc99d Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 18:00:00 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:21:21 +0200 x86/irq/32: Make

Re: [PATCH v2] ARM: debug-ll: add default address for digicolor

Hi Arnd, On Wed, Apr 17 2019, Arnd Bergmann wrote: > The digicolor platform has three UARTs, but the Kconfig.debug > file explicitly lists port zero as the one to be used for the > console, while not providing any default values. > > This can get an automated randconfig build stuck in a loop >

[tip:x86/irq] x86/irq/32: Define IRQ_STACK_SIZE

Commit-ID: aa641c287b2f7676f6f0064a8351daf08eca6b0a Gitweb: https://git.kernel.org/tip/aa641c287b2f7676f6f0064a8351daf08eca6b0a Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:59 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:18:36 +0200 x86/irq/32: Define

[PATCH 3/5] regulator: wm8350: Switch to SPDX identifier

Signed-off-by: Axel Lin --- drivers/regulator/wm8350-regulator.c | 21 - 1 file changed, 8 insertions(+), 13 deletions(-) diff --git a/drivers/regulator/wm8350-regulator.c b/drivers/regulator/wm8350-regulator.c index 0eb3f3a33caa..56d6168a888d 100644 ---

[PATCH 4/5] regulator: wm8400: Switch to SPDX identifier

Signed-off-by: Axel Lin --- drivers/regulator/wm8400-regulator.c | 20 +++- 1 file changed, 7 insertions(+), 13 deletions(-) diff --git a/drivers/regulator/wm8400-regulator.c b/drivers/regulator/wm8400-regulator.c index 5ce86b92851b..6f331b51e479 100644 ---

[PATCH v4 3/4] PCI: Modify kernel parameters to differentiate between MMIO and MMIO_PREF sizes

Add kernel parameter pci=hpmemprefsize=nn[KMG] to control MMIO_PREF size for PCI hotplug bridges. Change behaviour of pci=hpmemsize=nn[KMG] to only control MMIO size, rather than controlling both MMIO and MMIO_PREF sizes. Update kernel-parameters documentation to reflect the above changes.

[PATCH v4 4/4] PCI: Cleanup block comments in setup-bus.c to meet kernel style guidelines

Change block comments to accepted style with asterisks on each line. Justify block comments to 80-character limit to reduce the number of lines where possible. Signed-off-by: Nicholas Johnson --- drivers/pci/setup-bus.c | 248 +++- 1 file changed, 120

[PATCH v4 1/4] PCI: Consider alignment of hot-added bridges when distributing available resources

Rewrite pci_bus_distribute_available_resources to better handle bridges with different resource alignment requirements. Pass more details arguments recursively to track the resource start and end addresses relative to the initial hotplug bridge. This is especially useful for Thunderbolt with

[PATCH v4 2/4] PCI: Fix serious bug when sizing bridges with additional size

Change find_free_bus_resource function to not skip assigned resources with non-null parent. Add checks in pbus_size_io and pbus_size_mem to return success if resource returned from find_free_bus_resource is already allocated. This avoids pbus_size_io and pbus_size_mem returning error code to

[PATCH 1/5] regulator: arizona: Switch to SPDX identifier

Signed-off-by: Axel Lin --- drivers/regulator/arizona-ldo1.c| 19 +++ drivers/regulator/arizona-micsupp.c | 19 +++ 2 files changed, 14 insertions(+), 24 deletions(-) diff --git a/drivers/regulator/arizona-ldo1.c b/drivers/regulator/arizona-ldo1.c index

[PATCH 5/5] regulator: wm8994: Switch to SPDX identifier

Signed-off-by: Axel Lin --- drivers/regulator/wm8994-regulator.c | 19 +++ 1 file changed, 7 insertions(+), 12 deletions(-) diff --git a/drivers/regulator/wm8994-regulator.c b/drivers/regulator/wm8994-regulator.c index 38928cdcb6e6..cadea0344486 100644 ---

[PATCH 2/5] regulator: wm831x: Switch to SPDX identifier

Signed-off-by: Axel Lin --- drivers/regulator/wm831x-dcdc.c | 19 +++ drivers/regulator/wm831x-isink.c | 19 +++ drivers/regulator/wm831x-ldo.c | 19 +++ 3 files changed, 21 insertions(+), 36 deletions(-) diff --git

[tip:x86/irq] x86/dumpstack/64: Speedup in_exception_stack()

Commit-ID: c450c8f532b63475b30e29bc600c25ab0a4ab282 Gitweb: https://git.kernel.org/tip/c450c8f532b63475b30e29bc600c25ab0a4ab282 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:58 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:16:57 +0200 x86/dumpstack/64:

[tip:x86/irq] x86/exceptions: Split debug IST stack

Commit-ID: 2a594d4ccf3f10f80b77d71bd3dad10813ac0137 Gitweb: https://git.kernel.org/tip/2a594d4ccf3f10f80b77d71bd3dad10813ac0137 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:57 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:14:28 +0200 x86/exceptions:

[PATCH v4 0/4] PCI: Patch series to support Thunderbolt without any BIOS support

1. Based on 5.1-rc5 so should apply cleanly to latest version 2. The comment clean-up patch is now last 3. Kernel parameters are no longer renamed Sorry - last time I misunderstood or read over the requirements too quickly. I hope this time everything is as requested. Please let me know if

[tip:x86/irq] x86/exceptions: Enable IST guard pages

Commit-ID: 1bdb67e5aa2d5d43c48cb7d93393fcba276c9e71 Gitweb: https://git.kernel.org/tip/1bdb67e5aa2d5d43c48cb7d93393fcba276c9e71 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:56 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:05:32 +0200 x86/exceptions:

[tip:x86/irq] x86/exceptions: Disconnect IST index and stack order

Commit-ID: 3207426925d2b4da390be8068df1d1c2b36e5918 Gitweb: https://git.kernel.org/tip/3207426925d2b4da390be8068df1d1c2b36e5918 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:55 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 15:01:09 +0200 x86/exceptions:

Re: [PATCH v6 09/12] irqchip: ti-sci-inta: Add support for Interrupt Aggregator driver

Hi Lokesh, On 10/04/2019 05:13, Lokesh Vutla wrote: > Texas Instruments' K3 generation SoCs has an IP Interrupt Aggregator > which is an interrupt controller that does the following: > - Converts events to interrupts that can be understood by > an interrupt router. > - Allows for multiplexing

[tip:x86/irq] x86/cpu: Remove orig_ist array

Commit-ID: 4d68c3d0ecd5fcba8876e8a58ac41ffb360de43e Gitweb: https://git.kernel.org/tip/4d68c3d0ecd5fcba8876e8a58ac41ffb360de43e Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:54 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 14:44:17 +0200 x86/cpu: Remove

[tip:x86/irq] x86/cpu: Prepare TSS.IST setup for guard pages

Commit-ID: f6ef73224a0f0400c3979c8bc68b383f9d2eb9d8 Gitweb: https://git.kernel.org/tip/f6ef73224a0f0400c3979c8bc68b383f9d2eb9d8 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:53 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 14:29:22 +0200 x86/cpu: Prepare

Re: [PATCH] signal: don't silently convert SI_USER signals to non-current pidfd

On Wed, Apr 17, 2019 at 03:50:03PM +0200, Oleg Nesterov wrote: > On 04/17, Christian Brauner wrote: > > > > On Wed, Apr 17, 2019 at 03:16:03PM +0200, Oleg Nesterov wrote: > > > On 04/17, Christian Brauner wrote: > > > > > > > > On Mon, Apr 08, 2019 at 03:13:16PM +0200, Oleg Nesterov wrote: > > > >

[PATCH] nvme: determine the number of IO queues

Some controllers support limited IO queues, when over set the number, it will return invalid field error. Then NVME will be removed by driver. Find the max number of IO queues that controller supports. When it still got invalid result, set 1 IO queue at least to bring NVME online. Signed-off-by:

[tip:x86/irq] x86/dumpstack/64: Use cpu_entry_area instead of orig_ist

Commit-ID: afcd21dad88b68d646e91ed36948117d58b4c197 Gitweb: https://git.kernel.org/tip/afcd21dad88b68d646e91ed36948117d58b4c197 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:52 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 13:05:06 +0200 x86/dumpstack/64:

Re: [PATCH v2] x86/PCI: fix a memory leak bug

On Wed, Apr 17, 2019 at 12:58 AM Ingo Molnar wrote: > > > * Wenwen Wang wrote: > > > On Tue, Apr 16, 2019 at 3:33 PM Thomas Gleixner wrote: > > > > > > On Tue, 16 Apr 2019, Wenwen Wang wrote: > > > > > > > In pcibios_irq_init(), the PCI IRQ routing table 'pirq_table' is firstly > > > > found

[tip:x86/irq] x86/irq/64: Use cpu entry area instead of orig_ist

Commit-ID: bf5882abab773afd1277415e2f826b21de28f30d Gitweb: https://git.kernel.org/tip/bf5882abab773afd1277415e2f826b21de28f30d Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:51 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 13:02:48 +0200 x86/irq/64: Use

Re: [PATCH v1 3/4] signal: support CLONE_PIDFD with pidfd_send_signal

On Wed, Apr 17, 2019 at 04:01:06PM +0200, Oleg Nesterov wrote: > On 04/16, Christian Brauner wrote: > > > > @@ -3581,12 +3588,12 @@ SYSCALL_DEFINE4(pidfd_send_signal, int, pidfd, int, > > sig, > > if (flags) > > return -EINVAL; > > > > - f = fdget_raw(pidfd); > > + f =

[tip:x86/irq] x86/traps: Use cpu_entry_area instead of orig_ist

Commit-ID: d876b67343a648f3613506c7dbfed088fa0c875b Gitweb: https://git.kernel.org/tip/d876b67343a648f3613506c7dbfed088fa0c875b Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:50 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 13:01:59 +0200 x86/traps: Use

[tip:x86/irq] x86/cpu_entry_area: Provide exception stack accessor

Commit-ID: 7623f37e411156e6e09b95cf5c76e509c5fda640 Gitweb: https://git.kernel.org/tip/7623f37e411156e6e09b95cf5c76e509c5fda640 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:49 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 13:00:22 +0200

[tip:x86/irq] x86/cpu_entry_area: Prepare for IST guard pages

Commit-ID: a4af767ae59cc579569bbfe49513a0037d5989ee Gitweb: https://git.kernel.org/tip/a4af767ae59cc579569bbfe49513a0037d5989ee Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:48 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:58:21 +0200

[tip:x86/irq] x86/exceptions: Add structs for exception stacks

Commit-ID: 019b17b3ffe48100e52f609ca1c6ed6e5a40cba1 Gitweb: https://git.kernel.org/tip/019b17b3ffe48100e52f609ca1c6ed6e5a40cba1 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:47 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:55:18 +0200 x86/exceptions:

[tip:x86/irq] x86/cpu_entry_area: Cleanup setup functions

Commit-ID: 881a463cf21dbf83aab2cf6c9a359f34f88c2491 Gitweb: https://git.kernel.org/tip/881a463cf21dbf83aab2cf6c9a359f34f88c2491 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:46 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:50:46 +0200

[tip:x86/irq] x86/exceptions: Make IST index zero based

Commit-ID: 8f34c5b5afce91d171bb0802631197484cb69b8b Gitweb: https://git.kernel.org/tip/8f34c5b5afce91d171bb0802631197484cb69b8b Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:45 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:48:00 +0200 x86/exceptions:

Re: [PATCH v4] mm/hotplug: treat CMA pages as unmovable

> Acked-by: Michal Hocko > Acked-by: Vlastimil Babka > Signed-off-by: Qian Cai Reviewed-by: Oscar Salvador > --- > > v4: Use is_migrate_cma_page() and update the commit log per > Vlastimil. > v3: Use a string pointer instead of an array per Michal. > v2: Borrow some commit log texts. >

[tip:x86/irq] x86/exceptions: Remove unused stack defines on 32bit

Commit-ID: 30842211506e376b76394a9cb4e6d0c9d258b8d4 Gitweb: https://git.kernel.org/tip/30842211506e376b76394a9cb4e6d0c9d258b8d4 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:44 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:45:29 +0200 x86/exceptions:

[tip:x86/irq] x86/64: Remove stale CURRENT_MASK

Commit-ID: 6f36bd8d2e8c221eaaf4ce5b0ebbb11c00b0ac98 Gitweb: https://git.kernel.org/tip/6f36bd8d2e8c221eaaf4ce5b0ebbb11c00b0ac98 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:43 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:38:36 +0200 x86/64: Remove

[tip:x86/irq] x86/idt: Remove unused macro SISTG

Commit-ID: 99d334511b337884cadbdfae28da912a4edb1001 Gitweb: https://git.kernel.org/tip/99d334511b337884cadbdfae28da912a4edb1001 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:42 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:36:19 +0200 x86/idt: Remove

Re: [PATCH v4 11/16] locking/rwsem: Enable readers spinning on writer

On Sat, Apr 13, 2019 at 01:22:54PM -0400, Waiman Long wrote: > @@ -650,6 +686,33 @@ __rwsem_down_read_failed_common(struct rw_semaphore > *sem, int state) > struct rwsem_waiter waiter; > DEFINE_WAKE_Q(wake_q); > > + if (!rwsem_can_spin_on_owner(sem)) > + goto queue;

[tip:x86/irq] x86/irq/64: Sanitize the top/bottom confusion

Commit-ID: df835e7083bee33e98635aca26b39b63ebc6cca7 Gitweb: https://git.kernel.org/tip/df835e7083bee33e98635aca26b39b63ebc6cca7 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:41 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:34:49 +0200 x86/irq/64:

[tip:x86/irq] x86/irq/64: Remove a hardcoded irq_stack_union access

Commit-ID: 4f44b8f0b33b7111216f0fad353315f796b81617 Gitweb: https://git.kernel.org/tip/4f44b8f0b33b7111216f0fad353315f796b81617 Author: Andy Lutomirski AuthorDate: Sun, 14 Apr 2019 17:59:40 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:31:38 +0200 x86/irq/64: Remove

[tip:x86/irq] x86/irq/64: Limit IST stack overflow check to #DB stack

Commit-ID: 7dbcf2b0b770eeb803a416ee8dcbef78e6389d40 Gitweb: https://git.kernel.org/tip/7dbcf2b0b770eeb803a416ee8dcbef78e6389d40 Author: Thomas Gleixner AuthorDate: Sun, 14 Apr 2019 17:59:38 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:06:56 +0200 x86/irq/64: Limit

[tip:x86/irq] x86/dumpstack: Fix off-by-one errors in stack identification

Commit-ID: fa33215422fd415a07ec2a00e9f1acdaf0fa8e94 Gitweb: https://git.kernel.org/tip/fa33215422fd415a07ec2a00e9f1acdaf0fa8e94 Author: Andy Lutomirski AuthorDate: Sun, 14 Apr 2019 17:59:39 +0200 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 12:26:50 +0200 x86/dumpstack: Fix

Re: linux-next: build warning after merge of the block tree

On 04/17, Chao Yu wrote: > Hi Jaegeuk, > > On 2019/4/17 10:31, Stephen Rothwell wrote: > > Hi all, > > > > After merging the block tree, today's linux-next build (x86_64 > > allmodconfig) produced this warning: > > > > fs/f2fs/node.c: In function 'f2fs_remove_inode_page': > >

[tip:x86/irq] mm/slab: Remove store_stackinfo()

Commit-ID: 80552f0f7aebdd8deda8ea455292cbfbf462d655 Gitweb: https://git.kernel.org/tip/80552f0f7aebdd8deda8ea455292cbfbf462d655 Author: Qian Cai AuthorDate: Tue, 16 Apr 2019 10:22:57 -0400 Committer: Borislav Petkov CommitDate: Wed, 17 Apr 2019 11:46:27 +0200 mm/slab: Remove

Re: [PATCH v2 3/3] arm64/fpsimd: Don't disable softirq when touching FPSIMD/SVE state

On Wed, Apr 17, 2019 at 12:37:57PM +0100, Julien Grall wrote: > Hi Dave, > > On 16/04/2019 13:30, Dave Martin wrote: > >On Fri, Apr 12, 2019 at 06:14:20PM +0100, Julien Grall wrote: [...] > >>+ > >>+/* > >>+ * Obtain the CPU FPSIMD context for use by the calling context. If we say something

Re: [PATCH v1 3/4] signal: support CLONE_PIDFD with pidfd_send_signal

On 04/16, Christian Brauner wrote: > > @@ -3581,12 +3588,12 @@ SYSCALL_DEFINE4(pidfd_send_signal, int, pidfd, int, > sig, > if (flags) > return -EINVAL; > > - f = fdget_raw(pidfd); > + f = fdget(pidfd); could you explain this change? I am just curious, I don't

Re: [PATCH v4 07/10] drivers: pinctrl: msm: setup GPIO irqchip hierarchy

On Thu, Mar 21, 2019 at 10:54 PM Stephen Boyd wrote: > Quoting Marc Zyngier (2019-03-16 04:39:48)> > On Fri, 15 Mar 2019 09:28:31 > -0700 > > Stephen Boyd wrote: > > > > > Quoting Lina Iyer (2019-03-13 14:18:41) > > > > @@ -994,6 +1092,22 @@ static int msm_gpio_init(struct msm_pinctrl > > > >

Re: [PATCH v4 11/16] locking/rwsem: Enable readers spinning on writer

On Sat, Apr 13, 2019 at 01:22:54PM -0400, Waiman Long wrote: > +/* > + * Try to acquire read lock before the reader is put on wait queue. > + * Lock acquisition isn't allowed if the rwsem is locked or a writer handoff > + * is ongoing. > + */ > +static inline bool

Re: [PATCH v5 1/4] dt-bindings: arm: coresight: Add new compatible for static replicator

On Tue, 16 Apr 2019 at 18:10, Leo Yan wrote: > > On Tue, Apr 16, 2019 at 02:18:40PM -0600, Mathieu Poirier wrote: > > Hi Leo, > > > > On Fri, 12 Apr 2019 at 04:28, Leo Yan wrote: > > > > > > CoreSight uses below bindings for replicator: > > > > > > Dynamic replicator, aka. configurable

Re: [PATCH v4 11/16] locking/rwsem: Enable readers spinning on writer

On Sat, Apr 13, 2019 at 01:22:54PM -0400, Waiman Long wrote: > @@ -549,7 +582,7 @@ static noinline enum owner_state > rwsem_spin_on_owner(struct rw_semaphore *sem) > return !owner ? OWNER_NULL : OWNER_READER; > } > > -static bool rwsem_optimistic_spin(struct rw_semaphore *sem) > +static

Re: [PATCH v1 3/4] mm/memory_hotplug: Make __remove_section() never fail

On Tue, 2019-04-09 at 12:01 +0200, David Hildenbrand wrote: > Let's just warn in case a section is not valid instead of failing to > remove somewhere in the middle of the process, returning an error > that > will be mostly ignored by callers. > > Cc: Andrew Morton > Cc: Oscar Salvador > Cc:

Re: [PATCH] signal: don't silently convert SI_USER signals to non-current pidfd

On 04/17, Christian Brauner wrote: > > On Wed, Apr 17, 2019 at 03:16:03PM +0200, Oleg Nesterov wrote: > > On 04/17, Christian Brauner wrote: > > > > > > On Mon, Apr 08, 2019 at 03:13:16PM +0200, Oleg Nesterov wrote: > > > > > > > > but perhaps it should always fail, even if task_pid(current) ==

Re: [PATCH v1 1/4] mm/memory_hotplug: Release memory resource after arch_remove_memory()

On 17.04.19 15:31, Michal Hocko wrote: > On Wed 17-04-19 15:24:47, David Hildenbrand wrote: >> On 17.04.19 15:12, Michal Hocko wrote: >>> On Tue 09-04-19 12:01:45, David Hildenbrand wrote: __add_pages() doesn't add the memory resource, so __remove_pages() shouldn't remove it. Let's

Re: [PATCH v7 02/10] vsprintf: Consistent %pK handling for kptr_restrict == 0

On Wed, 17 Apr 2019 13:53:42 +0200 Petr Mladek wrote: > restricted_pointer() pretends that it prints the address when kptr_restrict > is set to zero. But it is never called in this situation. Instead, > pointer() falls back to ptr_to_id() and hashes the pointer. > > This patch removes the

[PATCH] KVM: fix KVM_CLEAR_DIRTY_LOG for memory slots of unaligned size

If a memory slot's size is not a multiple of 64 pages (256K), then the KVM_CLEAR_DIRTY_LOG API is unusable: clearing the final 64 pages either requires the requested page range to go beyond memslot->npages, or requires log->num_pages to be unaligned, and kvm_clear_dirty_log_protect requires

RE: [PATCH V12 3/5] thermal: imx_sc: add i.MX system controller thermal support

Best Regards! Anson Huang > -Original Message- > > From: Anson Huang > > Sent: Tuesday, April 16, 2019 11:22 AM > > > > i.MX8QXP is an ARMv8 SoC which has a Cortex-M4 system controller > > inside, the system controller is in charge of controlling power, clock > > and thermal sensors

Re: [PATCH] mm: get_cmdline use arg_lock instead of mmap_sem

On Wed 17-04-19 14:03:47, Michal Koutny wrote: > The commit a3b609ef9f8b ("proc read mm's {arg,env}_{start,end} with mmap > semaphore taken.") added synchronization of reading argument/environment > boundaries under mmap_sem. Later commit 88aa7cc688d4 ("mm: introduce > arg_lock to protect

Re: [PATCH v4 10/16] locking/rwsem: Wake up almost all readers in wait queue

On Sat, Apr 13, 2019 at 01:22:53PM -0400, Waiman Long wrote: > When the front of the wait queue is a reader, other readers > immediately following the first reader will also be woken up at the > same time. However, if there is a writer in between. Those readers > behind the writer will not be

Re: [PATCH 0/3] vmalloc enhancements

On 3/29/19 11:07 PM, Roman Gushchin wrote: >> Roman Gushchin (3): >> mm: refactor __vunmap() to avoid duplicated call to find_vm_area() >> mm: separate memory allocation and actual work in alloc_vmap_area() >> mm: show number of vmalloc pages in /proc/meminfo >> >> fs/proc/meminfo.c |

Re: [PATCH 3/3] mm: show number of vmalloc pages in /proc/meminfo

On 3/1/19 4:05 PM, Vlastimil Babka wrote: > On 2/25/19 9:30 PM, Roman Gushchin wrote: >> Vmalloc() is getting more and more used these days (kernel stacks, >> bpf and percpu allocator are new top users), and the total % >> of memory consumed by vmalloc() can be pretty significant >> and changes

Re: [RFC PATCH] mm/workingset : judge file page activity via timestamp

On Wed, Apr 17, 2019 at 08:26:22PM +0800, Zhaoyang Huang wrote: [quoting Johannes here] > As Matthew says, you are fairly randomly making refault activations > more aggressive (especially with that timestamp unpacking bug), and > while that expectedly boosts workload transition / startup, it comes

Re: [PATCH v1 1/4] mm/memory_hotplug: Release memory resource after arch_remove_memory()

On Wed 17-04-19 15:24:47, David Hildenbrand wrote: > On 17.04.19 15:12, Michal Hocko wrote: > > On Tue 09-04-19 12:01:45, David Hildenbrand wrote: > >> __add_pages() doesn't add the memory resource, so __remove_pages() > >> shouldn't remove it. Let's factor it out. Especially as it is a special >

Re: [PATCH 2/3] mm: separate memory allocation and actual work in alloc_vmap_area()

On 3/1/19 5:48 PM, Roman Gushchin wrote: > On Fri, Mar 01, 2019 at 03:43:19PM +0100, Vlastimil Babka wrote: >> On 2/25/19 9:30 PM, Roman Gushchin wrote: >>> alloc_vmap_area() is allocating memory for the vmap_area, and >>> performing the actual lookup of the vm area and vmap_area >>>

[PATCH v4 1/2] ARM: dts: colibri/apalis: convert to SPDX license tags

Replace boiler plate licenses texts with the SPDX license identifiers in Colibri/Apalis DTS files. Acked-by: Marcel Ziswiler Signed-off-by: Igor Opaniuk --- v4: - no changes v3: - Add Marcel's Acked-by tag - Remove un-needed parentheses in SPDX line v2: - Address Stefan's comment: replace

[PATCH v4 2/2] ARM: dts: tegra124-apalis: convert to SPDX license tags

Replace boiler plate licenses texts with the SPDX license identifiers in Colibri/Apalis DTS files. Acked-by: Marcel Ziswiler Signed-off-by: Igor Opaniuk --- v4: - Fix typo in the SPDX tag, noticed by Marc (probably was introduced when manually removing unneeded brackets) v3: - Add Marcel's

Re: [PATCH v3 1/3] module: Prepare for addition of new ro_after_init sections

+++ Joel Fernandes (Google) [10/04/19 15:57 -0400]: For the purposes of hardening modules by adding sections to ro_after_init sections, prepare for addition of new ro_after_init entries which we do in future patches. Create a table to which new entries could be added later. This makes it less

Re: [PATCH v1 1/4] mm/memory_hotplug: Release memory resource after arch_remove_memory()

On 17.04.19 15:12, Michal Hocko wrote: > On Tue 09-04-19 12:01:45, David Hildenbrand wrote: >> __add_pages() doesn't add the memory resource, so __remove_pages() >> shouldn't remove it. Let's factor it out. Especially as it is a special >> case for memory used as system memory, added via

Re: [PATCH] signal: don't silently convert SI_USER signals to non-current pidfd

On Wed, Apr 17, 2019 at 03:16:03PM +0200, Oleg Nesterov wrote: > On 04/17, Christian Brauner wrote: > > > > On Mon, Apr 08, 2019 at 03:13:16PM +0200, Oleg Nesterov wrote: > > > > > > but perhaps it should always fail, even if task_pid(current) == pid. > > > > > > sys_rt_sigqueueinfo() allows to

Re: [PATCH v4 09/16] locking/rwsem: Ensure an RT task will not spin on reader

On Sat, Apr 13, 2019 at 01:22:52PM -0400, Waiman Long wrote: > An RT task can do optimistic spinning only if the lock holder is > actually running. If the state of the lock holder isn't known, there > is a possibility that high priority of the RT task may block forward > progress of the lock

Re: [PATCH] signal: don't silently convert SI_USER signals to non-current pidfd

On 04/17, Christian Brauner wrote: > > On Mon, Apr 08, 2019 at 03:13:16PM +0200, Oleg Nesterov wrote: > > > > but perhaps it should always fail, even if task_pid(current) == pid. > > > > sys_rt_sigqueueinfo() allows to send any siginfo to yourself, but this is > > only needed > > for

[PATCH v3] proc/sysctl: add shared variables for range check

In the sysctl code the proc_dointvec_minmax() function is often used to validate the user supplied value between an allowed range. This function uses the extra1 and extra2 members from struct ctl_table as minimum and maximum allowed value. On sysctl handler declaration, in every source file there

Re: [PATCH v1 1/4] mm/memory_hotplug: Release memory resource after arch_remove_memory()

On Tue 09-04-19 12:01:45, David Hildenbrand wrote: > __add_pages() doesn't add the memory resource, so __remove_pages() > shouldn't remove it. Let's factor it out. Especially as it is a special > case for memory used as system memory, added via add_memory() and > friends. > > We now remove the

Re: [PATCH v1 2/4] mm/memory_hotplug: Make unregister_memory_section() never fail

On 17.04.19 14:45, Oscar Salvador wrote: > On Tue, 2019-04-09 at 12:01 +0200, David Hildenbrand wrote: >> Failing while removing memory is mostly ignored and cannot really be >> handled. Let's treat errors in unregister_memory_section() in a nice >> way, warning, but continuing. >> >> Cc: Greg

Re: [PATCH RFC 1/2] Add polling support to pidfd

On 04/16, Joel Fernandes wrote: > > On Tue, Apr 16, 2019 at 02:04:31PM +0200, Oleg Nesterov wrote: > > > > Could you explain when it should return POLLIN? When the whole process > > exits? > > It returns POLLIN when the task is dead or doesn't exist anymore, or when it > is in a zombie state and

Re: [PATCH v3 14/26] PCI: keystone: Add support for PCIe RC in AM654x Platforms

Hi Lorenzo, On 16/04/19 7:45 PM, Lorenzo Pieralisi wrote: > On Sat, Apr 13, 2019 at 10:26:33AM -0500, Bjorn Helgaas wrote: >> On Mon, Mar 25, 2019 at 03:09:35PM +0530, Kishon Vijay Abraham I wrote: >>> Add PCIe RC support for AM654x Platforms in pci-keystone.c >> >>> +static int

[PATCH] irqchip: stm32: use a platform driver for stm32mp1-exti device

This irqchip driver uses the hwspinlock framework (coprocessor HW regs access concurrency) for the stm32mp1-exti device. Hence, this driver needs to handle the hwspinlock driver dependency using the deferred probe mechanism which requires to move this driver into a platform one with a probe() ops.

Re: [PATCH] signal: don't silently convert SI_USER signals to non-current pidfd

On Mon, Apr 08, 2019 at 03:13:16PM +0200, Oleg Nesterov wrote: > On 03/30, Jann Horn wrote: > > > > --- a/kernel/signal.c > > +++ b/kernel/signal.c > > @@ -3605,16 +3605,11 @@ SYSCALL_DEFINE4(pidfd_send_signal, int, pidfd, int, > > sig, > > if (unlikely(sig != kinfo.si_signo)) > >

Re: [PATCH v4 08/16] locking/rwsem: Make rwsem_spin_on_owner() return owner state

On Wed, Apr 17, 2019 at 02:41:01PM +0200, Peter Zijlstra wrote: > On Sat, Apr 13, 2019 at 01:22:51PM -0400, Waiman Long wrote: > > In the special case that there is no active lock and the handoff bit > > is set, optimistic spinning has to be stopped. > > > @@ -500,9 +521,19 @@ static noinline

[GIT PULL v2] PHY: For 5.1 -rc

Hi Greg, Please find the updated pull request for 5.1 -rc. I've removed the lengthy ti-pipe3 PHY driver changes to follow the TRM sequence. This will be included in 5.2 -rc1 pull request. I've also added an additional patch to fix gadget mode working in Allwinner's sun4i-usb PHY driver. Let me

Re: [RFC PATCH] mm/workingset : judge file page activity via timestamp

On Wed 17-04-19 20:26:22, Zhaoyang Huang wrote: > repost the feedback by under Johannes's comment Please follow up in the original email thread. Fragmenting the discussion is exactly what I wanted... -- Michal Hocko SUSE Labs

Re: [PATCH 0/7] introduce cpu.headroom knob to cpu controller

On Wed, 10 Apr 2019 at 21:43, Song Liu wrote: > > Hi Morten, > > > On Apr 10, 2019, at 4:59 AM, Morten Rasmussen > > wrote: > > > > > > The bit that isn't clear to me, is _why_ adding idle cycles helps your > > workload. I'm not convinced that adding headroom gives any latency > > improvements

Re: RFC: on adding new CLONE_* flags [WAS Re: [PATCH 0/4] clone: add CLONE_PIDFD]

On Wed, Apr 17, 2019 at 02:03:16PM +0200, Enrico Weigelt, metux IT consult wrote: > On 16.04.19 23:31, Andy Lutomirski wrote: > > >> How exactly would the pidfd improve this scenario ? > >> IMHO, would just need to pass the inherited fd's to that daemon (eg. > >> via unix socket) which then sets

[PATCH v2] ARM: debug-ll: add default address for digicolor

The digicolor platform has three UARTs, but the Kconfig.debug file explicitly lists port zero as the one to be used for the console, while not providing any default values. This can get an automated randconfig build stuck in a loop waiting for the user to input the number. As we already know the

Re: [PATCH] ARM: debug-ll: add default address for digicolor

On Wed, Apr 17, 2019 at 6:12 AM Baruch Siach wrote: > On Tue, Apr 16, 2019 at 03:17:30PM +0200, Arnd Bergmann wrote: > > The digicolor platform has three UARTs, but the Kconfig.debug > > file explicitly lists port zero as the one to be used for the > > console, while not providing any default

Re: [PATCH v4 08/16] locking/rwsem: Make rwsem_spin_on_owner() return owner state

On Wed, Apr 17, 2019 at 02:41:01PM +0200, Peter Zijlstra wrote: > On Sat, Apr 13, 2019 at 01:22:51PM -0400, Waiman Long wrote: > > In the special case that there is no active lock and the handoff bit > > is set, optimistic spinning has to be stopped. > > > @@ -500,9 +521,19 @@ static noinline

<    1   2   3   4   5   6   7   8   9   >