On Thu, Jun 13, 2019 at 08:42:10AM -0600, Rob Herring wrote:
> Currently, the binding examples are just built with dtc. dtc recently
> gained the support necessary to output the examples in YAML format
> (commit 87963ee20693 ("livetree: add missing type markers in generated
> overlay properties").
On Thu, Jun 13, 2019 at 4:15 PM Hillf Danton wrote:
>
>
> Hello Dmitry
>
> On Thu, 13 Jun 2019 20:12:06 +0800 Dmitry Vyukov wrote:
> > On Thu, Jun 13, 2019 at 2:07 PM Hillf Danton wrote:
> > >
> > > Hello Jason
> > >
> > > On Thu, 13 Jun 2019 17:10:39 +0800 Jason Wang wrote:
> > > >
> > > > This
The kernel provides no architecture-independent mechanism to get the
size of the virtual address space of a task (userspace process) without
brute-force calculation. This patch allows a user to easily retrieve
this value via a new VmTaskSize entry in /proc/$$/status.
Signed-off-by: Joel Savitz
--
After all the workqueue and the timer rework, we can finally make the
worker_pool lock raw.
The lock is not held over an unbounded period of time/iterations.
Signed-off-by: Sebastian Andrzej Siewior
---
kernel/workqueue.c | 164 ++---
1 file changed, 82 in
The swait_event_lock_irq() is inspired by wait_event_lock_irq(). This is
required by the workqueue code once it switches to swait.
Signed-off-by: Sebastian Andrzej Siewior
---
include/linux/swait.h | 14 ++
1 file changed, 14 insertions(+)
diff --git a/include/linux/swait.h b/includ
I just did a quick test on a patched kernel to check on that "no
longer affine to..." message:
# nproc
64
# taskset -p 4 $$
pid 2261's current affinity mask:
pid 2261's new affinity mask: 4
# echo off > /sys/devices/system/cpu/cpu2/online
# taskset -p $$
pid 2261's current affini
On Tue, 4 Jun 2019 at 20:52, Krzysztof Kozlowski wrote:
>
> Remove the CONFIG_UEVENT_HELPER_PATH because:
> 1. It is disabled since commit 1be01d4a5714 ("driver: base: Disable
>CONFIG_UEVENT_HELPER by default") as its dependency (UEVENT_HELPER) was
>made default to 'n',
> 2. It is not reco
From: Thomas Gleixner
All callers use GFP_KERNEL. No point in having that argument.
Signed-off-by: Thomas Gleixner
Signed-off-by: Sebastian Andrzej Siewior
---
kernel/workqueue.c | 23 +++
1 file changed, 11 insertions(+), 12 deletions(-)
diff --git a/kernel/workqueue.c b
In order for the workqueue code use raw_spinlock_t typed locking there
must not be a spinlock_t typed lock be acquired. A wait_queue_head uses
a spinlock_t lock for its list protection.
Use a swait based queue head to avoid raw_spinlock_t -> spinlock_t
locking.
Signed-off-by: Sebastian Andrzej Si
Due to the TIMER_IRQSAFE flag, the timer callback is invoked with
disabled interrupts. On -RT the callback is invoked in softirq context
with enabled interrupts. Since the interrupts are threaded, there are
are no in_irq() users. The local_bh_disable() around the threaded
handler ensures that there
From: Thomas Gleixner
None of those functions have any users outside of workqueue.c. Confine
them.
Signed-off-by: Thomas Gleixner
Signed-off-by: Sebastian Andrzej Siewior
---
include/linux/workqueue.h | 4
kernel/workqueue.c| 7 +++
2 files changed, 3 insertions(+), 8 deletio
Hi,
the workqueue code has been reworked in -RT to use raw_spinlock_t based
locking. This change allows to schedule worker from preempt_disable()ed
or IRQ disabled section on -RT. This is the last patch. The previous
patches are prerequisites or tiny cleanup (like patch #1 and #2).
Sebastian
stable-rc/linux-5.1.y boot: 59 boots: 0 failed, 59 passed
(v5.1.9-156-g10f90b20eaf9)
Full Boot Summary:
https://kernelci.org/boot/all/job/stable-rc/branch/linux-5.1.y/kernel/v5.1.9-156-g10f90b20eaf9/
Full Build Summary:
https://kernelci.org/build/stable-rc/branch/linux-5.1.y/kernel/v5.1.9-156-g
On 6/13/19 6:34 AM, David Howells wrote:
> Randy Dunlap wrote:
>
>> What is the problem with inline functions in UAPI headers?
>
> It makes compiler problems more likely; it increases the potential for name
> collisions with userspace; it makes for more potential problems if the headers
> are im
The required clocks needs to be enabled before the first register
access. After commit fe8abf332b8f ("usb: dwc3: support clocks and resets
for DWC3 core"), this happens when the dwc3_core_is_valid function is
called, but the mentioned commit adds that call in the wrong place,
before the clocks are
On 6/13/2019 7:39 PM, Jon Hunter wrote:
On 13/06/2019 11:41, Sameer Pujar wrote:
Add DT nodes for following devices on Tegra186 and Tegra194
* ACONNECT
* ADMA
* AGIC
Signed-off-by: Sameer Pujar
---
changes from previous revision
* fixed size value for ranges property in aconnect
Currently, the binding examples are just built with dtc. dtc recently
gained the support necessary to output the examples in YAML format
(commit 87963ee20693 ("livetree: add missing type markers in generated
overlay properties"). Now just switch the output format and the examples
will be checked ag
> This whole discussion has zero to do with what text format 'ss' outputs.
Would you like to support the clarification of additional data formats
for the usage of specific information by tools for socket statistics
(from the directory “/proc/net” and related ones)?
Regards,
Markus
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid.git for-linus
to receive fixes for HID subsystem; highlights:
=
- regression fixes (reverts) for module loading changes that turned out to
be incompatible with some userspace, from Benjamin Tissoires
- regress
Generated nodes for overlays begin with '_'. The binding examples are
built as overlays in order to allow unresolved phandles, so we need to
allow the generated node names.
Signed-off-by: Rob Herring
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 +-
1 file changed, 1 insertion(+
Peter Zijlstra wrote:
> Basically we fail for:
>
> *x = 1;
> atomic_inc(u);
> smp_mb__after_atomic();
> r0 = *y;
>
> Because, while the atomic_inc() implies memory order, it
> (surprisingly) does not provide a compiler barrier. This then allows
> the compiler to re-order
Hi, Robert,
On 02/21/2019 10:58 PM, Robert Marko wrote:
> On Wed, 20 Feb 2019 at 21:29, wrote:>>
> Hi, Robert,>> On 02/14/2019 10:57 PM, Robert Marko wrote:> >
> Datasheet:
> https://www.winbond.com/resource-files/w25q16jv%20spi%20revg%2003222018%20plus.pdf>
Testing done on Mikrotik Routerb
On Thu, Jun 13, 2019 at 02:24:37PM +0100, Liviu Dudau wrote:
> On Thu, Jun 13, 2019 at 11:08:14AM +0200, Daniel Vetter wrote:
> > On Thu, Jun 13, 2019 at 09:28:13AM +0100, Liviu Dudau wrote:
> > > On Thu, Jun 13, 2019 at 10:17:27AM +0200, Daniel Vetter wrote:
> > > > On Wed, Jun 12, 2019 at 02:26:2
On Fri, Jun 07, 2019 at 10:10:24PM +0900, Naohiro Aota wrote:
> Currently, dev-replace copy all the device extents on source device to the
> target device, and it also clones new incoming write I/Os from users to the
> source device into the target device.
>
> Cloning incoming IOs can break the se
On Tue, 2019-02-26 at 08:57 +0100, Håkon Bugge wrote:
> During certain workloads, the default CM response timeout is too
> short, leading to excessive retries. Hence, make it configurable
> through sysctl. While at it, also make number of CM retries
> configurable.
>
> The defaults are not changed
On 13/06/2019 15:43, Sameer Pujar wrote:
>
> On 6/13/2019 7:39 PM, Jon Hunter wrote:
>> On 13/06/2019 11:41, Sameer Pujar wrote:
>>> Add DT nodes for following devices on Tegra186 and Tegra194
>>> * ACONNECT
>>> * ADMA
>>> * AGIC
>>>
>>> Signed-off-by: Sameer Pujar
>>> ---
>>> changes f
The pm8005_s1 is VDD_GFX, and needs to be on to enable the GPU.
This should be hooked up to the GPU CPR, but we don't have support for that
yet, so until then, just turn on the regulator and keep it on so that we
can focus on basic GPU bringup.
Signed-off-by: Jeffrey Hugo
Reviewed-by: Bjorn Ander
On 6/12/19 11:35 AM, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Jason Baron
> Cc: linux-kernel@vger.kernel.org
> Signe
On Fri, Jun 07, 2019 at 08:18:56PM +0200, Daniel Vetter wrote:
Hi Daniel,
> On Fri, Jun 07, 2019 at 03:03:39PM +, Ayan Halder wrote:
> > One needs to set "(struct drm_device *)->irq_enabled = true" to signal drm
> > core
> > to enable vblank interrupts after the hardware has been initialized
From: Jorge Ramirez
The PMS405 has 5 HFSMPS and 13 LDO regulators,
This commit adds support for one of the 5 HFSMPS regulators (s3) to
the spmi regulator driver.
The PMIC HFSMPS 430 regulators have 8 mV step size and a voltage
control scheme consisting of two 8-bit registers defining a 16-bit
From: Jorge Ramirez
The PMS405 supports 5 SMPS and 13 LDO regulators.
Signed-off-by: Jorge Ramirez-Ortiz
Reviewed-by: Rob Herring
Signed-off-by: Jeffrey Hugo
---
.../regulator/qcom,spmi-regulator.txt | 24 +++
1 file changed, 24 insertions(+)
diff --git
a/Documentat
The PM8005 is used on the msm8998 MTP. The S1 regulator is VDD_GFX, ie
it needs to be on and controlled inorder to use the GPU. Add support to
drive the PM8005 regulators so that we can bring up the GPU on msm8998.
Signed-off-by: Jeffrey Hugo
---
drivers/regulator/qcom_spmi-regulator.c | 169 +
On Fri, Jun 07, 2019 at 10:10:22PM +0900, Naohiro Aota wrote:
> When truncating a file, file buffers which have already been allocated but
> not yet written may be truncated. Truncating these buffers could cause
> breakage of a sequential write pattern in a block group if the truncated
> blocks ar
spmi_regulator_common_get_mode and spmi_regulator_common_set_mode use
multi-level ifs which mirror a switch statement. Refactor to use a switch
statement to make the code flow more clear.
Signed-off-by: Jeffrey Hugo
---
drivers/regulator/qcom_spmi-regulator.c | 28 -
1 f
From: Jorge Ramirez-Ortiz
Signed-off-by: Jorge Ramirez-Ortiz
Signed-off-by: Jeffrey Hugo
---
drivers/regulator/qcom_spmi-regulator.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/regulator/qcom_spmi-regulator.c
b/drivers/regulator/qcom_spmi-regulator.c
index 53a61fb65642.
Document the dt bindings for the PM8005 regulators which are usually used
for VDD of standalone blocks on a SoC like the GPU.
Signed-off-by: Jeffrey Hugo
Reviewed-by: Bjorn Andersson
---
.../devicetree/bindings/regulator/qcom,spmi-regulator.txt | 4
1 file changed, 4 insertions(+)
dif
The MSM8998 MTP reference platform supplies VDD_GFX from s1 of the
pm8005 PMIC. VDD_GFX is needed to turn on the GPU. As we are looking
to bring up the GPU, add the support for pm8005 and wire up s1 in a
basic manner so that we have this dependency out of the way and can
focus on enabling the GPU
On 6/13/19 12:27 AM, Alexander Graf wrote:
>> Where's the context-switching code? Did I just miss it?
>
> I'm not sure I understand the question. With this mechanism, the global
> linear map pages are just not present anymore, so there is no context
> switching needed. For the process local memor
This section lacks links to functions. Add one to simplify reading.
Signed-off-by: Luca Ceresoli
---
Documentation/media/kapi/v4l2-controls.rst | 67 +++---
1 file changed, 35 insertions(+), 32 deletions(-)
diff --git a/Documentation/media/kapi/v4l2-controls.rst
b/Documentation
The tutorial in this section is almost complete, add the one missing bit.
Signed-off-by: Luca Ceresoli
---
Documentation/media/kapi/v4l2-controls.rst | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/media/kapi/v4l2-controls.rst
b/Documentation/media/kapi/v4l2-controls.rst
i
Fix indentation in example C code.
Signed-off-by: Luca Ceresoli
---
Documentation/media/uapi/v4l/extended-controls.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/media/uapi/v4l/extended-controls.rst
b/Documentation/media/uapi/v4l/extended-controls.rst
inde
This section lacks links to struct definitions. Add one where each struct
is introduced.
Signed-off-by: Luca Ceresoli
---
Documentation/media/kapi/v4l2-controls.rst | 18 ++
1 file changed, 10 insertions(+), 8 deletions(-)
diff --git a/Documentation/media/kapi/v4l2-controls.rst
> On Jun 13, 2019, at 7:16 AM, Kirill A. Shutemov wrote:
>
> On Thu, Jun 13, 2019 at 01:57:30PM +, Song Liu wrote:
>>> And I'm not convinced that it belongs here at all. User requested PMD
>>> split and it is done after split_huge_pmd(). The rest can be handled by
>>> the caller as needed.
The code snippet showing how to add controls to the driver’s top-level
struct is present twice, but only the second time it is split in the V4L2
and subdev cases. Consolidate everything at the beginning.
Also remove the "Where foo->bar is of type struct baz" sentences, this
obvious from the code.
On Fri, May 31, 2019 at 11:45:12PM +, Ghannam, Yazen wrote:
> diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
> index 9fa2f205f05c..dd60cf5a3d96 100644
> --- a/drivers/edac/amd64_edac.c
> +++ b/drivers/edac/amd64_edac.c
> @@ -943,91 +943,101 @@ static void prep_chip_selects(s
On Thu, Jun 13, 2019 at 01:57:30PM +, Song Liu wrote:
> > And I'm not convinced that it belongs here at all. User requested PMD
> > split and it is done after split_huge_pmd(). The rest can be handled by
> > the caller as needed.
>
> I put this part here because split_huge_pmd() for file-backe
Registering the same notifier to a hook repeatedly can cause the hook
list to form a ring or lose other members of the list.
case1: An infinite loop in notifier_chain_register can cause soft lockup
atomic_notifier_chain_register(&test_notifier_list, &test_notifier1);
atomic_notifie
Hi Daniel,
On 31.05.2019 13:41, Daniel Lezcano wrote:
>
> Hi Claudiu,
>
>
> On 30/05/2019 09:46, claudiu.bez...@microchip.com wrote:
>> Hi Daniel,
>>
>> Taking into account the discussion on this tread and the fact that we have
>> no answer from Rob on this topic (I'm talking about [1]), what d
On Fri, Jun 07, 2019 at 10:10:15PM +0900, Naohiro Aota wrote:
> When in HMZONED mode, make sure that device super blocks are located in
> randomly writable zones of zoned block devices. That is, do not write super
> blocks in sequential write required zones of host-managed zoned block
> devices as
On 2019-06-13 09:45, Jonas Bonn wrote:
> Hi Max,
>
> On 12/06/2019 12:42, Maxim Mikityanskiy wrote:
>> On 2019-06-11 13:03, Jonas Bonn wrote:
>>> Patch 7dc2bccab0ee37ac28096b8fcdc390a679a15841 introduces a regression
>>> with systemd 241. In that revision, systemd-networkd fails to pass the
>>> r
On Fri, Jun 07, 2019 at 10:10:17PM +0900, Naohiro Aota wrote:
> Sequential allocation is not enough to maintain sequential delivery of
> write IOs to the device. Various features (async compress, async checksum,
> ...) of btrfs affect ordering of the IOs. This patch introduces submit
> buffer to so
Dear Good day
It is with tears that i am writing to you i need your help and
assistance am an aging widow suffering from long time cancer of the
throat and I inherited from my late husband,and I need someone like
you a foreign partner that will withdraw this money then use for
better investments a
Hi Bjorn,
There were many different names along the way to this support merged, and I
think that the naming became almost irrelevant in the end.
Yep, Arnd is right. The "PIO" name contributed a little to my
confusion, but I think the bigger piece was that I read the "indirect
PIO addresses"
On Thu, Jun 13, 2019 at 11:32:47AM +0200, Benjamin Tissoires wrote:
> On Thu, Jun 13, 2019 at 10:49 AM Charles Keepax
> wrote:
> >
> > On Wed, Jun 12, 2019 at 06:27:18PM +0300, Mika Westerberg wrote:
> > > On Tue, Jun 11, 2019 at 01:30:58PM +0100, Charles Keepax wrote:
> > > > In preparation for m
On 13/06/2019 11:41, Sameer Pujar wrote:
> Add DT nodes for following devices on Tegra186 and Tegra194
> * ACONNECT
> * ADMA
> * AGIC
>
> Signed-off-by: Sameer Pujar
> ---
> changes from previous revision
> * fixed size value for ranges property in aconnect
>
> arch/arm64/boot/dts/nvidi
Hello,
This patch series does some cleanup on the code and add a file for Vimc
at the kernel documentation.
Thanks,
André
André Almeida (4):
media: vimc: debayer: Fix typos
media: vimc: Makefile: file cleanup
media: vimc: stream: add missing function documentation
media: docs: cr
On Thu, Jun 13, 2019 at 03:43:21PM +0200, Peter Zijlstra wrote:
> Recent probing at the Linux Kernel Memory Model uncovered a
> 'surprise'. Strongly ordered architectures where the atomic RmW
> primitive implies full memory ordering and
> smp_mb__{before,after}_atomic() are a simple barrier() (such
On Wed, Jun 12, 2019 at 07:57:43PM -0700, Randy Dunlap wrote:
> In yesterday's mmotm, I see this objtool warning:
>
> arch/x86/entry/entry_64.o: warning: objtool: .entry.text+0x908: unreachable
> instruction
I think it's this one again:
https://lkml.kernel.org/r/15ed85f4-bf2e-da91-71c1-46875d
Remove redundant Makefile rules (vimc_capture-objs, ...).
Stop exposing vimc-{common, streamer} as modules, since there's no use
case where they would be individually added/removed from Vimc. As
consequence, remove MODULE_ macros from vimc-{common, streamer}.
`-objs` is fitted for building host p
Fix typo on "tranforming". Add a line break so it keeps under 80 columns.
Fix typo on "[it] need".
Signed-off-by: André Almeida
---
drivers/media/platform/vimc/vimc-debayer.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/media/platform/vimc/vimc-debayer.c
b/d
> -Original Message-
> From: Shawn Guo
> Sent: Wednesday, June 12, 2019 7:45 PM
> To: Leo Li
> Cc: Madalin-cristian Bucur ; Rob Herring
> ; Aisheng Dong ; Vinod Koul
> ; Grant Likely ; moderated
> list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE ker...@lists.infradead.org>; lkml
> Subje
Create vimc documentation file to explain it basics features, it's
topology, how to configure it and to document vimc's subdevices.
Signed-off-by: André Almeida
Suggested-by: Helen Koike
---
Documentation/media/v4l-drivers/index.rst | 1 +
Documentation/media/v4l-drivers/vimc.dot | 22 +
Hi Jonas,
On Thu, Jun 13, 2019 at 11:34:33AM +0200, Jonas Stenvall wrote:
> Fixed a coding style issue, replacing unsigned with unsigned int.
No concerns on my side. FWIW, the 'bare use of unsigned' coding style
inconsistency is quite common in the USB gadget framework [1-2].
Depending on the fe
Add comments at vimc_streamer_s_stream and vimc_streamer_thread, making
the vimc-stream totally documented.
Signed-off-by: André Almeida
---
drivers/media/platform/vimc/vimc-streamer.c | 22 +
1 file changed, 22 insertions(+)
diff --git a/drivers/media/platform/vimc/vimc-str
On Thu, Jun 06, 2019 at 04:40:45PM +0100, Sudeep Holla wrote:
> On Thu, Jun 06, 2019 at 10:20:40AM -0500, Jassi Brar wrote:
> > On Thu, Jun 6, 2019 at 7:51 AM Sudeep Holla wrote:
> >
> > >
> > > > BTW, this is not going to be the end of SCMI troubles (I believe
> > > > that's what his client is).
On 06/12/19 at 07:10pm, Lendacky, Thomas wrote:
> On 6/12/19 1:07 PM, Borislav Petkov wrote:
> > On Wed, Jun 12, 2019 at 04:52:22PM +, Lendacky, Thomas wrote:
> >> I think the discussion ended up being that debuginfo wasn't being stripped
> >> from the kernel and initrd (mainly the initrd). Wh
/linux/commits/Christophe-Leroy/powerpc-8xx-move-CPM1-related-files-from-sysdev-to-platforms-8xx/20190613-182651
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
config: powerpc-ep8248e_defconfig (attached as .config)
compiler: powerpc-linux-gcc (GCC) 7.4.0
reproduce
From: Willem de Bruijn
Deferred static key clean_acked_data_enabled uses the deferred
variants of dec and flush. Do the same for inc.
Signed-off-by: Willem de Bruijn
---
net/ipv4/tcp_input.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp
From: Willem de Bruijn
This interface is currently only defined if CONFIG_JUMP_LABEL. Make it
available also when jump labels are off.
Signed-off-by: Willem de Bruijn
Acked-by: Peter Zijlstra (Intel)
---
include/linux/jump_label_ratelimit.h | 5 +++--
1 file changed, 3 insertions(+), 2 deleti
This patch corrects the SPDX License Identifier style
in header file related to Firmware Drivers for ARM SCMI
Message Protocol.
For C header files Documentation/process/license-rules.rst
mandates C-like comments (opposed to C source files where
C++ style should be used)
Changes made by using a scr
On Wed, Jun 12, 2019 at 10:16:18PM +0300, Jarkko Sakkinen wrote:
> On Mon, Jun 10, 2019 at 03:01:18PM -0700, Douglas Anderson wrote:
> > From: Vadim Sukhomlinov
> >
> > TPM 2.0 Shutdown involve sending TPM2_Shutdown to TPM chip and disabling
> > future TPM operations. TPM 1.2 behavior was differe
> On Jun 13, 2019, at 5:57 AM, Kirill A. Shutemov wrote:
>
> On Wed, Jun 12, 2019 at 03:03:17PM -0700, Song Liu wrote:
>> This patches introduces a new foll_flag: FOLL_SPLIT_PMD. As the name says
>> FOLL_SPLIT_PMD splits huge pmd for given mm_struct, the underlining huge
>> page stays as-is.
>
From: Willem de Bruijn
1. make static_branch_deferred_inc available if !CONFIG_JUMP_LABEL
2. convert the existing STATIC_KEY_DEFERRED_FALSE user to this api
Willem de Bruijn (2):
locking/static_key: always define static_branch_deferred_inc
tcp: use static_branch_deferred_inc for clean_acked_
Hi Felix,
On 13 June 2019 14:02, Felix Riemann wrote:
> Subject: [PATCH] regulator: da9062: Adjust LDO voltage selection minimum value
>
> According to the datasheet the LDO's voltage selection registers have
> a minimum value of 0x2. This offset was not observed by the driver,
> causing the LDO
On Fri, Jun 07, 2019 at 10:10:08PM +0900, Naohiro Aota wrote:
> If a zoned block device is found, get its zone information (number of zones
> and zone size) using the new helper function btrfs_get_dev_zonetypes(). To
> avoid costly run-time zone report commands to test the device zones type
> duri
On Tue, Jun 11, 2019 at 10:12:52PM +0800, John Garry wrote:
Another thought here:
> if (addr < MMIO_UPPER_LIMIT) { \
> ret = read##bw(PCI_IOBASE + addr); \
> } else if (addr >= MMIO_UPPER_LIMIT && addr < IO_SPACE_LIMIT
On Wed, Jun 05, 2019 at 01:11:44PM +0530, Jagan Teki wrote:
> On Tue, Jun 4, 2019 at 8:00 PM Maxime Ripard
> wrote:
> >
> > On Fri, May 24, 2019 at 03:37:36PM +0530, Jagan Teki wrote:
> > > On Fri, May 24, 2019 at 2:18 AM Maxime Ripard
> > > wrote:
> > > >
> > > > On Mon, May 20, 2019 at 02:33:
On Fri, May 31, 2019 at 11:45:11PM +, Ghannam, Yazen wrote:
> From: Yazen Ghannam
>
> ...because AMD Family 17h systems support 2 DIMMs, 4 CS bases, and 2 CS
> masks per channel.
>
> Fixes: 07ed82ef93d6 ("EDAC, amd64: Add Fam17h debug output")
> Signed-off-by: Yazen Ghannam
> ---
> drivers
Hi all,
I still have these patches sitting in my queue and figured I'd repost them.
Last time Linus proposed a "+m" alternative approach, but that generates far
far worse code (I've lost the patch and not re-ran those numbers, but I suppose
I can redo if found important).
These patches have been
Nadav reported that since the this_cpu_*() ops got asm-volatile
constraints on, code generation suffered for do_IRQ(), but since this
is all with IRQs disabled we can use __this_cpu_*().
smp_x86_platform_ipi 234222
-12,+0
smp_kvm_posted_intr_ipi
Nadav Amit reported that commit:
b59167ac7baf ("x86/percpu: Fix this_cpu_read()")
added a bunch of constraints to all sorts of code; and while some of
that was correct and desired, some of that seems superfluous.
The thing is, the this_cpu_*() operations are defined IRQ-safe, this
means the va
Since raw_cpu_xchg() doesn't need to be IRQ-safe, like
this_cpu_xchg(), we can use a simple load-store instead of the cmpxchg
loop.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/percpu.h | 20
1 file changed, 16 insertions(+), 4 deletions(-)
--- a/arch/x8
Nadav reported that code-gen changed because of the this_cpu_*()
constraints, avoid this for select_idle_cpu() because that runs with
preemption (and IRQs) disabled anyway.
Reported-by: Nadav Amit
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/fair.c |5 +++--
1 file changed, 3 inse
Nadav reported that since this_cpu_read() became asm-volatile, many
smp_processor_id() users generated worse code due to the extra
constraints.
However since smp_processor_id() is reading a stable value, we can use
__this_cpu_read().
While this does reduce text size somewhat, this mostly results
On Thu 13 Jun 07:22 PDT 2019, Jeffrey Hugo wrote:
> From: Jorge Ramirez-Ortiz
>
> Signed-off-by: Jorge Ramirez-Ortiz
> Signed-off-by: Jeffrey Hugo
> ---
> drivers/regulator/qcom_spmi-regulator.c | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/regulator/qcom_spmi-regul
Hi Fredrik,
On 6/13/19 6:40 AM, Fredrik Noring wrote:
Hi Guenter,
I don't think I'll have time to do that anytime soon. Not that I know what
exactly to look for in the first place.
I can confirm that there is a problem with mass storage devices and these
local memory patches.
Thanks for t
On Wed, Jun 12, 2019 at 07:31:44PM +0300, roman.stratiie...@globallogic.com
wrote:
> From: Roman Stratiienko
>
> Adding support to nbd to use it as a root device. This code essentially
> provides a minimal nbd-client implementation within the kernel. It opens
> a socket and makes the negotiation
Use r10 instead of r9 to calculate CPU offset as r9 contains
the value from SRR1 which is used later.
Fixes: 1a4b739bbb4f ("powerpc/32: implement fast entry for syscalls on BOOKE")
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/head_booke.h | 6 +++---
1 file changed, 3 insertions(+), 3
Recent probing at the Linux Kernel Memory Model uncovered a
'surprise'. Strongly ordered architectures where the atomic RmW
primitive implies full memory ordering and
smp_mb__{before,after}_atomic() are a simple barrier() (such as MIPS
without WEAK_REORDERING_BEYOND_LLSC) fail for:
*x = 1;
On Thu, Jun 13, 2019 at 5:33 AM Peter Zijlstra wrote:
>
> On Wed, Jun 12, 2019 at 01:56:27PM -0700, Jakub Kicinski wrote:
> > On Wed, 12 Jun 2019 16:25:16 -0400, Willem de Bruijn wrote:
> > > On Wed, Jun 12, 2019 at 3:59 PM Jakub Kicinski
> > > wrote:
> > > >
> > > > On Wed, 12 Jun 2019 15:44:09
Hi,
This all started when Andrea Parri found a 'surprising' behaviour for x86:
http://lkml.kernel.org/r/20190418125412.GA10817@andrea
Basically we fail for:
*x = 1;
atomic_inc(u);
smp_mb__after_atomic();
r0 = *y;
Because, while the atomic_inc() implies memory
From: Bich Hemon
Add idle and no_console_suspend states to uart4 pin configuration.
Signed-off-by: Bich Hemon
Signed-off-by: Erwan Le Ray
diff --git a/arch/arm/boot/dts/stm32mp157a-dk1.dts
b/arch/arm/boot/dts/stm32mp157a-dk1.dts
index 098dbfb..b851f80 100644
--- a/arch/arm/boot/dts/stm32mp15
From: Bich Hemon
Add idle and no_console_suspend states to uart4 pin configuration
Signed-off-by: Bich Hemon
Signed-off-by: Erwan Le Ray
diff --git a/arch/arm/boot/dts/stm32mp157c-ed1.dts
b/arch/arm/boot/dts/stm32mp157c-ed1.dts
index 62a8c78..34cc847 100644
--- a/arch/arm/boot/dts/stm32mp157
Recent probing at the Linux Kernel Memory Model uncovered a
'surprise'. Strongly ordered architectures where the atomic RmW
primitive implies full memory ordering and
smp_mb__{before,after}_atomic() are a simple barrier() (such as x86)
fail for:
*x = 1;
atomic_inc(u);
smp_m
The comment describing the loongson_llsc_mb() reorder case doesn't
make any sense what so ever. Instruction re-ordering is not an SMP
artifact, but rather a CPU local phenomenon. Clarify the comment by
explaining that these issue cause a coherence fail.
For the branch speculation case; if futex_at
Select either pinctrl sleep state in suspend function or default state in
resume function.
Signed-off-by: Bich Hemon
Signed-off-by: Erwan Le Ray
diff --git a/drivers/tty/serial/stm32-usart.c b/drivers/tty/serial/stm32-usart.c
index 9c2b04e..a8f20ba 100644
--- a/drivers/tty/serial/stm32-usart.c
There were no memory barriers on the 32bit implementation of
cmpxchg64(). Fix this.
Cc: Paul Burton
Signed-off-by: Peter Zijlstra (Intel)
---
arch/mips/include/asm/cmpxchg.h |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
--- a/arch/mips/include/asm/cmpxchg.h
+++ b/arch/mips/in
Currently, pinctrl states defines only one "sleep" configuration for pins,
no matter the possible uart low power modes (Rx pin always kept active).
Sleep pin configuration is refined for low power modes:
- "sleep" (no wakeup & console suspend enabled): put pins in analog state
to optimize power
- Mark all usart/uart devices as wakeup source.
- Identify all dedicated interrupts with a specific interrupt name (either
"event" or "wakeup").
- add interrupts-extended wakeup interrupt
Signed-off-by: Erwan Le Ray
diff --git a/arch/arm/boot/dts/stm32mp157c.dtsi
b/arch/arm/boot/dts/stm32mp157
On 6/13/19 1:32 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.126 release.
There are 81 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made
1 - 100 of 1728 matches
Mail list logo
