On Wed 2017-09-06 19:54:52, Andy Lutomirski wrote:
> Patch 1 is the fix. Patch 2 is a comment that would have kept me from
> chasing down a false lead.
>
> I've tested patch 2 using CPU hotplug and suspend/resume. I haven't
> tested hibernation or kexec because I don't know how. (If I do
> syst
Hi,
Mainline kernel panics during DLPAR CPU add/remove operation.
Machine Type: Power8 PowerVM LPAR
kernel 4.13.0
gcc 6.3.1
config: attached
trace messaged:
-
drmgr: -c cpu -d 5 -w 30 -r
cpu 8 (hwid 8) Ready to die...
cpu 9 (hwid 9) Ready to die...
cpu 10 (hwid 10) Ready to die...
c
Hi,
We have one query regarding the behavior of RCU expedited grace period,
for scenario where resched_cpu() in sync_sched_exp_handler() fails to
acquire the rq lock and returns w/o setting the need_resched. In this
case, how do we ensure that the CPU notify rcu about the
end of sched grace perio
On 09/14/2017 05:51 PM, Levin, Alexander (Sasha Levin) wrote:
From: James Liao
[ Upstream commit f235c7e7a75325f28a33559a71f25a0eca6112db ]
Add MT2701 subsystem clock controllers, inlcude mmsys, imgsys,
vdecsys, hifsys, ethsys and bdpsys.
Signed-off-by: James Liao
Signed-off-by: Matthias B
From: Changbin Du
There are some trace options to control what gets printed in the trace
output or manipulate the tracers. This patch add a commandline option
to set it.
Example:
perf ftrace -t function -O noprint-parent --trace-funcs "__kmalloc" -a
Xorg-1874 [002] 4107.182911
On Thu 2017-09-07 10:07:09, Ingo Molnar wrote:
>
> * Linus Torvalds wrote:
>
> > On Tue, Sep 5, 2017 at 2:40 PM, Ingo Molnar wrote:
> > >
> > > Hm, just as background, there are no regression reports I'm aware of
> > > against any of these trees, plus most of the dangerous commits have
> > > be
On 15/09/2017 05:48, Wanpeng Li wrote:
> 2017-09-14 5:45 GMT+08:00 Paolo Bonzini :
>> On 13/09/2017 13:03, Wanpeng Li wrote:
>>> From: Wanpeng Li
>>>
>>> [ cut here ]
>>> WARNING: CPU: 4 PID: 5280 at /home/kernel/linux/arch/x86/kvm//vmx.c:11394
>>> nested_vmx_vmexit+0xc2b
On 15/09/2017 13:26, Paolo Bonzini wrote:
> On 15/09/2017 05:48, Wanpeng Li wrote:
>> 2017-09-14 5:45 GMT+08:00 Paolo Bonzini :
>>> On 13/09/2017 13:03, Wanpeng Li wrote:
From: Wanpeng Li
[ cut here ]
WARNING: CPU: 4 PID: 5280 at /home/kernel/linux/arch
Em Fri, 15 Sep 2017 06:18:20 -0400
Satendra Singh Thakur escreveu:
> Hello Mr Chehab,
> Thanks for the comments.
> I have modified dtv_property_process_set and
> also added documentation.
> Please let me know if any further modifications required.
That's a way better. Just a few minor things to
Hi all,
Linaro has announced the support for ILP32-enabled cross-toolchain:
https://lists.linaro.org/pipermail/linaro-toolchain/2017-September/006247.html
Files:
http://snapshots.linaro.org/components/toolchain/binaries/7.1-2017.08-rc1/aarch64-linux-gnu_ilp32/
Yury
On Mon, Jun 19, 2017 at 06:49
On 14/09/2017 00:22, Davidlohr Bueso wrote:
> On Wed, 13 Sep 2017, Paolo Bonzini wrote:
>> has_sleeper*s*. Can fix when committing.
>
> So for regular waitqueues we have it singular, which is why I kept
> that name -- albeit sleepers() being better suited, yes. I don't think
> we want to rename i
On 13/09/2017 22:08, Davidlohr Bueso wrote:
> A comment might serve future readers.
>
> Signed-off-by: Davidlohr Bueso
> ---
> arch/x86/kvm/lapic.c | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/arch/x86/kvm/lapic.c b/arch/x86/kvm/lapic.c
> index aaf10b6f5380..69c5612be786 100644
On Fri 15-09-17 17:23:24, Kemi Wang wrote:
> This patch adds a tunable interface that allows VM stats configurable, as
> suggested by Dave Hansen and Ying Huang.
>
> When performance becomes a bottleneck and you can tolerate some possible
> tool breakage and some decreased counter precision (e.g.
On Fri 15-09-17 17:23:25, Kemi Wang wrote:
[...]
> @@ -2743,6 +2745,17 @@ static inline void zone_statistics(struct zone
> *preferred_zone, struct zone *z)
> #ifdef CONFIG_NUMA
> enum numa_stat_item local_stat = NUMA_LOCAL;
>
> + /*
> + * skip zone_statistics() if vmstat is a coa
On 13/09/2017 22:08, Davidlohr Bueso wrote:
> The following patches fix and/or justify (in baby steps) some of the
> callers. The main exception is s390, which I didn't follow how ->valid_wakeup
> can get hoisted as kvm_vcpu_block does not use that in the wait loop.
valid_wakeup is just an optimiz
Dne 15.9.2017 v 02:16 Taras Kondratiuk napsal(a):
Hi
In our devices under low memory conditions we often get into a trashing
state when system spends most of the time re-reading pages of .text
sections from a file system (squashfs in our case). Working set doesn't
fit into available page cache,
On 2017/09/15 2:14, Yang Shi wrote:
> @@ -1274,6 +1276,29 @@ static int slab_show(struct seq_file *m, void *p)
> return 0;
> }
>
> +void show_unreclaimable_slab()
> +{
> + struct kmem_cache *s = NULL;
> + struct slabinfo sinfo;
> +
> + memset(&sinfo, 0, sizeof(sinfo));
> +
> +
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 711aab1dbb324d321e3d84368a435a78908c7bce
commit: 799c43415442414b1032580c47684cb709dfed6d kbuild: thin archives make
default for all archs
date: 3 months ago
config: frv-defconfig (attached as .config)
com
Hi Michal and Geert, +Nicolas and Masahiro
On 14.9.2017 11:19, Geert Uytterhoeven wrote:
> Hi Michal,
>
> On Thu, Sep 14, 2017 at 11:07 AM, Michal Hocko wrote:
>> I've started seeing the following compilation failures with microblaze
>> with the current linux-next (next-20170913). I have no idea
On Tue, Aug 22, 2017 at 06:52:48PM +0200, Borislav Petkov wrote:
> As always, the devil is in the detail.
Ok, actually we can make this much simpler by using a static key. A
conceptual patch below - I only need to fix that crazy include hell I'm
stepping into with this.
In any case, we were talki
Wait until we know the exact number of ppas to be sent to the device,
before allocating the bio.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-rb.c| 5 +++--
drivers/lightnvm/pblk-write.c | 20 ++--
drivers/lightnvm/pblk.h | 4 ++--
3 files changed, 15 inse
For consistency with the rest of pblk, use rqd->end_io to point to the
function taking care of ending the request on the completion path.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-core.c | 7 ---
drivers/lightnvm/pblk-read.c | 5 ++---
2 files changed, 2 insertions(+), 10 dele
On REQ_PREFLUSH, directly tag the I/O context flags to signal a flush in
the write to cache path, instead of finding the correct entry context
and imposing a memory barrier. This simplifies the code and might
potentially prevent race conditions when adding functionality to the
write path.
Signed-o
Hi,
On 14/09/2017 19:06, Marc Zyngier wrote:
> On Thu, Sep 14 2017 at 10:57:28 am BST, Eric Auger
> wrote:
>> At the moment, the in-kernel emulated ITS is not properly reset.
>> On guest restart/reset some registers keep their old values and
>> internal structures like device, ITE, collection li
Refactor the rqd allocation and free functions so that all I/O types can
use these helper functions.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-core.c | 40 ++--
drivers/lightnvm/pblk-read.c | 2 --
drivers/lightnvm/pblk-recovery.c | 2
Use a constant to set the maximum number of inflight GC requests
allowed.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-gc.c | 4 ++--
drivers/lightnvm/pblk.h| 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/lightnvm/pblk-gc.c b/drivers/lightnvm/pblk-g
Each request type sent to the LightNVM subsystem requires different
metadata. Until now, we have tailored this metadata based on write, read
and erase commands. However, pblk uses different metadata for internal
writes that do not hit the write buffer. Instead of abusing the metadata
for reads, cre
Simplify put bio by doing it on bio end_io instead of manually putting
it on the completion path.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-core.c | 10 +++---
drivers/lightnvm/pblk-read.c | 1 -
drivers/lightnvm/pblk-recovery.c | 1 -
drivers/lightnvm/pblk-write.c
This patchset is a general cleanup to improve code readability.
Javier González (11):
lightnvm: pblk: use constant for GC max inflight
lightnvm: pblk: normalize ppa namings
lightnvm: pblk: refactor read lba sanity check
lightnvm: pblk: simplify data validity check on GC
lightnvm: pblk: r
Simplify the part of the garbage collector where data is read from the
line being recycled and moved into an internal queue before being copied
to the memory buffer. This allows to get rid of a dedicated function,
which introduces an unnecessary dependency on the code.
Signed-off-by: Javier Gonzál
When a line is selected for recycling by the garbage collector (GC), the
line state changes and the invalid bitmap is frozen, preventing
invalidations from happening. Throughout the GC, the L2P map is checked
to verify that not data being recycled has been updated. The last check
is done before the
Refactor lba sanity check on read path to avoid code duplication.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-read.c | 29 ++---
1 file changed, 10 insertions(+), 19 deletions(-)
diff --git a/drivers/lightnvm/pblk-read.c b/drivers/lightnvm/pblk-read.c
index
Normalize the way we name ppa variables to improve code readability.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-core.c | 48 +++-
1 file changed, 25 insertions(+), 23 deletions(-)
diff --git a/drivers/lightnvm/pblk-core.c b/drivers/lightnvm/
On 09/14/2017 04:40 AM, Jarkko Sakkinen wrote:
On Wed, Sep 13, 2017 at 11:39:03AM -0700, Peter Huewe wrote:
Am 12. September 2017 17:45:08 GMT-07:00 schrieb Jarkko Sakkinen
:
On Wed, Sep 06, 2017 at 08:56:36AM -0400, Nayna Jain wrote:
The TPM burstcount status indicates the number of bytes
Metadata I/Os are scheduled to minimize their impact on user data I/Os.
When there are enough LUNs instantiated (i.e., enought bandwidth), it is
easy to interleave metadata and data one after the other so that
metadata I/Os are the ones being blocked and not viceversa.
We do this by calculating th
Make sure that the variable controlling block threshold for allocating
extra metadata sectors in case of a line with bad blocks does not get a
negative value. Otherwise, the line will be marked as corrupted and
wasted.
Signed-off-by: Javier González
---
drivers/lightnvm/pblk-init.c | 2 +-
1 fil
When a line is recycled during garbage collection, reads can still be
issued to the line. If the line is freed in the middle of this process,
data corruption might occur.
This patch guarantees that lines are not freed in the middle of reads
that target them (lines). Specifically, we use the existi
As part of pblk's recovery scheme, we store the lba mapped to each
physical sector on the device's out-of-bound (OOB) area.
On the read path, we can use this information to validate that the data
being delivered to the upper layers corresponds to the lba being
requested. The cost of this check is
Remove two adjacent assignments to the same location.
In practice, many such occurences are intentional but
this case don't seem to fall into that category.
Done using following coccinelle semantic patch
@@
expression e1,e2,e3;
@@
(
(<+...e1++...+>)=e2;
|
(<+...e1--...+>)=e2;
|
(<+...++e1...+>
pblk schedules user I/O, metadata I/O and erases on the write path in
order to minimize collisions at the media level. Until now, there has
been a dependency between user and metadata I/Os that could lead to a
deadlock as both take the per-LUN semaphore to schedule submission.
This path removes th
A partial read I/O in pblk is an I/O where some sectors reside in the
write buffer in main memory and some are persisted on the device. Such
an I/O must at least contain 2 lbas, therefore checking for the case
where a single lba is mapped is not necessary.
Signed-off-by: Javier González
---
driv
On 09/13/2017 06:28 AM, Jarkko Sakkinen wrote:
On Wed, Sep 06, 2017 at 08:56:37AM -0400, Nayna Jain wrote:
The existing wait_for_tpm_stat() checks the chip status before
sleeping for 5 msec in a polling loop. For some functions although
the status isn't ready immediately, the status returns e
Hi,
On 14/09/2017 11:40, Sergey Senozhatsky wrote:
> On (09/14/17 11:15), Laurent Dufour wrote:
>> On 14/09/2017 11:11, Sergey Senozhatsky wrote:
>>> On (09/14/17 10:58), Laurent Dufour wrote:
>>> [..]
That's right, but here this is the sequence counter mm->mm_seq, not the
vm_seq one.
>
On 09/13/2017 06:30 AM, Jarkko Sakkinen wrote:
On Wed, Sep 06, 2017 at 08:56:38AM -0400, Nayna Jain wrote:
Currently, get_burstcount() function sleeps for 5msec in a loop
before retrying for next query to burstcount. However, if it takes
lesser time for TPM to return, this 5 msec delay is long
Linus,
I2C has two more, new drivers: Altera FPGA and STM32F7.
Please pull.
Thanks,
Wolfram
The following changes since commit 46c1e79fee417f151547aa46fae04ab06cb666f4:
Merge branch 'perf-urgent-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2017-09-13 12:24:20
-
In pci_enable_bridge() pci_enable_device() is called before calling
pci_set_master(), thus check pci_is_enabled() becomes true in the
middle of this sequence. As a result in pci_enable_device_flags()
concurrent enable of device on same bridge could think that this
bridge is completely enabled, but
On Fri, Sep 15, 2017 at 6:04 AM, abdul wrote:
> Hi,
>
> Mainline kernel panics during DLPAR CPU add/remove operation.
>
> Machine Type: Power8 PowerVM LPAR
> kernel 4.13.0
Did 4.12 work or when was it last working? I'm not seeing anything
recent in the DT code that looks suspicious.
Rob
On Fri, 15 Sep 2017, Thomas Gleixner wrote:
> On Fri, 15 Sep 2017, kernel test robot wrote:
> > [0.035023] CPU: Intel Common KVM processor (family: 0xf, model: 0x6,
> > stepping: 0x1)
> > [0.042302] Performance Events: unsupported Netburst CPU model 6 no PMU
> > driver, software events o
This commit makes Cavium PCI ACS quirk applicable only to Cavium
ThunderX (CN81/83/88XX) PCIE Root Ports which has limited PCI capabilities
in terms of no ACS support advertisement. However, the RTL internally
implements similar protection as if ACS had completion redirection,
blocking and validati
Hi folks,
did anyone already use the imx6's csi port for anything other than
cameras ?
I'm thinking about using it for an ADC (in fpga). Theoretically it
should be possible to transfer non-video data, but the question
here is whether the ipu might interfer here (eg. trying colorspace
conversion
On 13/09/17 11:23, Juergen Gross wrote:
> On 12/09/17 20:54, Andrew Cooper wrote:
>> On 08/09/17 15:48, Juergen Gross wrote:
>>> static void gnttab_request_version(void)
>>> {
>>> - int rc;
>>> + long rc;
>>> struct gnttab_set_version gsv;
>>>
>>> - gsv.version = 1;
>>> + rc = HYPER
Hi Michal,
2017-09-15 21:17 GMT+09:00 Michal Simek :
> Hi Michal and Geert, +Nicolas and Masahiro
>
> On 14.9.2017 11:19, Geert Uytterhoeven wrote:
>> Hi Michal,
>>
>> On Thu, Sep 14, 2017 at 11:07 AM, Michal Hocko wrote:
>>> I've started seeing the following compilation failures with microblaze
On Fri, Sep 15, 2017 at 01:21:52PM +0800, shuw...@redhat.com wrote:
> From: Shu Wang
>
> Kmemleak reports about a thousand false positives for fusion->
> cmd_list[]. Root casue is the cmd_list objects are allocated from
> slab allocator, and stored its pointer in object allocated by page
> alloca
On Thu, Sep 14, 2017 at 02:11:15PM +0200, Johannes Thumshirn wrote:
> Add info prints in sample kprobe handlers for S/390
>
> Signed-off-by: Johannes Thumshirn
> ---
> samples/kprobes/kprobe_example.c | 8
> 1 file changed, 8 insertions(+)
Applied, thanks!
Hi!
> > After commit 9caf25f996e8, user for CMA memory should use to check
> > PageHighmem in order to get proper virtual address of the page. If
> > someone doesn't use it, it is possible to use wrong virtual address
> > and it then causes the use of wrong physical address.
> > CONFIG_DEBUG_VIRTU
>>> On 15.09.17 at 15:00, wrote:
> So I've found the data I've searched in the hypervisor. The maximum
> frame number to expect can be calculated from max_page, mem_hotplug
> and the maximum physical address from cpuid node 0x8008. If
> CONFIG_BIGMEM isn't defined in Xen it is 16TB max.
>
> T
Many thinkpad laptops and convertibles provide the GMMS method to
resolve how far the laptop has been opened and whether it has been
converted into tablet mode. This allows reporting a more precise tablet
mode state to userspace.
The current implementation only reports a summarized tablet mode sta
On 15/09/17 15:21, Jan Beulich wrote:
On 15.09.17 at 15:00, wrote:
>> So I've found the data I've searched in the hypervisor. The maximum
>> frame number to expect can be calculated from max_page, mem_hotplug
>> and the maximum physical address from cpuid node 0x8008. If
>> CONFIG_BIGMEM
On Tue 2017-09-05 08:06:41, Prarit Bhargava wrote:
> printk.time=1/CONFIG_PRINTK_TIME=1 adds a unmodified local hardware clock
> timestamp to printk messages. The local hardware clock loses time each
> day making it difficult to determine exactly when an issue has occurred in
> the kernel log, and
On Thursday 07 September 2017 16:30:38 Joonsoo Kim wrote:
> If it doesn't help, is there a way to test n900 configuration in QEMU?
Hi Joonsoo, linaro version of QEMU has support for n900 machine. For
more information how to prepare & run kernel image see this email:
https://lists.denx.de/pipermail
On 15.09.2017 10:23, Bjorn Helgaas wrote:
This reverts commit 40f11adc7cd9281227f0a6a627d966dd0a5f0cd9.
Jens found that iwlwifi firmware loading failed on a Lenovo X1 Carbon,
gen4:
iwlwifi :04:00.0: Direct firmware load for iwlwifi-8000C-34.ucode failed
with error -2
iwlwifi :04:
Hi!
I noticed that mainline and pmos kernels have problems if USB is
already attached. My kernels don't seem to have that problem so
.. can you test following?
Against v4.13.
Pavel
diff --git a/drivers/usb/gadget/udc/core.c b/d
Gidday,
The Linux man-pages maintainer proudly announces:
man-pages-4.13 - man pages for Linux
This release resulted from patches, bug reports, reviews, and
comments from around 40 contributors. The release is rather
larger than average. (The context diff runs to more than 90k
lines.) The
Stephen Hemminger writes:
> On Fri, 11 Aug 2017 10:03:59 -0700
> k...@exchange.microsoft.com wrote:
>
>> From: K. Y. Srinivasan
>>
>> This patch handles the following issues that were observed when we are
>> handling racing channel offer message and rescind message for the same
>> offer:
>>
>>
On 09/05/2017 08:15 AM, Thomas Gleixner wrote:
> On Tue, 5 Sep 2017, Prarit Bhargava wrote:
>> +static struct tk_fast tk_fast_mono cacheline_aligned = {
>> +.base = {
>> +(struct tk_read_base){
>> +.clock = &dummy_clock,
>> +},
>> +(
On Fri, 15 Sep 2017, Harsha Sharma wrote:
> Remove two adjacent assignments to the same location.
> In practice, many such occurences are intentional but
> this case don't seem to fall into that category.
> Done using following coccinelle semantic patch
>
> @@
> expression e1,e2,e3;
> @@
>
> (
>
Hi Konstantin,
On Fri, Sep 15, 2017 at 6:18 PM, Konstantin Khlebnikov
wrote:
> In pci_enable_bridge() pci_enable_device() is called before calling
> pci_set_master(), thus check pci_is_enabled() becomes true in the
> middle of this sequence. As a result in pci_enable_device_flags()
> concurrent e
Vitaly Kuznetsov writes:
> Stephen Hemminger writes:
>
>> On Fri, 11 Aug 2017 10:03:59 -0700
>> k...@exchange.microsoft.com wrote:
>>
>>> From: K. Y. Srinivasan
>>>
>>> This patch handles the following issues that were observed when we are
>>> handling racing channel offer message and rescind
On Fri, Sep 15, 2017 at 10:06:24AM +0200, Miklos Szeredi wrote:
> And, btw. I also hate all the hacks we need to do in the VFS for the
> sake of overlayfs. It may actually end up all being removed and all
> the stacking moved to overlayfs; that's something I'd really like to
> look at. All of th
While the core of the backup mode for SAMA5D2 has been integrated in
v4.13, it is far from complete. Individual controllers in the chip have
drivers that do not support the reset of the registers during suspend,
and they need to be adapted to handle it.
The first patch uses the clock wakeup code f
During backup mode, the contents of all registers will be cleared as the
SoC will be completely powered down. For a product that boots on NAND
Flash memory, the bootloader will obviously use the related controller
to read the Flash and correct any detected error in the memory, before
handling back
It is not normal for the PMECC to fail when trying to fix ECC errors.
Report these cases as errors.
Signed-off-by: Romain Izard
---
drivers/mtd/nand/atmel/pmecc.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/nand/atmel/pmecc.c b/drivers/mtd/nand/atmel/pmecc.
The atmel serial port driver reported the following warning on suspend:
atmel_usart f802.serial: ttyS1: Unable to drain transmitter
As the ATMEL_US_TXEMPTY status bit in ATMEL_US_CSR is always cleared
when the transmitter is disabled, we need to know the transmitter's
state to return the real
The controller used by a flexcom module is configured at boot, and left
alone after this. As the configuration will be lost after backup mode,
restore the state of the flexcom driver on resume.
Signed-off-by: Romain Izard
---
drivers/mfd/atmel-flexcom.c | 65 ++---
When an Atmel SoC is suspended with the backup mode, the USB bus will be
powered down. As this is expected, do not return an error to the driver
core when ehci_resume detects it.
Signed-off-by: Romain Izard
---
drivers/usb/host/ehci-atmel.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Save and restore registers for the PWM on suspend and resume, which
makes hibernation and backup modes possible.
Signed-off-by: Romain Izard
---
drivers/pwm/pwm-atmel-tcb.c | 63 +++--
1 file changed, 61 insertions(+), 2 deletions(-)
diff --git a/drivers/
From: Romain Izard
When an AT91 programmable clock is declared in the device tree, register
it into the Power Management Controller driver. On entering suspend mode,
the driver saves and restores the Programmable Clock registers to support
the backup mode for these clocks.
Signed-off-by: Romain
The contents of the System Clock Status Register (SCSR) needs to be
restored into the System Clock Enable Register (SCER).
As the bootloader will restore some clocks by itself, the issue can be
missed as only the USB controller, the LCD controller, the Image Sensor
controller and the programmable
On Fri, Sep 15, 2017 at 03:58:05PM +0200, Miklos Szeredi wrote:
> And here's the prototype. Poof, d_real() is gone.
>
> It definitely has got problems, but just maybe it can be made better than the
> current mess. It *does* solve the ro-rw inconsistency for normal reads (not
> mmaps).
... and m
Wait for the syncronization of all clocks when resuming, not only the
UPLL clock. Do not use regmap_read_poll_timeout, as it will call BUG()
when interrupts are masked, which is the case in here.
Signed-off-by: Romain Izard
---
drivers/clk/at91/pmc.c | 24
1 file changed
On 09/14/2017 07:09 PM, Mikulas Patocka wrote:
> On Tue, 5 Sep 2017, Joe Lawrence wrote:
>> pipe_max_size is assigned directly via procfs sysctl:
>>
>> static struct ctl_table fs_table[] = {
>> ...
>> {
>> .procname = "pipe-max-size",
>>
> Can you please point me to that email?
I assume you can search the email lists just as well as i can.
Andrew
On 09/15/2017 07:24 AM, Borislav Petkov wrote:
On Tue, Aug 22, 2017 at 06:52:48PM +0200, Borislav Petkov wrote:
As always, the devil is in the detail.
Ok, actually we can make this much simpler by using a static key. A
conceptual patch below - I only need to fix that crazy include hell I'm
s
On 09/15/2017 04:49 AM, Michal Hocko wrote:
> Why do we need an auto-mode? Is it safe to enforce by default.
Do we *need* it? Not really.
But, it does offer the best of both worlds: The vast majority of users
see virtually no impact from the counters. The minority that do need
them pay the cost
From: Markus Elfring
Date: Fri, 15 Sep 2017 16:15:47 +0200
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/media/platform/soc_camera/sh_mobile_ceu_camera.c | 4 +---
1 f
On Fri 15-09-17 07:16:23, Dave Hansen wrote:
> On 09/15/2017 04:49 AM, Michal Hocko wrote:
> > Why do we need an auto-mode? Is it safe to enforce by default.
>
> Do we *need* it? Not really.
>
> But, it does offer the best of both worlds: The vast majority of users
> see virtually no impact from
On Thu, Sep 14, 2017 at 02:15:36PM -0700, Jiri Kosina wrote:
> From: Jiri Kosina
>
> ... therefore make it static.
>
> Fixes: 439e7271dc2 ("livepatch: introduce shadow variable API")
> Signed-off-by: Jiri Kosina
> ---
>
> Sorry for not having spotted this before pushing out.
>
> kernel/livep
On 09/15/2017 06:28 AM, Petr Mladek wrote:
I am still slightly nervous that external tools would need updating.
Also they might have troubles to interpret the time stamps especially
when the source is changed at runtime via
/sys/module/printk/parameters/time.
My comment below is a rehash/summary
On 09/14/2017 05:16 PM, Taras Kondratiuk wrote:
Hi
In our devices under low memory conditions we often get into a trashing
state when system spends most of the time re-reading pages of .text
sections from a file system (squashfs in our case). Working set doesn't
fit into available page cache, so
On Tue, Sep 12, 2017 at 4:57 PM, Palmer Dabbelt wrote:
> This patch adds documentation for the platform-level interrupt
> controller (PLIC) found in all RISC-V systems. This interrupt
> controller routes interrupts from all the devices in the system to each
> hart-local interrupt controller.
It
On Thu 14-09-17 17:16:27, Taras Kondratiuk wrote:
> Hi
>
> In our devices under low memory conditions we often get into a trashing
> state when system spends most of the time re-reading pages of .text
> sections from a file system (squashfs in our case). Working set doesn't
> fit into available pa
On 09/15/2017 09:28 AM, Petr Mladek wrote:
>
> I am still slightly nervous that external tools would need updating.
> Also they might have troubles to interpret the time stamps especially
> when the source is changed at runtime via
> /sys/module/printk/parameters/time.
In earlier versions I had
On Fri, Sep 15, 2017 at 09:13:00AM -0500, Brijesh Singh wrote:
> thanks for the suggestion Boris, it will make patch much simpler.
> I will try this out.
It won't build - this was supposed to show the general idea.
I need to figure out the include hell first.
--
Regards/Gruss,
Boris.
SUSE
On Fri, Sep 15 2017 at 11:05:25 am BST, zijun_hu wrote:
> On 09/15/2017 03:20 AM, Marc Zyngier wrote:
>> On Thu, Sep 14 2017 at 1:15:14 pm BST, zijun_hu wrote:
>>> From: zijun_hu
>>>
>>> get_cpu_number() doesn't use existing helper to iterate over possible
>>> CPUs, so error happens in case of
On 09/15/2017 09:40 AM, Borislav Petkov wrote:
I need to figure out the include hell first.
I am working with slightly newer patch sets -- in that patch Tom has
moved the sev_active() definition in arch/x86/mm/mem_encrypt.c and I
have no issue using your recommended (since I no longer need th
On Thu, Sep 14, 2017 at 10:50:27PM -0700, Linus Torvalds wrote:
> This is still wrong.
>
> (a) there is no explanation for why we need that exclusive lock in the
> first place
>
> Why should a read need exclusive access? You'd think shared is sufficient.
> But regardless, it needs *explanation*.
>> @@ -338,14 +346,18 @@ static struct reserved_mem
>> *dma_reserved_default_memory __initdata;
>> static int rmem_dma_device_init(struct reserved_mem *rmem, struct device
>> *dev)
>> {
>> struct dma_coherent_mem *mem = rmem->priv;
>> + int ret;
>> +
>> + if (!mem)
>> +
My recent bug fix introduced another bug, which caused rmem_dma_device_init
to always fail, as rmem->priv is never set to anything.
This restores the previous behavior, calling dma_init_coherent_memory()
whenever ->priv is NULL.
Fixes: d35b0996fef3 ("dma-coherent: fix dma_declare_coherent_memory(
A new feature Range Selector (RS) has been added to GIC specification
in order to support more than 16 CPUs at affinity level 0. New fields
are introduced in SGI system registers (ICC_SGI0R_EL1, ICC_SGI1R_EL1
and ICC_ASGI1R_EL1) to relax an artificial limit of 16 at level 0.
- A new RSS field in I
101 - 200 of 510 matches
Mail list logo
