>> Oh, I see. Should I send the patch again with the above change? If so
>> should I mark it v3 or just v2?
>
> Easier for benh/mpe if you do ;)
> Be sure to include my reviewed-by tag in your v3.
Sure. I will send v3.
On 2016/12/13 01:06PM, PrasannaKumar Muralidharan wrote:
> Hi Naveen,
>
> >> Add modsw and moduw instruction emulation support to analyse_instr.
> >> modsw is an x-form instruction that calculates signed modulo of values
> >> stored in registers. moduw is similar to modsw but it works with
> >> un
Hi Naveen,
>> Add modsw and moduw instruction emulation support to analyse_instr.
>> modsw is an x-form instruction that calculates signed modulo of values
>> stored in registers. moduw is similar to modsw but it works with
>> unsigned values.
>>
>> Changes in v2:
>> Don't update CR register as th
Hi,
I'd like to revisit this patch to do the fixup of relative addresses
for "else" part of alternate instruction patching at compile-time rather
than runtime. Without this I pretty quickly run into "ftr_alt relocation
truncated to fit" errors when trying to use feature patching for anything
non-t
It looks like there may still be a recursive locking issue in this
patch, please don't merge just yet...
On 10/12/16 03:30, Frederic Barrat wrote:
+static inline int cxl_pcie_config_info(struct pci_bus *bus, unsigned
int devfn,
+ struct cxl_afu *afu, int *_record)
+{
+
On Tue, 13 Dec 2016 16:36:11 +1100
Balbir Singh wrote:
> On Mon, 2016-12-12 at 23:31 +1000, Nicholas Piggin wrote:
> > On Mon, 12 Dec 2016 20:50:03 +1100
> > Balbir Singh wrote:
> >
> > > This patch removes the disabling of interrupts
> > > in soft-disable mode, when interrupts are received
>
On 2016/12/07 11:15PM, PrasannaKumar Muralidharan wrote:
> Add modsw and moduw instruction emulation support to analyse_instr.
> modsw is an x-form instruction that calculates signed modulo of values
> stored in registers. moduw is similar to modsw but it works with
> unsigned values.
>
> Changes
On Mon, 2016-12-12 at 23:31 +1000, Nicholas Piggin wrote:
> On Mon, 12 Dec 2016 20:50:03 +1100
> Balbir Singh wrote:
>
> > This patch removes the disabling of interrupts
> > in soft-disable mode, when interrupts are received
> > (in lazy mode). The new scheme keeps the interrupts
> > enabled when
On Mon, 2016-12-12 at 09:24 -0600, Benjamin Herrenschmidt wrote:
> On Mon, 2016-12-12 at 23:31 +1000, Nicholas Piggin wrote:
> > Otherwise, this looks nice if it does the right thing with the
> > interrupt
> > controller. It hasn't taken a lot of lines to implement which is
> > very
> > cool.
>
>
Signed-off-by: Michał Mirosław
---
arch/powerpc/net/bpf_jit_comp.c | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/arch/powerpc/net/bpf_jit_comp.c b/arch/powerpc/net/bpf_jit_comp.c
index 7e706f3..22ae63f 100644
--- a/arch/powerpc/net/bpf_jit_comp.c
+++ b/arch
Signed-off-by: Michał Mirosław
---
include/linux/skbuff.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index 332e767..4a85a1f 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -768,6 +768,12 @@ struct sk_buff {
Extend the existing PRRN infrastructure to perform the actual affinity
updating for cpus and memory in addition to the device tree updating. For
cpus, dynamic affinity updating already appears to exist in the kernel in
the form of arch_update_cpu_topology. For memory, we must place a READD
operatio
Currently, memory must be hot removed and subsequently re-added in order
to dynamically update the affinity of LMBs specified by a PRRN event.
Earlier implementations of the PRRN event handler ran into issues in which
the hot remove would occur successfully, but a hotplug event would be
initiated f
Formerly, when we received a PRRN rtas event, device tree updating was
performed in the kernel and the actual topology updating was performed in
userspace. This was necessary as in order to update the topology for memory,
we must perform a hot remove and a subsequent hot add and until recently,
mem
On Wed, Dec 07, 2016 at 02:15:27PM -0800, Kees Cook wrote:
> Can you resend this patch with /proc/$pid/maps output showing the
> before/after effects of this change also included here? Showing that
> reduction in executable mapping should illustrate the benefit of
> avoiding having the execute bit
On 12/07/2016 01:16 AM, Michael Bringmann wrote:
> prom_init.c: Enable support for new DRC device tree properties
> "ibm,drc-info" and "ibm,dynamic-memory-v2" in initial handshake
> between the Linux kernel and the front end processor.
>
> Signed-off-by: Michael Bringmann
Reviewed-by: Nathan Fon
On 12/07/2016 01:15 AM, Michael Bringmann wrote:
> architecture.vec5 features: The boot-time memory management needs to
> know the form of the "ibm,dynamic-memory-v2" property early during
> scanning of the flattened device tree. This patch moves execution of
> the function pseries_probe_fw_featur
On 12/07/2016 01:15 AM, Michael Bringmann wrote:
> rpadlpar_core.c: Provide parallel routines to search the older device-
> tree properties ("ibm,drc-indexes", "ibm,drc-names", "ibm,drc-types"
> and "ibm,drc-power-domains"), or the new property "ibm,drc-info".
>
> The interface to examine the DRC
On 12/07/2016 01:14 AM, Michael Bringmann wrote:
> hotplug_init: Simplify the code needed for runtime memory hotplug and
> maintenance with a conversion routine that transforms the compressed
> property "ibm,dynamic-memory-v2" to the form of "ibm,dynamic-memory"
> within the "ibm,dynamic-reconfigur
On 12/07/2016 01:14 AM, Michael Bringmann wrote:
> powerpc/memory: Add parallel routines to parse the new property
> "ibm,dynamic-memory-v2" property when it is present, and then to
> finish initialization of the relevant memory structures with the
> operating system. This code is shared between t
On 12/07/2016 01:14 AM, Michael Bringmann wrote:
> powerpc/memory: Add parallel routines to parse the new property
> "ibm,dynamic-memory-v2" property when it is present, and then to
> register the relevant memory blocks with the operating system.
> This property format is intended to provide a more
On Mon, 2016-12-12 at 23:31 +1000, Nicholas Piggin wrote:
> Otherwise, this looks nice if it does the right thing with the interrupt
> controller. It hasn't taken a lot of lines to implement which is very
> cool.
We might want to be a bit careful. It will work with XICS fine, but it
might be trick
On 12/07/2016 01:14 AM, Michael Bringmann wrote:
> Firmware Features: Define new bit flags representing the presence of
> new device tree properties "ibm,drc-info", and "ibm,dynamic-memory-v2".
> These flags are used to tell the front end processor when the Linux
> kernel supports the new propertie
On Sun, Dec 11, 2016 at 01:08:33PM +1100, Balbir Singh wrote:
>
>
> On 11/12/16 04:17, Josh Poimboeuf wrote:
> > On Sat, Dec 10, 2016 at 04:46:17PM +1100, Balbir Singh wrote:
> >> On Thu, 2016-12-08 at 12:08 -0600, Josh Poimboeuf wrote:
> >>> Dusting the cobwebs off the consistency model again.
On Mon, 12 Dec 2016 20:50:03 +1100
Balbir Singh wrote:
> This patch removes the disabling of interrupts
> in soft-disable mode, when interrupts are received
> (in lazy mode). The new scheme keeps the interrupts
> enabled when we receive an interrupt and does the
> following
>
> a. On decrementer
This patch removes the disabling of interrupts
in soft-disable mode, when interrupts are received
(in lazy mode). The new scheme keeps the interrupts
enabled when we receive an interrupt and does the
following
a. On decrementer interrupt, instead of setting
dec to maximum and returning, we do the
We merge IPI and DEFAULT priorities to the same
value. The idea is to keep interrupts enabled
even in lazy soft-disabled mode. Instead of storing
the IPI and irq separately, we keep the levels
same so that we deal with only one of them
Cc: Michael Ellerman
Cc: Benjamin Herrenschmidt
Cc: Paul Mac
This patch is based on suggestions from paulus and benh.
The bugs are all mine. The idea was to implement soft
NMI(s) by keeping interrupts enabled in the soft-disabled
state, but to use the interrupt controller to gate posting
of new interrupts to the processor. This is still work in
progress and
Highlights include 8xx hugepage support, qbman fixes/cleanup, device
tree updates, and some misc cleanup.
The following changes since commit 555c16328ae6d75a90e234eac9b51998d68f185b:
powerpc/mm: Correct process and partition table max size (2016-11-17 17:11:53
+1100)
are available in the git
29 matches
Mail list logo
