On Thu, 21 Jun 2018 12:03:21 +1000
David Gibson wrote:
> On Sun, Jun 17, 2018 at 09:14:28PM +1000, Alexey Kardashevskiy wrote:
> > At the moment we allocate the entire TCE table, twice (hardware part and
> > userspace translation cache). This normally works as we normally have
> > contigous memor
With SPARSEMEM config enabled, we make sure that we don't add sections beyond
MAX_PHYSMEM_BITS range. This results in not building vmemmap mapping for
range beyond max range. But our memblock layer looks the device tree and create
mapping for the full memory range. Prevent this by checking against
We do this only with VMEMMAP config so that our page_to_[nid/section] etc are
not
impacted.
Signed-off-by: Aneesh Kumar K.V
---
arch/powerpc/include/asm/sparsemem.h | 13 ++---
1 file changed, 10 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/include/asm/sparsemem.h
b/arch/po
Using 'at' as the part of the compatible string is now
deprecated. Use a correct string: 'atmel,'.
Signed-off-by: Bartosz Golaszewski
---
arch/powerpc/boot/dts/pdm360ng.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/boot/dts/pdm360ng.dts
b/arch/powerpc/boo
Using compatible strings without the part for at24 is
now deprecated. Use a correct 'atmel,' value.
Signed-off-by: Bartosz Golaszewski
---
arch/powerpc/boot/dts/fsl/kmcent2.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/boot/dts/fsl/kmcent2.dts
b/arch/powe
Using 'at24' as fallback is now deprecated - use the full
'atmel,' string.
Signed-off-by: Bartosz Golaszewski
---
arch/powerpc/boot/dts/ac14xx.dts | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/arch/powerpc/boot/dts/ac14xx.dts b/arch/powerpc/boot/dts/a
At the moment we allocate the entire TCE table, twice (hardware part and
userspace translation cache). This normally works as we normally have
contigous memory and the guest will map entire RAM for 64bit DMA.
However if we have sparse RAM (one example is a memory device), then
we will allocate TCE
Florian Weimer writes:
> On 06/19/2018 02:40 PM, Michael Ellerman wrote:
>>> I tested the whole series with the new selftests, with the printamr.c
>>> program I posted earlier, and the glibc test for pkey_alloc &c. The
>>> latter required some test fixes, but now passes as well. As far as I
>>>
Greeting's
WARN_ONCE is triggered when interface is toggled when running 'ethtool -S'
command
on a powerpc machine running today's mainline kernel
related commit looks to be:
commit 9b10df596bd4d38f2a58cf87e0780510acc53d8d
Author: Jacob Keller
Date: Thu May 17 01:08:36 2018 -0700
i40e:
Mathieu Malaterre writes:
> In commit 4aea909eeba3 ("powerpc: Add missing prototypes in setup_32.c")
I don't have that commit ^ ?
That might be because I squashed some of your fixes together or something?
> diff --git a/arch/powerpc/kernel/setup.h b/arch/powerpc/kernel/setup.h
> index 35ca3098
On Thu, Jun 21, 2018 at 6:31 PM, Aneesh Kumar K.V
wrote:
>
> We do this only with VMEMMAP config so that our page_to_[nid/section] etc are
> not
> impacted.
>
> Signed-off-by: Aneesh Kumar K.V
Why 128TB, given that it's sparse_vmemmap_extreme by default, why not
1PB directly (50 bits)?
Balbir
Hi Nipun,
On Thu, Jun 21, 2018 at 03:59:27AM +, Nipun Gupta wrote:
> Will this patch-set be taken for the next kernel release (and via which
> tree)?
I think you need Acks from Robin and Joerg in order for this to be queued.
Robin should be back at the beginning of next month, so there's stil
On 06/21/2018 05:02 PM, Balbir Singh wrote:
On Thu, Jun 21, 2018 at 6:31 PM, Aneesh Kumar K.V
wrote:
We do this only with VMEMMAP config so that our page_to_[nid/section] etc are
not
impacted.
Signed-off-by: Aneesh Kumar K.V
Why 128TB, given that it's sparse_vmemmap_extreme by default, wh
On 06/21/2018 05:02 PM, Balbir Singh wrote:
On Thu, Jun 21, 2018 at 6:31 PM, Aneesh Kumar K.V
wrote:
We do this only with VMEMMAP config so that our page_to_[nid/section] etc are
not
impacted.
Signed-off-by: Aneesh Kumar K.V
Why 128TB, given that it's sparse_vmemmap_extreme by default, wh
On Thu, Jun 21, 2018 at 02:14:53PM +1000, Michael Ellerman wrote:
> Ram Pai writes:
> > On Tue, Jun 19, 2018 at 10:39:52PM +1000, Michael Ellerman wrote:
> >> Ram Pai writes:
> >>
> >> > In a multithreaded application, a key allocated by one thread must
> >> > be activate and usable on all threa
On Thu, Jun 21, 2018 at 02:13:40PM +1000, Michael Ellerman wrote:
> Ram Pai writes:
>
> > On Tue, Jun 19, 2018 at 10:39:56PM +1000, Michael Ellerman wrote:
> >> Ram Pai writes:
> >>
> >> > When a thread forks the contents of AMR, IAMR, UAMOR registers in the
> >> > newly forked thread are not i
On Thu, Jun 21, 2018 at 08:28:47PM +1000, Michael Ellerman wrote:
> Florian Weimer writes:
>
> > On 06/19/2018 02:40 PM, Michael Ellerman wrote:
> >>> I tested the whole series with the new selftests, with the printamr.c
> >>> program I posted earlier, and the glibc test for pkey_alloc &c. The
>
p improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Michael-Bringmann/powerpc-hotplug-Update-affinity-for-migrated-CPUs/20180621-085543
> base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
> config: powerpc-defconfig (attached as
p improve the system]
>
> url:
> https://github.com/0day-ci/linux/commits/Michael-Bringmann/powerpc-hotplug-Update-affinity-for-migrated-CPUs/20180621-085543
> base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
> config: powerpc-defconfig (attached as
ida_alloc_range is the perfect fit for this use case. Eliminates
a custom spinlock, a call to ida_pre_get and a local check for the
allocated ID exceeding a maximum.
Signed-off-by: Matthew Wilcox
---
arch/powerpc/mm/mmu_context_book3s64.c | 44 +++---
1 file changed, 4 inser
Removes a custom spinlock and simplifies the code.
Signed-off-by: Matthew Wilcox
---
arch/powerpc/platforms/powernv/vas-window.c | 26 -
1 file changed, 4 insertions(+), 22 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/vas-window.c
b/arch/powerpc/platforms/powern
On Wed, Jun 20, 2018 at 07:51:11PM -0300, Breno Leitao wrote:
> - strncpy(prog, argv[0], strlen(argv[0]));
> + strncpy(prog, argv[0], sizeof(prog) - 1);
strncpy(prog, argv[0], sizeof prog);
if (prog[sizeof prog - 1])
scream_bloody_murder();
Silently using t
On Thu, Jun 21, 2018 at 07:36:27PM +1000, Alexey Kardashevskiy wrote:
> At the moment we allocate the entire TCE table, twice (hardware part and
> userspace translation cache). This normally works as we normally have
> contigous memory and the guest will map entire RAM for 64bit DMA.
>
> However i
Vipin K Parashar writes:
> printk() in unmap_cpu_from_node() uses KERN_ERR message severity,
> for a WARNING message. Change it to pr_warn().
>
> Signed-off-by: Vipin K Parashar
> ---
> arch/powerpc/mm/numa.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/powerp
On Wed, Jun 20, 2018 at 06:42:58PM +1000, Alexey Kardashevskiy wrote:
> When attaching a hardware table to LIOBN in KVM, we match table parameters
> such as page size, table offset and table size. However the tables are
> created via very different paths - VFIO and KVM - and the VFIO path goes
> th
On Thu, 21 Jun 2018 14:28:22 -0700
Matthew Wilcox wrote:
> ida_alloc_range is the perfect fit for this use case. Eliminates
> a custom spinlock, a call to ida_pre_get and a local check for the
> allocated ID exceeding a maximum.
>
> Signed-off-by: Matthew Wilcox
> ---
> arch/powerpc/mm/mmu_co
On Fri, Jun 22, 2018 at 12:15:11PM +1000, Nicholas Piggin wrote:
> On Thu, 21 Jun 2018 14:28:22 -0700
> Matthew Wilcox wrote:
> > static int alloc_context_id(int min_id, int max_id)
...
> > - spin_lock(&mmu_context_lock);
> > - err = ida_get_new_above(&mmu_context_ida, min_id, &index);
> > -
On Thu, 21 Jun 2018 21:38:15 -0700
Matthew Wilcox wrote:
> On Fri, Jun 22, 2018 at 12:15:11PM +1000, Nicholas Piggin wrote:
> > On Thu, 21 Jun 2018 14:28:22 -0700
> > Matthew Wilcox wrote:
> > > static int alloc_context_id(int min_id, int max_id)
> ...
> > > - spin_lock(&mmu_context_lock);
On Tue, 19 Jun 2018, Arnd Bergmann wrote:
> The real-time clock on m68k (and powerpc) mac systems uses an unsigned
> 32-bit value starting in 1904, which overflows in 2040, about two years
> later than everyone else, but this gets wrapped around in the Linux code
> in 2038 already because of th
Hi Michael,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.18-rc1 next-20180621]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Nicholas Piggin writes:
> On Thu, 21 Jun 2018 14:28:22 -0700
> Matthew Wilcox wrote:
>
>> ida_alloc_range is the perfect fit for this use case. Eliminates
>> a custom spinlock, a call to ida_pre_get and a local check for the
>> allocated ID exceeding a maximum.
>>
>> Signed-off-by: Matthew Wil
Matthew Wilcox writes:
> this situation from occurring (like, oh i don't know, this function only
> being called on process exit, so implicitly only called once per context).
>
That is correct.
Signed-off-by: Michael Neuling
---
.../powerpc/transactional_memory.txt | 44 +++
1 file changed, 44 insertions(+)
diff --git a/Documentation/powerpc/transactional_memory.txt
b/Documentation/powerpc/transactional_memory.txt
index e32fdbb4c9..b254eab517 100644
--- a/Docu
Signed-off-by: Michael Neuling
---
Documentation/powerpc/DAWR-POWER9.txt | 58 +++
1 file changed, 58 insertions(+)
create mode 100644 Documentation/powerpc/DAWR-POWER9.txt
diff --git a/Documentation/powerpc/DAWR-POWER9.txt
b/Documentation/powerpc/DAWR-POWER9.txt
new fi
34 matches
Mail list logo
