We expect to have these configs on by default, most
distros turn them off, its always good to have them on
so that we can use them and hopefully not break them
Signed-off-by: Balbir Singh
---
arch/powerpc/configs/powernv_defconfig | 4
arch/powerpc/configs/ppc64_defconfig | 3 +++
arch/po
At the moment the userspace can request a table smaller than a page size
and this value will be stored as kvmppc_spapr_tce_table::size.
However the actual allocated size will still be aligned to the system
page size as alloc_page() is used there.
This aligns the table size up to the system page si
When the userspace requests a small TCE table (which takes less than
the system page size) and more than 1 TCE level, the existing code
returns a single page size which is a bug as each additional TCE level
requires at least one page and this is what
pnv_pci_ioda2_table_alloc_pages() does. And we e
>>
>> Yes. It was derived from TASK_SIZE :
>>
>> http://lxr.free-electrons.com/source/arch/powerpc/include/asm/processor.h#L105
>>
>
> That is getting update to 128TB by default and conditionally to 512TB
>
Since this is compile time, we should probably keep the scope to 128TB
for now and see if w
From: Rick Lindsley
With the 512TB virtual addressing capability, a new field was added to
the paca and mm_context (addr_limit) to track the process's desire to
use the larger addressing space. Functions in the radix-enabled path
(mmap.c) were modified to inspect this value when deciding whether
On Thu, 13 Apr 2017 16:27:34 +1000
Michael Neuling wrote:
> On Thu, 2017-04-13 at 14:12 +1000, Benjamin Herrenschmidt wrote:
> > On Thu, 2017-04-13 at 09:28 +0530, Aneesh Kumar K.V wrote:
> > > > #endif
> > > > mtctr r12
> > > > bctrl
> > > > +/*
> > > > + * cur_cpu_spec->cpu_
Enable 64K page size and THP. I use ppc64le_defconfig when I need
a single config across guest and host, but having 4K page size
as default is not what I expect. I could move these over to
server.config and merge if ppc64_defconfig is meant for systems
that use 4k pages by default.
Signed-off-by:
Hi Baldir
Le 13/04/2017 à 09:03, Balbir Singh a écrit :
We expect to have these configs on by default, most
distros turn them off, its always good to have them on
so that we can use them and hopefully not break them
Isn't it the purpose of the target allyesconfig to allow such tests ?
FTRACE
Implement a new SMP based watchdog rather than use the perf based
hardlockup detector. The new watchdog uses all SMP threads to watch
each other for lockups, by pinging a shared cpumask.
This has nothing really to do with NMIs at the moment, but it looks
into a couple of kernel options and APIs th
On Thu, Apr 13, 2017 at 12:28 PM, Aneesh Kumar K.V
wrote:
>
>
> On Thursday 13 April 2017 12:22 PM, Bhupesh Sharma wrote:
>>
>> Hi Aneesh,
>>
>> On Thu, Apr 13, 2017 at 12:06 PM, Aneesh Kumar K.V
>> wrote:
>>>
>>> Bhupesh Sharma writes:
>>>
powerpc arch_mmap_rnd() currently uses hard-coded
On Thu, 2017-04-13 at 09:24 +0200, Christophe LEROY wrote:
> Hi Baldir
Hi Christophe, It's Balbir
>
> Le 13/04/2017 à 09:03, Balbir Singh a écrit :
> > We expect to have these configs on by default, most
> > distros turn them off, its always good to have them on
> > so that we can use them and h
On Thu, Apr 13, 2017 at 11:25:39AM +0800, Jin, Yao wrote:
SNIP
> >
> > Now it works without my patch and it runs with latest perf/core branch.
> > So it looks like a regression issue.
> >
> > Thanks
> > Jin Yao
> >
> >
>
> I have tested, the regression issue is happened after this commit:
>
Le 13/04/2017 à 10:19, Balbir Singh a écrit :
On Thu, 2017-04-13 at 09:24 +0200, Christophe LEROY wrote:
Hi Baldir
Hi Christophe, It's Balbir
Sorry
Le 13/04/2017 à 09:03, Balbir Singh a écrit :
We expect to have these configs on by default, most
distros turn them off, its always good
Excerpts from Masami Hiramatsu's message of April 13, 2017 10:04:
On Wed, 12 Apr 2017 16:28:27 +0530
"Naveen N. Rao" wrote:
This helper will be used in a subsequent patch to emulate instructions
on re-entering the kprobe handler. No functional change.
In this case, please merge this patch in
On Wed, Apr 12, 2017 at 10:39:47AM -0700, Paul E. McKenney wrote:
> CONFIG_ARCH_WEAK_RELACQ Kconfig option.
Naming in the changelog and patch don't match.
> +config ARCH_WEAK_RELEASE_ACQUIRE
> + bool
> +
On Wed, Apr 12, 2017 at 10:39:47AM -0700, Paul E. McKenney wrote:
> The definition of smp_mb__after_unlock_lock() is currently smp_mb()
> for CONFIG_PPC and a no-op otherwise. It would be better to instead
> provide an architecture-selectable Kconfig option, and select the
> strength of smp_mb__af
Hypervisor Virtualization and Directed Hypervisor Doorbell interrupt
handlers use the macro EXC_VIRT_OOL_MASKABLE_HV for their relocation-on
handlers, which calls MASKABLE_RELON_EXCEPTION_HV_OOL, which uses the
real mode interrupt prolog.
Use the RELON variant instead to reduce overhead.
Fixes: 1
Michael Neuling writes:
> On Wed, 2017-04-12 at 17:16 +0530, Gautham R. Shenoy wrote:
>> From: "Gautham R. Shenoy"
>>
>> This patch ensures that POWER8 and POWER9 processors use the correct
>> value of IDLE_THREAD_BITS as POWER8 has 8 threads per core and hence
>> the IDLE_THREAD_BITS should be
Nicholas Piggin writes:
> On Thu, 13 Apr 2017 16:27:34 +1000
> Michael Neuling wrote:
>
>> On Thu, 2017-04-13 at 14:12 +1000, Benjamin Herrenschmidt wrote:
>> > On Thu, 2017-04-13 at 09:28 +0530, Aneesh Kumar K.V wrote:
>> > > > #endif
>> > > > mtctr r12
>> > > > bctrl
>> > >
Oliver O'Halloran writes:
> On Wed, Apr 12, 2017 at 11:53 AM, Balbir Singh wrote:
>>
>> The API also does not clear linear_map_hash_slots[] under DEBUG_PAGEALLOC
>
> I'm not sure what API you're referring to here. The tracking for
> linear_map_hash_slots[] is agnostic of mmu_hash_ops so we should
Since last:
- Ported up to powerpc next (thanks mpe)
- Dropped darn workaround from DD1 for now.
- Dropped the guest doorbell hack. It's not an immediate problem and
will be tackled in other ways.
Nicholas Piggin (4):
powerpc: change the doorbell IPI calling convention
powerpc: Introduce msg
Change the doorbell callers to know about their msgsnd addressing,
rather than have them set a per-cpu target data tag at boot that gets
sent to the cause_ipi functions. The data is only used for doorbell IPI
functions, no other IPI types, so it makes sense to keep that detail
local to doorbell.
H
POWER9 changes requirements and adds new instructions for
synchronization.
Signed-off-by: Nicholas Piggin
---
arch/powerpc/include/asm/dbell.h | 22 ++
arch/powerpc/include/asm/smp.h | 1 +
arch/powerpc/kernel/dbell.c | 8 +---
arch/powerpc/kernel/smp.c|
Signed-off-by: Nicholas Piggin
---
arch/powerpc/include/asm/dbell.h | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/powerpc/include/asm/dbell.h b/arch/powerpc/include/asm/dbell.h
index 350694a1a6e5..040944659a20 100644
--- a/arch/powerpc/include/asm/dbell.h
+++ b/ar
POWER9 requires msgsync for receiver-side synchronization, and a DD1
workaround restricts IPIs to core-local.
Signed-off-by: Nicholas Piggin
---
arch/powerpc/include/asm/dbell.h | 3 +++
arch/powerpc/include/asm/feature-fixups.h | 20
arch/powerpc/include/asm/ppc-o
On those three files, the ABI representation described at
README are violated.
- at sysfs-bus-iio-proximity-as3935:
a ':' character is missing after "What"
- at sysfs-class-devfreq:
there's a typo at Description
- at sysfs-class-cxl, it is using the ":" character at a
fil
Christophe LEROY writes:
> Hi Anton,
>
> Le 04/04/2017 à 00:00, Anton Blanchard a écrit :
>> Hi Christophe,
>>
- if (user_mode(regs))
+ if (!is_exec && user_mode(regs))
>>>
>>> Shouldn't it also check 'is_write' ?
>>> If it is a store, is_write should be set, shouldn't it ?
>>
>> Than
Balbir Singh writes:
> On Thu, 2017-04-06 at 23:06 +1000, Michael Ellerman wrote:
>> On Mon, 2017-04-03 at 06:41:02 UTC, Anton Blanchard wrote:
>> > From: Anton Blanchard
>> >
>> Applied to powerpc next, thanks.
>>
>> https://git.kernel.org/powerpc/c/a7a9dcd882a67b68568868b988289f
>>
>
> FYI:
rickl...@linux.vnet.ibm.com writes:
> From: Rick Lindsley
>
> With the 512TB virtual addressing capability, a new field was added to
> the paca and mm_context (addr_limit) to track the process's desire to
> use the larger addressing space. Functions in the radix-enabled path
> (mmap.c) were modi
Frederic Barrat writes:
> Le 12/04/2017 à 09:52, Andrew Donnellan a écrit :
>> On 08/04/17 00:11, Christophe Lombard wrote:
>>> +static u32 get_phb_index(struct device_node *np)
>>> {
>>> u32 phb_index;
>>>
>>> if (of_property_read_u32(np, "ibm,phb-index", &phb_index))
>>> -ret
On Fri, 2017-03-31 at 01:37:48 UTC, Oliver O'Halloran wrote:
> On Book3s we have two PTE flags used to mark cache-inhibited mappings:
> _PAGE_TOLERANT and _PAGE_NON_IDEMPOTENT. Currently the kernel page
> table dumper only looks at the generic _PAGE_NO_CACHE which is
> defined to be _PAGE_TOLERANT.
On Mon, 2017-04-10 at 02:04:04 UTC, Rashmica Gupta wrote:
> Current behaviour assumes that memory in RAM is contiguous and
> iterates from the start of RAM to (start + size of memory). When the
> memory isn't physically contiguous, this approach doesn't work.
>
> If memory exists at 0-5 GB and 6-1
On Wed, 2017-04-12 at 06:35:19 UTC, Balbir Singh wrote:
> This patch uses SYSCALL_DEFINE6 for sys_mmap and sys_mmap2
> so that the meta-data associated with these syscalls is
> visible to the syscall tracer. In the absence of this
> generic syscalls (defined outside arch) like munmap,etc.
> are vis
On Wed, 2017-04-12 at 10:11:07 UTC, Michael Ellerman wrote:
> Recently in commit f6eedbba7a26 ("powerpc/mm/hash: Increase VA range to
> 128TB"),
> we increased H_PGD_INDEX_SIZE to 15 when we're building with 64K pages. This
> makes it larger than RADIX_PGD_INDEX_SIZE (13), which means the logic to
Christophe LEROY writes:
> Hello Michael and Scott,
>
> I see that the status of the below patch has been changed to 'Not
> Applicable' in the linuxppc-dev Patchwork.
>
> About this serie, David S. Miller said:
>
> Sujet : Re: [PATCH 0/2] get rid of immrbar_virt_to_phys()
> Date : Wed, 08 Feb 20
Christophe LEROY writes:
> Hi Rashmica,
>
> Le 17/11/2016 à 13:03, Michael Ellerman a écrit :
>> On Fri, 2016-27-05 at 05:48:59 UTC, Rashmica Gupta wrote:
>>> Useful to be able to dump the kernels page tables to check permissions
>>> and memory types - derived from arm64's implementation.
>>>
>>>
On Thu, Apr 13, 2017 at 08:00:47PM +1000, Michael Ellerman wrote:
> Michael Neuling writes:
>
> > On Wed, 2017-04-12 at 17:16 +0530, Gautham R. Shenoy wrote:
> >> From: "Gautham R. Shenoy"
> >>
> >> This patch ensures that POWER8 and POWER9 processors use the correct
> >> value of IDLE_THREAD_B
Anju T Sudhakar writes:
> On Thursday 06 April 2017 02:07 PM, Stewart Smith wrote:
>> Madhavan Srinivasan writes:
>>> --- a/arch/powerpc/platforms/powernv/opal-imc.c
>>> +++ b/arch/powerpc/platforms/powernv/opal-imc.c
>>> @@ -33,6 +33,388 @@
>>
>>> +static void imc_pmu_setup(struct device_node *
On 04/13/2017 03:58 AM, Aneesh Kumar K.V wrote:
I would suggest we don't do this change now. But rather we audit the
usage of TASK_SIZE(), mm->task_size and move them correctly to
mm->task_size and mm->context.addr_limit. The context.addr_limit is
added as an optimization for slice_mask copy and
On Thursday 13 April 2017 05:13 PM, Rick Lindsley wrote:
On 04/13/2017 03:58 AM, Aneesh Kumar K.V wrote:
I would suggest we don't do this change now. But rather we audit the
usage of TASK_SIZE(), mm->task_size and move them correctly to
mm->task_size and mm->context.addr_limit. The context.ad
On Thu, Apr 13, 2017 at 6:41 PM, Christophe LEROY
wrote:
>
>
> Le 13/04/2017 à 10:19, Balbir Singh a écrit :
>>
>> On Thu, 2017-04-13 at 09:24 +0200, Christophe LEROY wrote:
>>>
>>> Hi Baldir
>>
>>
>> Hi Christophe, It's Balbir
>
>
> Sorry
>
No worries!
>>
>>>
>>> Le 13/04/2017 à 09:03, Balbir Si
On Thu, Apr 13, 2017 at 04:55:45PM +1000, Michael Neuling wrote:
> On Wed, 2017-04-12 at 17:16 +0530, Gautham R. Shenoy wrote:
> > From: "Gautham R. Shenoy"
> >
> > The idle-exit code assumes that if Timebase is not lost, then neither
> > are the per-core hypervisor resources lost.
>
> Double n
On Thu, Apr 13, 2017 at 05:18:17PM +1000, Nicholas Piggin wrote:
> On Thu, 13 Apr 2017 16:27:34 +1000
> Michael Neuling wrote:
>
> > On Thu, 2017-04-13 at 14:12 +1000, Benjamin Herrenschmidt wrote:
> > > On Thu, 2017-04-13 at 09:28 +0530, Aneesh Kumar K.V wrote:
> > > > > #endif
> > > > >
On Thu, 13 Apr 2017 17:24:34 +0530
Gautham R Shenoy wrote:
> On Thu, Apr 13, 2017 at 05:18:17PM +1000, Nicholas Piggin wrote:
> > On Thu, 13 Apr 2017 16:27:34 +1000
> > Michael Neuling wrote:
> >
> > > On Thu, 2017-04-13 at 14:12 +1000, Benjamin Herrenschmidt wrote:
> > > > On Thu, 2017-04-
On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote:
> From: Sukadev Bhattiprolu
>
> perf_mem_data_src is an union that is initialized via the ->val field
> and accessed via the bitmap fields. For this to work on big endian
> platforms (Which is broken now), we also need a big-end
On PPC32 (ex: mpc885_ads_defconfig), page table dump compilation
fails as follows. This is because the memory layout is slightly
different on PPC32. This patch adapts it.
CC arch/powerpc/mm/dump_linuxpagetables.o
arch/powerpc/mm/dump_linuxpagetables.c: In function 'walk_pagetables':
arch/po
On some targets, _PAGE_RW is 0 and this is _PAGE_RO which is used.
There is also _PAGE_SHARED that is missing
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/dump_linuxpagetables.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/arch/powerpc/mm/dump_linuxpagetables.c
b/arch/pow
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/dump_linuxpagetables.c | 4
1 file changed, 4 insertions(+)
diff --git a/arch/powerpc/mm/dump_linuxpagetables.c
b/arch/powerpc/mm/dump_linuxpagetables.c
index 98b7b07c6863..05109d7fa027 100644
--- a/arch/powerpc/mm/dump_linuxpagetables.c
Page table dump is a powerpc specific thing, so it should
appear in powerpc/ subdirectory of debugfs
Signed-off-by: Christophe Leroy
---
arch/powerpc/mm/dump_linuxpagetables.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/mm/dump_linuxpagetables.c
b/arch
Le 13/04/2017 à 13:31, Michael Ellerman a écrit :
Christophe LEROY writes:
Hi Rashmica,
Le 17/11/2016 à 13:03, Michael Ellerman a écrit :
On Fri, 2016-27-05 at 05:48:59 UTC, Rashmica Gupta wrote:
Useful to be able to dump the kernels page tables to check permissions
and memory types - der
Currently powerpc's asm/io.h includes linux/io.h, and linux/io.h
includes asm/io.h.
This can cause problems because depending on which is included first the
order of definitions between the two files will change.
The include of linux/io.h was added back in 2008 in commit b41e5fffe8b8
("[POWERPC]
Christophe LEROY writes:
> Le 13/04/2017 à 13:31, Michael Ellerman a écrit :
>> Christophe LEROY writes:
>>> Le 17/11/2016 à 13:03, Michael Ellerman a écrit :
On Fri, 2016-27-05 at 05:48:59 UTC, Rashmica Gupta wrote:
> Useful to be able to dump the kernels page tables to check permission
Christophe Leroy writes:
> Page table dump is a powerpc specific thing, so it should
> appear in powerpc/ subdirectory of debugfs
It's not powerpc specific. x86, arm, arm64 and s390 all have it.
But, I notice we somehow got the name wrong :}
All the other arches call it "kernel_page_tables".
Peter Zijlstra writes:
> On Tue, Apr 11, 2017 at 07:21:05AM +0530, Madhavan Srinivasan wrote:
>> From: Sukadev Bhattiprolu
>>
>> perf_mem_data_src is an union that is initialized via the ->val field
>> and accessed via the bitmap fields. For this to work on big endian
>> platforms (Which is bro
On Thu, 30 Mar 2017 13:30:17 -0300
Paulo Flabiano Smorigo wrote:
> On 2017-03-29 20:08, Tyrel Datwyler wrote:
> > On 03/29/2017 08:13 AM, Michal Suchánek wrote:
> >> On Wed, 29 Mar 2017 16:51:35 +0200
> >> Greg Kroah-Hartman wrote:
> >>
> >>> On Wed, Mar 29, 2017 at 02:56:39PM +0200, Michal
Nicholas Piggin writes:
> Hypervisor Virtualization and Directed Hypervisor Doorbell interrupt
> handlers use the macro EXC_VIRT_OOL_MASKABLE_HV for their relocation-on
> handlers, which calls MASKABLE_RELON_EXCEPTION_HV_OOL, which uses the
> real mode interrupt prolog.
>
> Use the RELON variant
Michael Ellerman writes:
> Of the 64-bit Book3S platforms, only powermac supports booting on an
> actual non-SMP system. The other platforms can be built with SMP
> disabled, but it doesn't make a lot of sense given the CPUs they support
> are all multicore or multithreaded.
>
> So give platforms
On 13/04/17 20:08, Mauro Carvalho Chehab wrote:
diff --git a/Documentation/ABI/testing/sysfs-class-cxl
b/Documentation/ABI/testing/sysfs-class-cxl
index 640f65e79ef1..d0b32452dfe1 100644
--- a/Documentation/ABI/testing/sysfs-class-cxl
+++ b/Documentation/ABI/testing/sysfs-class-cxl
@@ -1,6 +1,6
This patch is a bunch of small cleanups of the do_page_fault()
function:
1/ Function store_updates_sp() checks whether the faulting
instruction is a store updating r1. Therefore we can limit its calls
to stores exceptions
2/ Only the get_user() in store_updates_sp() has to be done outside
the mm se
Excerpts from Balbir Singh's message of April 13, 2017 12:33:
We expect to have these configs on by default, most
distros turn them off, its always good to have them on
so that we can use them and hopefully not break them
Thanks! I find myself constantly enabling these options.
Signed-off-by
Hi Rick,
[auto build test ERROR on powerpc/next]
[also build test ERROR on next-20170413]
[cannot apply to v4.11-rc6]
[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/commits/ricklind-linux-vnet-ibm-com
On Thu, Apr 13, 2017 at 11:21:53AM +0200, Peter Zijlstra wrote:
> On Wed, Apr 12, 2017 at 10:39:47AM -0700, Paul E. McKenney wrote:
>
> > CONFIG_ARCH_WEAK_RELACQ Kconfig option.
>
> Naming in the changelog and patch don't match.
Good eyes! Fixed.
On Thu, Apr 13, 2017 at 11:24:18AM +0200, Peter Zijlstra wrote:
> On Wed, Apr 12, 2017 at 10:39:47AM -0700, Paul E. McKenney wrote:
> > The definition of smp_mb__after_unlock_lock() is currently smp_mb()
> > for CONFIG_PPC and a no-op otherwise. It would be better to instead
> > provide an archite
On Thu, Apr 13, 2017 at 09:26:51AM -0700, Paul E. McKenney wrote:
> ARCH_WEAK_RELEASE_ACQUIRE actually works both ways.
>
> To see this, imagine some strange alternate universe in which the Power
> hardware guys actually did decide to switch PPC to doing RCsc as you
> suggest. There would still
On Thu, Apr 13, 2017 at 06:37:57PM +0200, Peter Zijlstra wrote:
> On Thu, Apr 13, 2017 at 09:26:51AM -0700, Paul E. McKenney wrote:
>
> > ARCH_WEAK_RELEASE_ACQUIRE actually works both ways.
> >
> > To see this, imagine some strange alternate universe in which the Power
> > hardware guys actually
Hello Wolfram,
This series is a follow-up to patch [0] that added an OF device ID table
to the at24 EEPROM driver. As you suggested [1], this version instead of
adding entries for every used tuple, only adds a single
entry for each chip type using the "atmel" vendor as a generic fallback.
The fi
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
We don't init addr_limit correctly for 32 bit applications. So default to using
mm->task_size for boundary condition checking. We use addr_limit to only control
free space search. This makes sure that we do the right thing with 32 bit
applications.
We should consolidate the usage of TASK_SIZE/mm->
rickl...@linux.vnet.ibm.com writes:
> From: Rick Lindsley
>
> However, the non-radix path falls through to the old, hashed slice code
> (slice_get_unmapped_area, etc.) and these code paths still inspect
> task_size. The same attention to addr_limit made in (for example)
> radix__arch_get_unmapp
On Thu, 13 Apr 2017 01:59:13 +0530
Hari Bathini wrote:
> On Friday 07 April 2017 07:16 PM, Michael Ellerman wrote:
> > Hari Bathini writes:
> >> On Friday 07 April 2017 07:24 AM, Michael Ellerman wrote:
> >>> My preference would be that the fadump kernel "just works". If
> >>> it's using too
> On Apr 13, 2017, at 1:27 AM, Andrew Donnellan
> wrote:
>
> On 13/04/17 05:14, Uma Krishnan wrote:
>> From: "Matthew R. Ochs"
>>
>> An EEH during probe can lead to a crash as the recovery thread races
>> with the probe thread. To avoid this issue, introduce new states to
>> fence out EEH reco
> On Apr 12, 2017, at 2:15 PM, Uma Krishnan wrote:
>
> Introduce multiple hardware queues to improve legacy I/O path performance.
> Each hardware queue is comprised of a master context and associated I/O
> resources. The hardware queues are initially implemented as a static array
> embedded in th
> On Apr 11, 2017, at 6:13 AM, Frederic Barrat
> wrote:
> Le 11/04/2017 à 12:40, Michael Ellerman a écrit :
>> Frederic Barrat writes:
>>
>>> Le 05/04/2017 à 13:35, Vaibhav Jain a écrit :
During an eeh event when the cxl card is fenced and card sysfs attr
perst_reloads_same_image is s
> On Mar 24, 2017, at 11:03 AM, Matthew R. Ochs
> wrote:
>
> Add support for future IBM Coherent Accelerator (CXL) devices
> with an IDs of 0x0623 and 0x0628.
>
> Signed-off-by: Matthew R. Ochs
> Signed-off-by: Uma Krishnan
> Acked-by: Frederic Barrat
Hi Michael,
I think this one might hav
Madhavan Srinivasan writes:
> @@ -269,7 +263,7 @@ notrace void arch_local_irq_restore(unsigned long en)
> replay = __check_irq_replay();
>
> /* We can soft-enable now */
> - set_soft_enabled(IRQ_DISABLE_MASK_NONE);
> + soft_enabled_set(IRQ_DISABLE_MASK_NONE);
In upstream we
Hello Wolfram,
This series is a follow-up to patch [0] that added an OF device ID table
to the at24 EEPROM driver. As you suggested [1], this version instead of
adding entries for every used tuple, only adds a single
entry for each chip type using the "atmel" vendor as a generic fallback.
The fi
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
The at24 driver allows to register I2C EEPROM chips using different vendor
and devices, but the I2C subsystem does not take the vendor into account
when matching using the I2C table since it only has device entries.
But when matching using an OF table, both the vendor and device has to be
taken in
Uma,
> This patch series contains miscellaneous patches and adds 4 port
> device support. This series also includes patches to improve
> performance of the driver in the legacy IO path.
Applied to 4.12/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Hi Christophe,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.11-rc6 next-20170413]
[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/commits/Christophe-Leroy/powerpc-mm-Fix-missing
On 04/13/2017 12:33 PM, Aneesh Kumar K.V wrote:
I missed this part earlier. I guess that should be fixed in radix code.
This came in via fbfef9027c2a7ad9277755509fdb849dbccfe8c1 (powerpc/mm:
Switch some TASK_SIZE checks to use mm_context addr_limit). That patch
needs update. When we switched fro
On some targets, _PAGE_RW is 0 and this is _PAGE_RO which is used.
There is also _PAGE_SHARED that is missing.
Signed-off-by: Christophe Leroy
---
v2: Unlike the 3 other pgtable.h, arch/powerpc/include/asm/book3s/64/pgtable.h
doesn't include pte-common.h . Therefore, _PAGE_SHARED has to be defi
90 matches
Mail list logo
