Currently, all newly added memory blocks remain in 'offline' state unless
someone onlines them, some linux distributions carry special udev rules
like:
SUBSYSTEM=="memory", ACTION=="add", ATTR{state}=="offline", ATTR{state}="online"
to make this happen automatically. This is not a great solution
On Tue, Dec 15, 2015 at 9:56 AM, Toshi Kani wrote:
> On Tue, 2015-12-15 at 09:53 -0800, Dan Williams wrote:
[..]
>> > > > diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
>> > > > index 5eef4cb..5368baa 100644
>> > > > --- a/drivers/acpi/Kconfig
>> > > > +++ b/drivers/acpi/Kconfig
>> > > >
On Tue, Dec 15, 2015 at 05:45:16PM +, Mark Brown wrote:
> On Tue, Dec 15, 2015 at 05:28:37PM +, Mark Rutland wrote:
> > On Tue, Dec 15, 2015 at 05:17:13PM +, Mark Brown wrote:
>
> > > Obviously people are going to get upset if we introduce performance
> > > regressions - but that's tru
> This is the original code:
Really …?
> result = baz();
> if (result)
> goto label;
>
> label:
> go on...
I do not see such a source code structure
at the six places I propose to clean-up.
> I don't find the test->goto label; label: use offensive,
> but if he doe
On Tue, 2015-12-15 at 20:48 +0300, Dan Carpenter wrote:
> On Tue, Dec 15, 2015 at 07:02:31AM -0800, Joe Perches wrote:
> > This is the original code:
> >
> > result = foo();
> > if (result)
> > goto label;
> >
> > result = bar();
> > if (result)
> > goto la
On Tue, Dec 15, 2015 at 09:36:26AM -0800, Peter Hurley wrote:
> Hi Herton,
>
> On 12/14/2015 07:29 PM, Herton R. Krzesinski wrote:
> > pty_unix98_shutdown allows a potential use after free of inode from
> > slave tty->driver_data: if final pty close is called with slave
> > tty_struct, and inode w
This reverts commit 5677d67ae394 ("drm: Stop resetting connector state to
unknown")
Unfortunately, not resetting the connector status to unknown actually
breaks reprobing on suspend/resume in i915, which is important to have
working since it means a user docking their laptop in suspend won't have
This patch fixes address space warnings from sparse. Function
lprocfs_write_helper() accepts user space buffer but was being
passed kernel space buffer by these functions:
contention_seconds_store()
lockless_truncate_store()
Since these functions are used to implement show and store functions of
Sergei Ianovich writes:
> On Tue, 2015-12-15 at 18:02 +0100, Arnd Bergmann wrote:
>> On Tuesday 15 December 2015 19:42:07 Sergei Ianovich wrote:
>> > There are several board-specific devices on LP8x4x: custom FPGA,
>> > custom
>> > UART, custom IRQ on FPGA, custom parallel bus for industrial IO.
>> diff --git a/drivers/staging/lustre/lnet/selftest/conctl.c
>> b/drivers/staging/lustre/lnet/selftest/conctl.c
>> index 556c837..2ca7d0e 100644
>> --- a/drivers/staging/lustre/lnet/selftest/conctl.c
>> +++ b/drivers/staging/lustre/lnet/selftest/conctl.c
>> @@ -679,45 +679,46 @@ static int
>> ls
>> struct libcfs_ioctl_hdr {
>> __u32 ioc_len;
>> @@ -87,6 +88,13 @@ do { \
>> data.ioc_hdr.ioc_len = sizeof(data);\
>> } while (0)
>>
>> +#define LIBCFS_IOC_INIT_V2(data, hdr) \
>> +do {
Hi,
This is v4 of the series. The previous version was posted [1]. I have
dropped the RFC because this has been sitting and waiting for the
fundamental objections for quite some time and there were none. I still
do not think we should rush this and merge it no sooner than 4.6. Having
this in the
On Mon, 2015-12-14 at 19:11 -0800, Greg KH wrote:
> On Mon, Dec 14, 2015 at 04:01:53PM -0800, K. Y. Srinivasan wrote:
> > From: Kamal Mostafa
> >
> > Use the local uapi headers to keep in sync with "recently" added #define's
> > (e.g. VSS_OP_REGISTER1).
> >
> > Fixes: 3eb2094c59e89db2bedd401e23c
On 12/11, Peter Zijlstra wrote:
>
> On Fri, Dec 11, 2015 at 03:30:33AM -0800, Paul Turner wrote:
>
> > > Blergh, all I've managed to far is to confuse myself further. Even
> > > something like the original (+- the EINTR) should work when we consider
> > > the looping, even when mixed with an occasi
From: Michal Hocko
__alloc_pages_slowpath has traditionally relied on the direct reclaim
and did_some_progress as an indicator that it makes sense to retry
allocation rather than declaring OOM. shrink_zones had to rely on
zone_reclaimable if shrink_zone didn't make any progress to prevent
from a
Hi Alan,
On Mon, Dec 14, 2015 at 5:56 PM, Alan Tull wrote:
>> I had an offline discussion with Josh Cartwright about his concerns.
>> He brought up a good
>> point on w.r.t to the way FPGA Area (Bus) deals with things.
>>
>> Currently we only support complete status = "okay" vs "disabled" kind
>
From: Michal Hocko
wait_iff_congested has been used to throttle allocator before it retried
another round of direct reclaim to allow the writeback to make some
progress and prevent reclaim from looping over dirty/writeback pages
without making any progress. We used to do congestion_wait before
0e
On Tue, Dec 15, 2015 at 06:14:19PM +, Simmons, James A. wrote:
>
> >> struct libcfs_ioctl_hdr {
> >>__u32 ioc_len;
> >> @@ -87,6 +88,13 @@ do {\
> >>data.ioc_hdr.ioc_len = sizeof(data);\
> >> } while (0)
> >>
> >
From: Michal Hocko
__alloc_pages_slowpath retries costly allocations until at least
order worth of pages were reclaimed or the watermark check for at least
one zone would succeed after all reclaiming all pages if the reclaim
hasn't made any progress.
The first condition was added by a41f24ea9fd6
On Tue, 2015-12-15 at 19:02 +0100, SF Markus Elfring wrote:
> > This is the original code:
> Really …?
> > result = baz();
> > if (result)
> > goto label;
> >
> > label:
> > go on...
>
> I do not see such a source code structure
> at the six places I propose to clean-up.
>
On Tue, Dec 15, 2015 at 05:53:31PM +, Luck, Tony wrote:
> My current generation cpu has a bit of an issue with recovering from a
> machine check in a "rep mov" ... so I'm working with a version of memcpy
> that unrolls into individual mov instructions for now.
Ah.
> I can drop the "nti" from
On Tue, Dec 08, 2015 at 07:43:47AM +0100, Anton Bondarenko wrote:
> Also removing change introduced in f6ee9b582d2db652497b73c1f117591dfb6d3a90
> since this change only fix usecases with transfer size from 33 to 128 bytes
> and doesn't fix 129 bytes and bigger.
This is a bug fix for stable but it
From: Paul Bolle
Date: Tue, 15 Dec 2015 18:11:27 +0100
> Sascha Levin reported that the syzkaller fuzzer triggered a WARNING in
> ser_gigaset (see https://lkml.kernel.org/g/56587467.8050...@oracle.com ). It
> turned out that ser_gigaset has always deallocated its platform device
> structure incor
On Tue, Dec 15, 2015 at 09:45:40AM -0800, Linus Torvalds wrote:
> On Tue, Dec 15, 2015 at 1:40 AM, Pavel Machek wrote:
> >
> > I tried applying:
> >
> > [PATCH 1/2] x86_32/mm: Set NX in __supported_pte_mask before enabling
> > paging
> >
> > but I still get
> >
> > [2.691897] x86/mm: Found ins
>From f424410bf4a6a0dd6ff88bec808798016f4161a0 Mon Sep 17 00:00:00 2001
From: Kamal Mostafa
Date: Wed, 11 Nov 2015 19:16:59 +
Subject: tools/hv: Use include/uapi with __EXPORTED_HEADERS__
Use the local uapi headers to keep in sync with "recently" added #define's
(e.g. VSS_OP_REGISTER1).
Fixe
From: Michal Hocko
This is based on the idea from Mel Gorman discussed during LSFMM 2015 and
independently brought up by Oleg Nesterov.
The OOM killer currently allows to kill only a single task in a good
hope that the task will terminate in a reasonable time and frees up its
memory. Such a tas
On Sat, 2015-12-12 at 13:48 +0800, Herbert Xu wrote:
> On Fri, Dec 11, 2015 at 08:54:40AM -0800, Tim Chen wrote:
> > Direct call I assume have less overhead. Let me think about
>
> static inline int crypto_ablkcipher_encrypt(struct ablkcipher_request *req)
> {
> struct ablkcipher_tfm *crt =
On Tue, Dec 15, 2015 at 1:07 PM, Lyude wrote:
> This reverts commit 5677d67ae394 ("drm: Stop resetting connector state to
> unknown")
>
> Unfortunately, not resetting the connector status to unknown actually
> breaks reprobing on suspend/resume in i915, which is important to have
> working since i
On Tue, Dec 15, 2015 at 10:27 AM, Dan Williams wrote:
> On Tue, Dec 15, 2015 at 9:53 AM, Luck, Tony wrote:
... and the non-temporal version is the optimal one even though we're
defaulting to copy_user_enhanced_fast_string for memcpy on modern Intel
CPUs...?
>>
>> My current generat
On Tue, 2015-12-15 at 19:26 +0100, SF Markus Elfring wrote:
> > rc = mdc_queue_wait(req);
> > goto out;
> > out:
> > ptlrpc_req_finished(req);
> > return rc;
> > }
> > -
> >
> > I think if the last goto out; is to be removed,
> > then it should be replaced by a
> rc = mdc_queue_wait(req);
> goto out;
> out:
> ptlrpc_req_finished(req);
> return rc;
> }
> -
>
> I think if the last goto out; is to be removed,
> then it should be replaced by a blank line.
>
> It separates the last operation block from the return.
On Tue, Dec 15, 2015 at 01:23:06PM -0500, Rob Clark wrote:
> On Tue, Dec 15, 2015 at 1:07 PM, Lyude wrote:
> > This reverts commit 5677d67ae394 ("drm: Stop resetting connector state to
> > unknown")
> >
> > Unfortunately, not resetting the connector status to unknown actually
> > breaks reprobing
On Tue, Dec 15, 2015 at 06:47:20PM +0100, Vincent Guittot wrote:
> On 15 December 2015 at 18:15, Mark Rutland wrote:
> > On Tue, Dec 15, 2015 at 05:59:34PM +0100, Vincent Guittot wrote:
> >> On 15 December 2015 at 17:41, Mark Rutland wrote:
> >> > On Tue, Dec 15, 2015 at 04:23:18PM +, Catalin
>On Tue, Dec 15, 2015 at 06:14:19PM +, Simmons, James A. wrote:
>>
>> >> struct libcfs_ioctl_hdr {
>> >> __u32 ioc_len;
>> >> @@ -87,6 +88,13 @@ do { \
>> >> data.ioc_hdr.ioc_len = sizeof(data);\
>> >> } while (0)
>> >>
On Tue, Dec 15, 2015 at 9:53 AM, Luck, Tony wrote:
>>> ... and the non-temporal version is the optimal one even though we're
>>> defaulting to copy_user_enhanced_fast_string for memcpy on modern Intel
>>> CPUs...?
>
> My current generation cpu has a bit of an issue with recovering from a
> machine
> kgdb/kdb and the perf event system both present garbage status in dr6
> then subsequently write this status into the thread.debugreg6 variable,
> then in some cases call hw_breakpoint_restore() which writes this
> status back into the dr6 hardware register.
>
I wanted to note here that this is t
On Tue, Dec 15, 2015 at 10:35:49AM -0800, Dan Williams wrote:
> Correction we have MOVNTDQA, but that requires saving the fpu state
> and marking the memory as WC, i.e. probably not worth it.
Not really. Last time I tried an SSE3 memcpy in the kernel like glibc
does, it wasn't worth it. The enhanc
On Tue, Dec 15, 2015 at 02:24:05PM +0100, Linus Walleij wrote:
> On Sun, Dec 13, 2015 at 5:44 PM, Dmitry Torokhov
> wrote:
> > On Sun, Dec 13, 2015 at 8:37 AM, Linus Walleij
> > wrote:
> >> On Wed, Dec 9, 2015 at 6:21 PM, Dmitry Torokhov
> >> wrote:
> >>
> > Hmm, I'd like to get this patch
On Tue, Dec 15, 2015 at 10:21:38AM -0800, Kamal Mostafa wrote:
> >From f424410bf4a6a0dd6ff88bec808798016f4161a0 Mon Sep 17 00:00:00 2001
> From: Kamal Mostafa
> Date: Wed, 11 Nov 2015 19:16:59 +
> Subject: tools/hv: Use include/uapi with __EXPORTED_HEADERS__
Why is all of this mess here?
Ple
Spansion and Winbond have occasionally used the same manufacturer ID,
and they don't support the same features. Particularly, writing SR=0
seems to break read access for Spansion's s25fl064k. Unfortunately, we
don't currently have a way to differentiate these Spansion and Winbond
parts, so rather t
On Tue, Dec 15, 2015 at 9:45 AM, Linus Torvalds
wrote:
> On Tue, Dec 15, 2015 at 1:40 AM, Pavel Machek wrote:
>>
>> I tried applying:
>>
>> [PATCH 1/2] x86_32/mm: Set NX in __supported_pte_mask before enabling
>> paging
>>
>> but I still get
>>
>> [2.691897] x86/mm: Found insecure W+X mapping
On Tue, Dec 15, 2015 at 1:33 PM, Ville Syrjälä
wrote:
> On Tue, Dec 15, 2015 at 01:23:06PM -0500, Rob Clark wrote:
>> On Tue, Dec 15, 2015 at 1:07 PM, Lyude wrote:
>> > This reverts commit 5677d67ae394 ("drm: Stop resetting connector state to
>> > unknown")
>> >
>> > Unfortunately, not resetting
Daniel Vetter writes:
> On Mon, Dec 14, 2015 at 04:26:26PM -0800, Eric Anholt wrote:
>> VC4 wraps the CMA objects in its own structures, so it needs to do its
>> own teardown (waiting for GPU to finish, updating bo_stats tracking).
>> The other CMA drivers are using drm_gem_cma_free_object as the
On Tue, Dec 15, 2015 at 04:50:45PM +, Okash Khawaja wrote:
> This patch fixes address space warnings from sparse. Function
> lprocfs_write_helper() accepts user space buffer but was being
> passed kernel space buffer by these functions:
>
> contention_seconds_store()
> lockless_truncate_store
On 12/14/2015 06:24 PM, Yuyang Du wrote:
>>> On Fri, Dec 11, 2015 at 06:01:45PM -0800, Steve Muckle wrote:
In init_entity_runnable_average() the last_update_time is initialized to
zero. The task is given max load and utilization as a pessimistic
initial estimate.
But if in
On Tue, Dec 15, 2015 at 06:10:03PM +, Mark Rutland wrote:
> On Tue, Dec 15, 2015 at 05:45:16PM +, Mark Brown wrote:
> > > I'm not sure I follow w.r.t. "inherently less information", unless you
> > > mean trying to debug without access to that DTB?
> > If what the kernel knows about the sy
On Tue, 15 Dec 2015, Russell King - ARM Linux wrote:
> On Tue, Dec 15, 2015 at 10:33:25AM +0100, Pali Rohár wrote:
> > So am I understand correctly that solution would be to hack
> > arch/arm/mm/mmu.c to not overwrite page at PHYS_OFFSET?
>
> That's completely unnecessary: there are enough platfo
Hi there. I plan to create a patch that puts additional ELF notes into
core dumps of user processes produced by the kernel. These are desired in
customer field work because 1) we often get a core without access to the
original machine and much of this would remove significant delays and
errors,
Some boards connect the LCD_RESET pin to a reset input on the
display panel. On these boards, this pin must be set to the
proper level for the display to function.
This adds an optional "reset-active" property to the "display"
subnode such that devicetrees can specify the desired polarity
of the
Activate/deactivate the LCD_RESET signal as specified by the
reset-active DT property when the controller is disabled/enabled.
If the property is missing, leave the signal unchanged.
Signed-off-by: Mans Rullgard
---
drivers/video/fbdev/mxsfb.c | 28 +---
1 file changed, 2
On Tue, Dec 15, 2015 at 06:14:19PM +, Simmons, James A. wrote:
>
> >> struct libcfs_ioctl_hdr {
> >>__u32 ioc_len;
> >> @@ -87,6 +88,13 @@ do {\
> >>data.ioc_hdr.ioc_len = sizeof(data);\
> >> } while (0)
> >>
> >
From: Thomas Abraham
For Exynos542x/5800 platforms, add CPU operating points
for migrating from Exynos specific cpufreq driver to using
generic cpufreq driver.
Changes by Bartlomiej:
- split Exynos5420 support from the original patch
- merged Exynos5422 fixes from Ben
Changes by Ben Gamari:
- P
Add cluster regulator supply properties as a preparation to
adding generic cpufreq-dt driver support for Exynos542x and
Exynos5800 based boards.
Cc: Kukjin Kim
Cc: Doug Anderson
Cc: Javier Martinez Canillas
Cc: Andreas Faerber
Cc: Thomas Abraham
Reviewed-by: Krzysztof Kozlowski
Signed-off-by
This patch uses SPLICE_F_PACKET as a flag, representing packetized pipe.
In splice_to_pipe() this flag is converted into PIPE_BUF_FLAG_PACKET on pipe
buffer.
Signed-off-by: Stanislav Kinsburskiy
---
fs/splice.c |8
1 file changed, 8 insertions(+)
diff --git a/fs/splice.c b/fs/splic
> -Original Message-
> From: ja...@microsoft.com [mailto:ja...@microsoft.com]
> Sent: Wednesday, December 9, 2015 2:55 PM
> To: gre...@linuxfoundation.org; KY Srinivasan ; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
> a...@canonical.com; vkuzn...@redhat.
On 12/15/2015 08:36 AM, Herton R. Krzesinski wrote:
> On Tue, Dec 15, 2015 at 08:17:56AM -0800, Peter Hurley wrote:
>>> I also expect in a rare case where all ptmx references are gone/closed,
>>> this also
>>> could happen on final close when the master tty is given to
>>> pty_unix98_shutdown.
>>
Am Dienstag, 15. Dezember 2015, 17:34:00 schrieb Arnd Bergmann:
> On Tuesday 15 December 2015 17:31:22 Thierry Reding wrote:
> > On Mon, Dec 14, 2015 at 12:39:44PM +0100, Arnd Bergmann wrote:
> > > On Wednesday 18 November 2015 17:56:22 Andy Yan wrote:
> > > > rockchip platform have a protocol to p
On Tue, Dec 15, 2015 at 05:38:34PM +0100, Michael Wang wrote:
> The hop_limit is only suggest that the package allowed to be
> routed, not have to, correct?
If the hop limit is >= 2 (?) then the GRH is mandatory. The
SM will return this information in the PathRecord if it determines a
GRH is requi
Hi,
This patch series adds generic cpufreq-dt driver support for
Exynos542x/5800 (using the new CPU clock type which allows it).
It has been tested on Exynos5422 based ODROID-XU3 Lite board.
Depends on:
- next-20151211 branch of linux-next kernel tree
- "[PATCH] ARM: dts: Make CPU configuration
With introduction of packetized pipes, splice wasn't updated to respect this
new behaviour.
In terms of splice it means, that it never set PIPE_BUF_FLAG_PACKET on
created pipe buffer regarless pipe operating mode, thus breaking the whole
logic.
To fix this, new SPLICE_F_PACKET flag was introduced.
Hi Linus,
The following changes since commit 31ade3b83e1821da5fbb2f11b5b3d4ab2ec39db8:
Linux 4.4-rc3 (2015-11-29 18:58:26 -0800)
are available in the git repository at:
git://git.infradead.org/users/vkoul/slave-dma.git tags/dmaengine-fix-4.4-rc6
for you to fetch changes up to aa876cd4b41b4
Hi Herton,
On 12/14/2015 07:29 PM, Herton R. Krzesinski wrote:
> pty_unix98_shutdown allows a potential use after free of inode from
> slave tty->driver_data: if final pty close is called with slave
> tty_struct, and inode was released already by devpts_pty_kill at
> pty_close, pty_unix98_shutdown
This flag is used by kernel only to represent pipe packetized mode for splice
engine.
Signed-off-by: Stanislav Kinsburskiy
---
include/linux/splice.h |5 +
1 file changed, 5 insertions(+)
diff --git a/include/linux/splice.h b/include/linux/splice.h
index da2751d..13ca14d 100644
--- a/in
With introduction of packetized pipe mode, represented by O_DIRECT flag,
splice stopped working correctly with a pipe in this mode.
To be able to fix them, this helper have to exposed.
Signed-off-by: Stanislav Kinsburskiy
---
fs/pipe.c |2 +-
include/linux/pipe_fs_i.h |2
stm_is_locked_sr() takes the status register (SR) value as the last
parameter, not the second.
Reported-by: Bayi Cheng
Signed-off-by: Brian Norris
Cc: Bayi Cheng
---
drivers/mtd/spi-nor/spi-nor.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/mtd/spi-nor/spi-no
On Tue, Dec 15, 2015 at 05:17:13PM +, Mark Brown wrote:
> On Tue, Dec 15, 2015 at 03:32:19PM +, Mark Rutland wrote:
> > On Tue, Dec 15, 2015 at 03:08:13PM +, Mark Brown wrote:
> > > On Tue, Dec 15, 2015 at 02:01:36PM +, Mark Rutland wrote:
>
> > > > I really don't want to see a tab
The new CPU clock type allows the use of cpufreq-dt driver
for Exynos5420.
Cc: Tomasz Figa
Cc: Kukjin Kim
Cc: Javier Martinez Canillas
Cc: Thomas Abraham
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: Bartlomiej Zolnierkiewicz
---
arch/arm/mach-exynos/exynos.c | 3 +++
1 file changed, 3 in
msg_iocb needs to be initialized on the recv/recvfrom path.
Otherwise afalg will wrongly interpret it as an async call.
Cc: sta...@vger.kernel.org
Reported-by: Harald Freudenberger
Signed-off-by: Tadeusz Struk
---
net/socket.c |1 +
1 file changed, 1 insertion(+)
diff --git a/net/socket.c
> I think there should _not_ be a hardened rule.
I guess that it can become hard to achieve consensus on a precise rule.
> Style is just a guide.
Generally nice …
> Do what you think appropriate.
I'm sorry for my evolving understanding. - But I imagine that your feedback
can cause further
Fix CPU operating points for Exynos5800 (it use different
voltages than Exynos5420 and supports additional frequencies).
However don't use 2000MHz & 1900MHz OPPs (for A15 cores) and
1400MHz OPP (for A7 cores) for now as they are not available
on all boards.
Based on Hardkernel's kernel for ODROID-
On Tue, Dec 15, 2015 at 05:34:00PM +0100, Arnd Bergmann wrote:
> On Tuesday 15 December 2015 17:31:22 Thierry Reding wrote:
> > On Mon, Dec 14, 2015 at 12:39:44PM +0100, Arnd Bergmann wrote:
> > > On Wednesday 18 November 2015 17:56:22 Andy Yan wrote:
> > > > rockchip platform have a protocol to pa
On Tue, Dec 15, 2015 at 05:10:39PM +, Simmons, James A. wrote:
>I have been pondering if pushing bug fixes before style cleanups
> is the right thing to do.
Generally push the least controversial patches first so that if you
have to redo one patch, then the rest are already applied and don't n
On Tue, 15 Dec 2015 11:26:41 +0800
"Zhang, Yanmin" wrote:
> > This seems very hackish, although I can't think of a better way at the
> > moment. But I would like not to add more code into module.c if
> > possible, and just use a notifier unless there's a real reason we can't
> > (as there was whe
On Tue, Dec 15, 2015 at 09:28:28AM -0800, Peter Hurley wrote:
> On 12/15/2015 08:36 AM, Herton R. Krzesinski wrote:
> > On Tue, Dec 15, 2015 at 08:17:56AM -0800, Peter Hurley wrote:
> >>> I also expect in a rare case where all ptmx references are gone/closed,
> >>> this also
> >>> could happen on
On Tue, Dec 15, 2015 at 5:11 AM, Borislav Petkov wrote:
> On Thu, Dec 10, 2015 at 04:21:50PM -0800, Tony Luck wrote:
>> Using __copy_user_nocache() as inspiration create a memory copy
>> routine for use by kernel code with annotations to allow for
>> recovery from machine checks.
>>
>> Notes:
>> 1
On Tue 2015-12-15 08:28:12, H. Peter Anvin wrote:
> On 12/15/15 06:08, Pavel Machek wrote:
> >
> > But it still says:
> >
> > address sizes : 32 bits physical, 32 bits virtual
> >
> > I thought pae would be 36bit virtual?
> >
>
> It should be unless the CPU reports otherwise, which your
On Tue, Dec 15, 2015 at 05:28:37PM +, Mark Rutland wrote:
> On Tue, Dec 15, 2015 at 05:17:13PM +, Mark Brown wrote:
> > Obviously people are going to get upset if we introduce performance
> > regressions - but that's true always, we can also introduce problems
> > with numbers people have
Signed-off-by: Sergei Ianovich
CC: Alexandre Belloni
---
v4..v5
* drop THIS_MODULE from struct platform driver
* use "dallas" for vendor name per vendor-prefixes.txt
v3..v4
* move DTS bindings to a different patch
v2..v3
* use usleep_range instead of custom nsleep
* numb
The new CPU clock type allows the use of generic cpufreq-dt driver
for Exynos5422/5800.
Cc: Tomasz Figa
Cc: Kukjin Kim
Cc: Javier Martinez Canillas
Cc: Thomas Abraham
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: Bartlomiej Zolnierkiewicz
---
arch/arm/mach-exynos/exynos.c | 1 +
1 file ch
The return type of hvt_op_poll() is unsigned int and -EBADF is
inappropriate, poll functions return POLL* statuses.
Reported-by: Dexuan Cui
Signed-off-by: Vitaly Kuznetsov
---
- This is a follow-up to the previously sent 'Drivers: hv: utils: introduce
HVUTIL_TRANSPORT_DESTROY mode' patch which
From: Thomas Abraham
With the addition of the new Samsung specific cpu-clock type, the
arm clock can be represented as a cpu-clock type. Add the CPU clock
configuration data and instantiate the CPU clock type for Exynos5420.
Changes by Bartlomiej:
- split Exynos5420 support from the original pat
On Tue, 2015-12-15 at 19:06 +0100, Robert Jarzmik wrote:
>
> > > Maybe we can have a pxa_defconfig file that enables lots of boards
> > > and then we remove the individual configs? We don't have to remove
> > > them all at once, but it would make me very happy if we could at
> > > least kill off s
Fix cpu clock configuration data for Exynos5422/5800 SoCs
(they use higher PCLK_DBG divider values than Exynos5420 and
support additional frequencies).
Based on Hardkernel's kernel for ODROID-XU3 board.
Cc: Tomasz Figa
Cc: Mike Turquette
Cc: Javier Martinez Canillas
Cc: Thomas Abraham
Acked-b
On Tue, Dec 15, 2015 at 02:24:56PM +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 12/15/2015 2:44 AM, Greg KH wrote:
>
> >>Maxim Integrated MAX3355E chip integrates a charge pump and
> >>comparators
> >>to
> >>enable a system with an integrated USB OTG dual-role transceiver to
>
On Tue, Dec 15, 2015 at 8:59 AM, Toshi Kani wrote:
> ACPI 6.0 defines NFIT table and new persistent memory types for
> EFI memory table (EFI_PERSISTENT_MEMORY) and e820 table (E820_PMEM).
>
> setup_e820() enabled by EFI_STUB converts EFI_PERSISTENT_MEMORY to
> E820_PMEM for the e820_map table on x
On Tue, Dec 15, 2015 at 1:40 AM, Pavel Machek wrote:
>
> I tried applying:
>
> [PATCH 1/2] x86_32/mm: Set NX in __supported_pte_mask before enabling
> paging
>
> but I still get
>
> [2.691897] x86/mm: Found insecure W+X mapping at address
> ffe69000/0xffe69000
This may be an insane suggestio
On Tue, Dec 15, 2015 at 11:48:24AM +0100, Geert Uytterhoeven wrote:
> Hi Vinod,
>
> On Fri, Jul 10, 2015 at 10:14 AM, Vinod Koul wrote:
> > On Wed, Jul 08, 2015 at 12:12:52PM +0200, Geert Uytterhoeven wrote:
> >> On Fri, Apr 26, 2013 at 11:06 AM, Linus Walleij
> >> wrote:
> >> > The documentatio
On Tue, 2015-12-15 at 18:02 +0100, Arnd Bergmann wrote:
> On Tuesday 15 December 2015 19:42:07 Sergei Ianovich wrote:
> > There are several board-specific devices on LP8x4x: custom FPGA,
> > custom
> > UART, custom IRQ on FPGA, custom parallel bus for industrial IO. The
> > defconfig file could ale
On Tue, Dec 15, 2015 at 5:50 AM, Frank Binns wrote:
> Is this not the issue fixed by 8e43c9c75?
No because if we start teardown without waiting for the fence to be
signaled it will still be on the active_list.
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux
On Tue, Dec 15, 2015 at 5:30 AM, Gustavo Padovan wrote:
> 2015-12-14 Dmitry Torokhov :
>
>> Userspace can close the sync device while there are still active fence
>> points, in which case kernel produces the following warning:
>>
>> [ 43.853176] [ cut here ]
>> [ 43.857
On 15 December 2015 at 18:15, Mark Rutland wrote:
> On Tue, Dec 15, 2015 at 05:59:34PM +0100, Vincent Guittot wrote:
>> On 15 December 2015 at 17:41, Mark Rutland wrote:
>> > On Tue, Dec 15, 2015 at 04:23:18PM +, Catalin Marinas wrote:
>> >> On Tue, Dec 15, 2015 at 03:57:37PM +, Mark Rutl
On Tue, 2015-12-15 at 09:53 -0800, Dan Williams wrote:
> On Tue, Dec 15, 2015 at 9:49 AM, Toshi Kani wrote:
> > On Tue, 2015-12-15 at 09:21 -0800, Dan Williams wrote:
> > > On Tue, Dec 15, 2015 at 8:59 AM, Toshi Kani
> > > wrote:
> > > > ACPI 6.0 defines NFIT table and new persistent memory types
On Mon 14-12-15 22:42:58, Vladimir Davydov wrote:
> On Mon, Dec 14, 2015 at 04:30:37PM +0100, Michal Hocko wrote:
> > On Thu 10-12-15 14:39:14, Vladimir Davydov wrote:
> > > In the legacy hierarchy we charge memsw, which is dubious, because:
> > >
> > > - memsw.limit must be >= memory.limit, so i
>> ... and the non-temporal version is the optimal one even though we're
>> defaulting to copy_user_enhanced_fast_string for memcpy on modern Intel
>> CPUs...?
My current generation cpu has a bit of an issue with recovering from a
machine check in a "rep mov" ... so I'm working with a version of m
On Tue, Dec 15, 2015 at 07:02:31AM -0800, Joe Perches wrote:
> This is the original code:
>
> result = foo();
> if (result)
> goto label;
>
> result = bar();
> if (result)
> goto label;
>
> result = baz();
> if (result)
>
On Tue, 2015-12-15 at 09:21 -0800, Dan Williams wrote:
> On Tue, Dec 15, 2015 at 8:59 AM, Toshi Kani wrote:
> > ACPI 6.0 defines NFIT table and new persistent memory types for
> > EFI memory table (EFI_PERSISTENT_MEMORY) and e820 table (E820_PMEM).
> >
> > setup_e820() enabled by EFI_STUB convert
On Tue, Dec 15, 2015 at 9:49 AM, Toshi Kani wrote:
> On Tue, 2015-12-15 at 09:21 -0800, Dan Williams wrote:
>> On Tue, Dec 15, 2015 at 8:59 AM, Toshi Kani wrote:
>> > ACPI 6.0 defines NFIT table and new persistent memory types for
>> > EFI memory table (EFI_PERSISTENT_MEMORY) and e820 table (E820
Linus Walleij writes:
> On Sat, Dec 12, 2015 at 11:55 PM, Robert Jarzmik
> wrote:
>
>> The interrupt management is changed by this patch to rely on chip data
>> instead of chained interrupts.
>>
>> The main goal is to loosen the dependency on the global pxa chip
>> structure in favor of the pas
On Tue, 2015-12-15 at 19:49 +0100, SF Markus Elfring wrote:
> > I think there should _not_ be a hardened rule.
> I guess that it can become hard to achieve consensus on a precise rule.
Consensus isn't unanimity.
> I imagine that your feedback
> can cause further software development troubles if t
This provides an MTD device driver for 512kB of battery backed up SRAM
on ICPDAS LP-8X4X programmable automation controllers.
SRAM chip is connected via FPGA and is not accessible without a driver,
unlike flash memory which is wired to CPU MMU.
This SRAM becomes an excellent persisent storage of
701 - 800 of 939 matches
Mail list logo
