Start qemu with the following arguments:
-m 64G,slots=2,maxmem=66G -object memory-backend-ram,id=mem1,size=2G
Which: boots machine with 64G, and adds a device mem1 with 2G which can be
hotplugged later.
Also make sure that config has the following turned on:
CONFIG_MEMORY_HOTPLUG
Changelog:
v2 - v3
Fixed two issues found during testing
Addressed Kbuild warning reports
v1 - v2
Added struct page poisoning checking in order to verify that
struct pages are never accessed until initialized during memory
hotplug
This
Darlehen Angebot bei 3%, zögern Sie nicht, uns für weitere Informationen zu
kontaktieren
In case of SMP we use GFRC from ARconnect and Timer1 is left
untouched. Still with that check in place we're panicing if Timer1
is missing in current hardware which is quite unexpected.
Signed-off-by: Alexey Brodkin
---
arch/arc/kernel/setup.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On 9 February 2018 at 16:03, James Morse wrote:
> Hi Akashi, Ard,
>
> On 02/02/18 04:35, AKASHI Takahiro wrote:
>> On Thu, Feb 01, 2018 at 05:34:26PM +, Ard Biesheuvel wrote:
>>> On 1 February 2018 at 09:04, AKASHI Takahiro
>>> wrote:
* Initial ACPI tables are normally stored in system
On Tue, Feb 13, 2018 at 02:17:22PM -0500, Mario Leinweber wrote:
> if (flags & FOLL_SPLIT && PageTransCompound(page)) {
> int ret;
> +
> get_page(page);
Hi Mario,
Thanks for your patch, but this kind of change to the Linux core is not
generally welcomed. There
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
head: 0fc8483b698620ea3d8cc6635b54eccc613c23a3
commit: 0fc8483b698620ea3d8cc6635b54eccc613c23a3 [14/14] x86/io: Define
readq()/writeq() to use 64-bit type
reproduce:
# apt-get install sparse
git
On Tue, Feb 13, 2018 at 08:16:57AM +0100, Rasmus Villemoes wrote:
> On 13 February 2018 at 07:20, Shunyong Yang
> wrote:
>
> >
> > This patch replaces space with readable "=" when output needs padding.
> > Following is the output after applying the patch,
>
> > Suggested-by: Rasmus Villemoes
>
On 02/12/2018 02:34 PM, Guenter Roeck wrote:
> Commit e67e02a544e9 ("powerpc/pseries: Fix cpu hotplug crash with
> memoryless nodes") adds an unconditional call to find_and_online_cpu_nid(),
> which is only declared if CONFIG_PPC_SPLPAR is enabled. This results in
> the following build error if
[Resending after delivery failure]
Hi Dave,
On 02/13/2018 10:22 AM, Dave Watson wrote:
>
> Yes, these both sound reasonable. I will send a V2.
>
> Thanks!
Another minor suggestion for v2:
It might be a good idea to check if the first assoclen bytes are already
contiguous and only do the
On Tue, Feb 13, 2018 at 8:12 PM, Brendan Higgins
wrote:
> On Tue, Feb 13, 2018 at 1:29 AM, Avi Fishman wrote:
>> On Tue, Feb 13, 2018 at 10:30 AM, Arnd Bergmann wrote:
>>> On Tue, Feb 6, 2018 at 12:57 AM, Brendan Higgins
>>> wrote:
Add a common device tree for all Nuvoton NPCM750 BMCs and
On 02/13/2018 11:35 AM, Alexey Brodkin wrote:
In case of SMP we use GFRC from ARconnect and Timer1 is left
untouched. Still with that check in place we're panicing if Timer1
is missing in current hardware which is quite unexpected.
Signed-off-by: Alexey Brodkin
---
arch/arc/kernel/setup.c |
From: Sukadev Bhattiprolu
Date: Fri, 9 Feb 2018 11:49:06 -0600
Subject: [PATCH 1/1] powerpc/vas: Fix cleanup when VAS is not configured
When VAS is not configured, unregister the platform driver. Also simplify
cleanup by delaying vas debugfs init until we know VAS is configured.
Signed-off-by:
Den 2/11/2018 23:32, skrev Ywe Cærlyn:
Ii is an unique time to do something good, with available source, and
dethrone Microsoft, its dodgy background, and lack of decent thread
prioritation Unix had already in the 70s.
People should move to the BSD 3-clause licence though. Research shows
On Wed, 2018-02-14 at 03:41 +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> x86/urgent
> head: 0fc8483b698620ea3d8cc6635b54eccc613c23a3
> commit: 0fc8483b698620ea3d8cc6635b54eccc613c23a3 [14/14] x86/io:
> Define readq()/writeq() to use
On 02/13/2018 02:09 AM, Michael Ellerman wrote:
> Randy Dunlap writes:
>
>> On 02/12/2018 04:28 AM, Michael Ellerman wrote:
>>> Randy Dunlap writes:
>>>
From: Randy Dunlap
Currently #includes for no obvious
reason. It looks like it's only a convenience, so remove
This is 4.16-rc1+todays git ona lowly P4 with NV5, worked fine in 4.15:
[7.361155] nouveau :01:00.0: NVIDIA NV05 (20154000)
[7.386601] nouveau :01:00.0: bios: version 02.05.19.03.00
[7.386715] nouveau :01:00.0: bios: DCB table not found
[7.386983] nouveau :01:00.0:
Addressed comments from:
- Joel: https://www.spinics.net/lists/arm-kernel/msg634074.html
- Arnd: https://www.spinics.net/lists/arm-kernel/msg634091.html
Summary of changes since previous update:
- Replaced "nuvoton,npcm7xx-smp" compatibility string with
"nuvoton,npcm750-smp".
- Fixed some
Add a common device tree for all Nuvoton NPCM750 BMCs and a board
specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by: Brendan Higgins
Reviewed-by: Tomer Maimon
Reviewed-by: Avi Fishman
Reviewed-by: Joel Stanley
Reviewed-by: Rob Herring
Tested-by: Tomer Maimon
Adds basic support for the Nuvoton NPCM750 BMC.
Signed-off-by: Brendan Higgins
Reviewed-by: Tomer Maimon
Reviewed-by: Avi Fishman
Tested-by: Tomer Maimon
Tested-by: Avi Fishman
---
arch/arm/Kconfig | 2 ++
arch/arm/Makefile| 1 +
arch/arm/mach-npcm/Kconfig | 48
Add maintainers and reviewers for the Nuvoton NPCM architecture.
Signed-off-by: Brendan Higgins
Reviewed-by: Tomer Maimon
Reviewed-by: Avi Fishman
---
MAINTAINERS | 14 ++
1 file changed, 14 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 44cb004c765d..2fa95aba0f7f
Fixes: 525e7273bc80 ("orangefs: let setattr write to cached inode")
Signed-off-by: Fengguang Wu
---
super.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/orangefs/super.c b/fs/orangefs/super.c
index 49bb1ce..c38310c 100644
--- a/fs/orangefs/super.c
+++
tree: https://github.com/martinbrandenburg/linux for-next
head: 525e7273bc80995f5bcfdc2780b870aa3ab37a18
commit: 525e7273bc80995f5bcfdc2780b870aa3ab37a18 [13/13] orangefs: let setattr
write to cached inode
reproduce:
# apt-get install sparse
git checkout
On Sat, Dec 30, 2017 at 8:41 PM, santosh.shilim...@oracle.com
wrote:
> On 12/30/17 1:17 AM, syzbot wrote:
>>
>> Hello,
>>
>> syzkaller hit the following crash on
>> fba961ab29e5ffb055592442808bb0f7962e05da
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
>> compiler: gcc
Change the first input parameter in mlxreg_hotplug_device_create to the
pointer to mlxreg_hotplug private data in order to allow to use the fields
from the private data structure inside this routine.
Signed-off-by: Vadim Pasternak
---
drivers/platform/mellanox/mlxreg-hotplug.c | 12 ++--
This patchset:
- Adds define for the channels number for mux device.
- Adds differed bus functionality.
- Changes input for device create routine in mlxreg-hotplug driver.
- Adds physical bus number auto detection.
Vadim Pasternak (4):
platform/x86: mlx-platform: Use define for the channel
Add define for the channels number for mux device, instead of using
hardcoded value inside the code in order to improve code readability.
Signed-off-by: Vadim Pasternak
---
drivers/platform/x86/mlx-platform.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
Add deferred bus functionality in order to enforce probing flow execution
order. Driver mlx-platform activates platform driver i2c-mux-reg, which
creates busses infrastructure, after that it activates mlxreg-hotplug
driver, which uses these busses, for connecting devices. The possible
Add physical bus number auto detection mechanism in order to avoid a
possible collision with I2C physical bus allocation. The mlx-platform
driver activates i2c-mlxcpld driver with no bus number specification. It
based on an assumption that on all Mellanox systems physical bus number is
supposed to
On Sat, Feb 10, 2018 at 8:06 PM, Alexey Skidanov
wrote:
> Currently, sg_page_count() may be used only inside the scatterlist.c file.
>
> However, the same calculation is done outside of scatterlist.c file
> causing to code duplication.
>
> To fix this, we move the sg_page_count() to the
On Thu, Jan 4, 2018 at 8:36 PM, Tom Herbert wrote:
> On Thu, Jan 4, 2018 at 4:10 AM, syzbot
> wrote:
>> Hello,
>>
>> syzkaller hit the following crash on
>> 6bb8824732f69de0f233ae6b1a8158e149627b38
>> git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/master
>> compiler: gcc (GCC)
If a signal-callback (lwi_on_signal) is set without lwi_allow_intr, as
is the case in ldlm_completion_ast(), the behavior depends on the
timeout set.
If a timeout is set, then signals are ignored. If the timeout is
reached, the timeout handler is called. If the timeout handler
return 0, which
On 02/13/2018 12:09 PM, Brendan Higgins wrote:
> Addressed comments from:
> - Joel: https://www.spinics.net/lists/arm-kernel/msg634074.html
> - Arnd: https://www.spinics.net/lists/arm-kernel/msg634091.html
>
> Summary of changes since previous update:
> - Replaced "nuvoton,npcm7xx-smp"
Davidlohr Bueso writes:
> Hi,
>
> The following patches adds the discussed[1] new command for shm
> as well as for sems and msq as they are subject to the same discrepancies
> for ipc object permission checks between the syscall and via procfs.
> These new commands are justified in that (1) we
From: Markus Elfring
Date: Tue, 13 Feb 2018 21:16:42 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation in two functions
Improve a size determination in
From: Markus Elfring
Date: Tue, 13 Feb 2018 20:42:40 +0100
Omit an extra message for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/dma/ppc4xx/adma.c | 2 --
1 file changed, 2 deletions(-)
From: Markus Elfring
Date: Tue, 13 Feb 2018 20:54:30 +0100
Replace the specification of a data structure by a pointer dereference
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was
On 14/12/2017 at 13:31:43 +0800, Baolin Wang wrote:
> It will be more helpful to add some tracepoints to track RTC actions when
> debugging RTC driver. Below sample is that we set/read the RTC time, then
> set 2 alarms, so we can see the trace logs:
>
> set/read RTC time:
> kworker/0:1-67 [000]
On 26/01/2018 at 13:06:01 +0800, Baolin Wang wrote:
> If we convert one large time values to rtc_time, in the original formula
> 'days * 86400' can be overflowed in 'unsigned int' type to make the formula
> get one incorrect remain seconds value. Thus we can use div_s64_rem()
> function to avoid
This is the third installment of a patchset that attempt to fix a problem
reported by Steve Rostedt [1] where DL bandwidth accounting is not
recomputed after CPUset and CPU hotplug operations took place. When CPU
hotplug and some CUPset manipulation take place root domains are destroyed
and new
Introducing function partition_sched_domains_locked() by taking
the mutex locking code out of the original function. That way
the work done by partition_sched_domains_locked() can be reused
without dropping the mutex lock.
No change of functionality is introduced by this patch.
Signed-off-by:
Care must be taken when CPUs are added to a new CPUset. If an ancestor
of that set has its sched_load_balance flag switch off then the CPUs in
the new CPUset will be added to a new root domain. If the ancestor also
had DL tasks those will end up covering more than one root domain,
breaking at
When a DL task is assigned a CPU the "utilisation" (this_bw) and the
"active utilisation" (running_bw) fields of rq->dl are incremented
accordingly. If the CPU is hotplugged out the DL task is transferred
to another CPU but the task's contribution to this_bw and running_bw
isn't substracted from
When considering to move a task to the DL policy we need to make sure
the CPUs it is allowed to run on matches the CPUs of the root domain of
the runqueue it is currently assigned to. Otherwise the task will be
allowed to roam on CPUs outside of this root domain, something that will
skew system
Now that we mandate that on creation, the ->cpus_allowed mask of a future
DL task has to be equal to the rd->span of the root domain it will be
associated with, changing the affinity of a DL task doesn't make sense
anymore.
Indeed, if we set the task to a smaller affinity set then we may be
When the topology of root domains is modified by CPUset or CPUhotplug
operations information about the current deadline bandwidth held in the
root domain is lost.
This patch address the issue by recalculating the lost deadline
bandwidth information by circling through the deadline tasks held in
This patch prevents the 'sched_load_balance' flag from being set to 0
when DL tasks are present in a CPUset. Otherwise we end up with the
DL tasks using CPUs belonging to different root domains, something that
breaks the mathematical model behind DL bandwidth management.
For example on a 4 core
Calls to task_rq_unlock() are done several times in function
__sched_setscheduler(). This is fine when only the rq lock needs to be
handled but not so much when other locks come into play.
This patch streamline the release of the rq lock so that only one location
need to be modified when dealing
The comment above function partition_sched_domains() clearly state that
the cpu_hotplug_lock should be held but doesn't mandate one to abide to
it. Adding an explicit check backs that comment and make it impossible
for anyone to miss the requirement.
Suggested-by: Juri Lelli
Signed-off-by:
No synchronisation mechanism exist between the cpuset subsystem and calls
to function __sched_setscheduler(). As such it is possible that new root
domains are created on the cpuset side while a deadline acceptance test
is carried out in __sched_setscheduler(), leading to a potential oversell
of
On Tue, 2018-02-13 at 21:25 +0100, SF Markus Elfring wrote:
> Omit an extra message for a memory allocation failure in these functions.
[]
> diff --git a/drivers/dma/ppc4xx/adma.c b/drivers/dma/ppc4xx/adma.c
[]
> @@ -4183,7 +4183,6 @@ static int ppc440spe_adma_probe(struct platform_device
>
We were printing the entire 32 bit register rather than just the lower
8 bits. Anything above bit 7 is reserved and may be any random value.
Fixes: 2f330caff577 ("memory: brcmstb: Add driver for DPFE")
Signed-off-by: Markus Mayer
---
drivers/memory/brcmstb_dpfe.c | 3 ++-
1 file changed, 2
This series primarily introduces a new way of passing information from
the DCPU to the host CPU.
Previously, all communication was via the DCPU data RAM. This
communication mode is still supported. In addition, we now support
passing data via the message RAM. The driver will dynamically detect
In some functions, variable "ret" should be ssize_t, so we fix it.
Fixes: 2f330caff577 ("memory: brcmstb: Add driver for DPFE")
Signed-off-by: Markus Mayer
---
drivers/memory/brcmstb_dpfe.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/memory/brcmstb_dpfe.c
The DCPU can now send message data in two ways:
- via the data RAM, as before (this is now message type 0)
- via the message RAM (this is message type 1)
In order to support both methods, we check the message type of the
response (bits 31:28) and then treat the offset (bits 27:0)
accordingly.
On 02/13/2018 10:14 PM, Andy Shevchenko wrote:
> On Sat, Feb 10, 2018 at 8:06 PM, Alexey Skidanov
> wrote:
>> Currently, sg_page_count() may be used only inside the scatterlist.c file.
>>
>> However, the same calculation is done outside of scatterlist.c file
>> causing to code duplication.
>>
On 16/01/2018 at 14:45:21 +, James Hogan wrote:
> Fix the following warning in MIPS allmodconfig by adding a
> MODULE_LICENSE() at the end of rtc-goldfish.c, based on the file header
> comment which says GNU General Public License version 2:
>
> WARNING: modpost: missing MODULE_LICENSE() in
On Tue, Feb 13, 2018 at 11:22 AM, Ross Zwisler
wrote:
> On Tue, Feb 13, 2018 at 03:54:04PM +0100, Christoph Hellwig wrote:
>> Looks good:
>>
>> Reviewed-by: Christoph Hellwig
>>
>> Can you wire up your test cases for blktests?
>
> Is blktests really the right place for this test? This failure
> From: netdev-ow...@vger.kernel.org [mailto:netdev-
> ow...@vger.kernel.org] On Behalf Of Christophe JAILLET
> Sent: Tuesday, February 6, 2018 11:48 AM
> To: Kirsher, Jeffrey T
> Cc: intel-wired-...@lists.osuosl.org; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org;
From: Markus Elfring
Date: Tue, 13 Feb 2018 21:48:26 +0100
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/dma/at_xdmac.c | 4 +---
1 file changed, 1 insertion(+), 3
On Mon 2018-02-05 22:29:41, Hans Verkuil wrote:
> On 02/05/2018 09:36 PM, Gustavo A. R. Silva wrote:
> > Add suffix ULL to constant 10 in order to give the compiler complete
> > information about the proper arithmetic to use. Notice that this
> > constant is used in a context that expects an
On Thu 2018-02-08 20:52:40, Alan Cox wrote:
> > > Also worth nothing that the difference between the cpu and memory
> > > speeds is much lower - so far fewer instructions could be speculatively
> > > executed while waiting a cache miss.
>
> But they also have more instructions that take a lot of
Hi!
> > You might think this absolutely crazy, but I would be willing to test
> > such systems if I can get my hands on the needed hardware that I lack.
> > I am already doing sanity testing on Intel
> > i486/i586/i586-MMX/i686-PentiumPro systems, I just don't have the
> > clone cpus (Cyrix,
On 02/08/2018 06:36 PM, Andrew Morton wrote:
On Wed, 31 Jan 2018 18:04:00 -0500 daniel.m.jor...@oracle.com wrote:
lru_lock, a per-node* spinlock that protects an LRU list, is one of the
hottest locks in the kernel. On some workloads on large machines, it
shows up at the top of lock_stat.
Do
On Sun, Feb 4, 2018 at 2:49 AM, Tycho Andersen wrote:
> This patch introduces a means for syscalls matched in seccomp to notify
> some other task that a particular filter has been triggered.
>
> The motivation for this is primarily for use with containers. For example,
> if a container does an
On Mon, Feb 12, 2018 at 10:30 PM, Amir Goldstein wrote:
> On Thu, Jan 25, 2018 at 10:36 PM, Amir Goldstein wrote:
>> On Thu, Jan 25, 2018 at 10:20 PM, Shakeel Butt wrote:
>>> On Wed, Jan 24, 2018 at 11:51 PM, Amir Goldstein wrote:
There is a nicer alternative, instead of failing the
On Sun, 04 Feb 2018 18:14:24 +0800
Xiongwei Song wrote:
> There is no file named 'enabled' in the directory tracing/events. It should
> be the file 'enable'.
Makes sense, applied to the docs tree, thanks.
jon
From: Markus Elfring
Date: Tue, 13 Feb 2018 22:10:42 +0100
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/devfreq/event/exynos-ppmu.c | 6 ++
1 file changed, 2
On 02/06/2018 03:20 PM, Daniel Díaz wrote:
> From: Anders Roxell
>
> The memfd test requires to insert the fuse module (CONFIG_FUSE_FS).
>
> Signed-off-by: Anders Roxell
> Signed-off-by: Daniel Díaz
> ---
> tools/testing/selftests/memfd/config | 1 +
> 1 file changed, 1 insertion(+)
>
On 02/06/2018 03:22 PM, Daniel Díaz wrote:
> From: Anders Roxell
>
> While testing memfd tests, there is a missing script, as reported by
> kselftest:
>
> ./run_tests.sh: line 7: ./run_fuse_test.sh: No such file or directory
>
> Signed-off-by: Anders Roxell
> Signed-off-by: Daniel Díaz
> ---
On 02/06/2018 03:23 PM, Daniel Díaz wrote:
> From: Anders Roxell
>
> Based on patch: https://patchwork.kernel.org/patch/10042045/
>
> arch64-linux-gnu-gcc -c sync.c -o sync/sync.o
> sync.c:42:29: fatal error: linux/sync_file.h: No such file or directory
> #include
>
On 02/06/2018 04:52 PM, Daniel Díaz wrote:
> The Makefile lacks a couple of line continuation backslashes
> in an `if' clause, which can make the subsequent rsync
> command go awry over the whole filesystem (`rsync -a / /`).
>
> /bin/sh: -c: line 5: syntax error: unexpected end of file
>
On 02/07/2018 10:24 AM, Daniel Díaz wrote:
> The Makefile lacks a couple of line continuation backslashes
> in an `if' clause, which produces an error while make'ing:
>
> $ make
> make[1]: Entering directory `/[...]/linux/tools/testing/selftests/futex'
> /bin/sh: -c: line 5: syntax error:
On Tue, Feb 13, 2018 at 2:32 AM, Michal Hocko wrote:
> On Tue 13-02-18 21:16:55, Michael Ellerman wrote:
>> Kees Cook writes:
>>
>> > On Mon, Feb 12, 2018 at 7:25 PM, Michael Ellerman
>> > wrote:
>> >> Michal Hocko writes:
>> >>> Hi,
>> >>> my build test machinery chokes on samples/seccomp
On 02/08/2018 12:51 AM, Kirill A. Shutemov wrote:
> On Wed, Feb 07, 2018 at 11:50:28PM -0600, Daniel Díaz wrote:
>> The 5lvl.c test file was incorporated into another one in
>> selftests/vm (va_128TBswitch.c) in commit 235266b8.
>>
>> Signed-off-by: Daniel Díaz
>
> Acked-by: Kirill A. Shutemov
On Sun, Feb 4, 2018 at 2:49 AM, Tycho Andersen wrote:
> Hoist out the nth filter resolving logic that ptrace uses into a new
> function. We'll use this in the next patch to implement the new
> PTRACE_SECCOMP_GET_FILTER_FLAGS command. This is based on an older patch
> that I had sent a while ago;
On 02/11/2018 03:59 AM, Dominik Brodowski wrote:
> The vDSO selftests ignored the O= or KBUILD_OUTPUT= parameters. Fix it.
>
> Signed-off-by: Dominik Brodowski
> ---
> tools/testing/selftests/vDSO/Makefile | 14 +++---
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git
On Sun, Feb 4, 2018 at 2:49 AM, Tycho Andersen wrote:
> As an alternative to SECCOMP_FILTER_FLAG_GET_LISTENER, perhaps a ptrace()
> version which can acquire filters is useful. There are at least two reasons
> this is preferable, even though it uses ptrace:
>
> 1. You can control tasks that
Thanks for the review. Comments inline.
On Mon, Feb 12, 2018 at 10:06:21AM +0100, Marcus Folkesson wrote:
> Hi Jerry,
>
> On Sun, Feb 11, 2018 at 10:21:06PM -0700, Jerry Hoemann wrote:
> > Follow Documentation/watchdog/convert_drivers_to_kernel_api.txt to
> > convert hpwdt from legacy watchdog
On Tue, Feb 13, 2018 at 8:57 AM, tedheadster wrote:
> Changing X86_32_LAZY_GS to 'y' does not cause the kernel to hang.
>
>> On Tue, Feb 13, 2018 at 11:40:17AM -0500, tedheadster wrote:
>>> in your patch "x86: make lazy %gs optional on x86_32" were you able
>>> to test it on really old
Hi Joerg,
On Tue, Feb 13, 2018 at 03:03:03PM +0100, Joerg Roedel wrote:
> On Fri, Feb 02, 2018 at 04:49:56PM -0800, Sohil Mehta wrote:
> > This series aims to add debugfs support for Intel IOMMU. It exposes IOMMU
> > registers, internal context and dumps individual table entries to help debug
> >
On 02/13/2018 10:50 AM, Christoph Hellwig wrote:
> On Fri, Feb 09, 2018 at 09:52:21AM -0500, Waiman Long wrote:
>> When multiple kernel threads are created to cooperatively work on
>> a common task, we may need a convenient way to access data that are
>> specific to each kthread.
>>
>> The
On 02/13/2018 04:40 PM, Waiman Long wrote:
> On 02/13/2018 10:50 AM, Christoph Hellwig wrote:
>> On Fri, Feb 09, 2018 at 09:52:21AM -0500, Waiman Long wrote:
>>> When multiple kernel threads are created to cooperatively work on
>>> a common task, we may need a convenient way to access data that
On Tue, Feb 13, 2018 at 8:09 AM, Laura Abbott wrote:
> No, arm64 doesn't fixup the aliases, mostly because arm64 uses larger
> page sizes which can't be broken down at runtime. CONFIG_PAGE_POISONING
> does use 4K pages which could be adjusted at runtime. So yes, you are
> right we would have
Silence the following command being printed while running test.
./mem-on-off-test.sh -r 2 && echo "selftests: memory-hotplug [PASS]" ||
echo "selftests: memory-hotplug [FAIL]"
Signed-off-by: Shuah Khan
---
tools/testing/selftests/memory-hotplug/Makefile | 2 +-
1 file changed, 1 insertion(+),
Update .gitignore with new test.
Signed-off-by: Shuah Khan
---
tools/testing/selftests/vm/.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/testing/selftests/vm/.gitignore
b/tools/testing/selftests/vm/.gitignore
index 63c94d776e89..342c7bc9dc8c 100644
---
On Fri, 09 Feb 2018 05:22:52 PST (-0800), matt.redfe...@mips.com wrote:
When these are included into arch Kconfig files, maintaining
alphabetical ordering of the selects means these get split up. To allow
for keeping things tidier and alphabetical, rename the selects to
GENERIC_LIB_*
On Mon, Feb 12, 2018 at 09:05:13PM +0800, Jianchao Wang wrote:
> @@ -1315,9 +1315,6 @@ static int nvme_suspend_queue(struct nvme_queue *nvmeq)
> nvmeq->cq_vector = -1;
> spin_unlock_irq(>q_lock);
>
> - if (!nvmeq->qid && nvmeq->dev->ctrl.admin_q)
> -
On Tue, 13 Feb 2018 14:31:55 -0500 Pavel Tatashin
wrote:
> This patchset:
> - Improves hotplug performance by eliminating a number of
> struct page traverses during memory hotplug.
>
> - Fixes some issues with hotplugging, where boundaries
> were not properly checked. And on x86 block size was
On Tue, Feb 13, 2018 at 11:10 PM, Shakeel Butt wrote:
> On Mon, Feb 12, 2018 at 10:30 PM, Amir Goldstein wrote:
>> On Thu, Jan 25, 2018 at 10:36 PM, Amir Goldstein wrote:
>>> On Thu, Jan 25, 2018 at 10:20 PM, Shakeel Butt wrote:
On Wed, Jan 24, 2018 at 11:51 PM, Amir Goldstein
On Tue, Feb 13, 2018 at 02:36:48PM -0700, Jerry Hoemann wrote:
>
>
> Thanks for the review. Comments inline.
>
> On Mon, Feb 12, 2018 at 10:06:21AM +0100, Marcus Folkesson wrote:
> > Hi Jerry,
> >
> > On Sun, Feb 11, 2018 at 10:21:06PM -0700, Jerry Hoemann wrote:
> > > Follow
On Tue, Feb 13, 2018 at 09:41:35AM -0800, Guenter Roeck wrote:
> On Sun, Feb 11, 2018 at 10:21:03PM -0700, Jerry Hoemann wrote:
> > + unsigned int mynmi = hpwdt_my_nmi();
> > + static char panic_msg[] =
> > + "00: An NMI occurred. Depending on your system the reason "
> > +
On Mon, Feb 12, 2018 at 11:35 PM, Vaibhav Jain
wrote:
> Thanks for reviewing this patch Balbir
>
> Balbir Singh writes:
>
>> Any specific issue you've run into without this patch?
> Without this patch since xmon is still accessible via sysrq and there is
> no indication/warning on the xmon
Hi Kieran,
Thank you for the patch.
On Tuesday, 13 February 2018 21:30:34 EET Kieran Bingham wrote:
> From: Kieran Bingham
>
> The FCPVB handles the interface between the VSPB and memory, while the
> FCPVD handles the interface between the VSPD and memory.
>
> Signed-off-by: Kieran Bingham
Hi Kieran,
Thank you for the patch.
On Tuesday, 13 February 2018 21:30:35 EET Kieran Bingham wrote:
> From: Kieran Bingham
>
> The r8a77995 has a VSPBS to support image processing such as blending of
> two input images, and has two VSPDs to handle display pipelines with a
> DU.
>
>
Hi Kieran,
Thank you for the patch.
On Tuesday, 13 February 2018 21:30:36 EET Kieran Bingham wrote:
> From: Kieran Bingham
>
> The VSPD includes a CLUT on RPF2. Ensure that the register space is
> mapped correctly to support this.
>
> Signed-off-by: Kieran Bingham
Reviewed-by: Laurent
Hi Kieran,
Thank you for the patch.
On Tuesday, 13 February 2018 21:30:37 EET Kieran Bingham wrote:
> From: Kieran Bingham
>
> The VSPD includes a CLUT on RPF2. Ensure that the register space is
> mapped correctly to support this.
>
> Signed-off-by: Kieran Bingham
Reviewed-by: Laurent
The mailing list archives[1,2] show no activity since September 2011.
[1]: https://lists.linuxfoundation.org/pipermail/bugme-new/
[2]: https://lists.linuxfoundation.org/pipermail/bugme-janitors/
Signed-off-by: Jonathan Neuschäfer
---
Documentation/process/howto.rst | 8
1 file
Hi,
2018-02-13 10:18 GMT+01:00 Emil Renner Berthing
:
> On 12 February 2018 at 23:29, Rob Herring wrote:
>> On Mon, Feb 12, 2018 at 3:26 PM, Brian Norris
>> wrote:
>>> Hi,
>>>
>>> On Mon, Feb 12, 2018 at 10:43:41AM -0600, Rob Herring wrote:
On Thu, Feb 8, 2018 at 3:23 PM, Enric Balletbo
Hi folks,
I'm currently trying to implement plan9 semantics on Linux and
yet sorting out how to do the mount namespace handling.
On plan9, any unprivileged process can create its own namespace
and mount/bind at will, while on Linux this requires CAP_SYS_ADMIN.
What is the reason for not
901 - 1000 of 2256 matches
Mail list logo
