On 03/05/17 13:52, Rashmica Gupta wrote:
On 28/04/17 19:52, Anshuman Khandual wrote:
+static int check_memblock_online(struct memory_block *mem, void *arg)
+{
+if (mem->state != MEM_ONLINE)
+return -1;
+
+return 0;
+}
+
+static int change_memblock_state(struct memory_block
On 03/05/17 13:52, Rashmica Gupta wrote:
On 28/04/17 19:52, Anshuman Khandual wrote:
+static int check_memblock_online(struct memory_block *mem, void *arg)
+{
+if (mem->state != MEM_ONLINE)
+return -1;
+
+return 0;
+}
+
+static int change_memblock_state(struct memory_block
On Wed, 3 May 2017 14:44:59 +1000
Michael Ellerman wrote:
> Currently the radix TLB code includes support for CPUs that do *not*
> have MMU_FTR_LOCKLESS_TLBIE. On those CPUs we are required to take a
> global spinlock before issuing a tlbie.
>
> Radix can only be built for 64-bit Book3s CPUs, a
Currently the radix TLB code includes support for CPUs that do *not*
have MMU_FTR_LOCKLESS_TLBIE. On those CPUs we are required to take a
global spinlock before issuing a tlbie.
Radix can only be built for 64-bit Book3s CPUs, and of those, only
POWER4, 970, Cell and PA6T do not have MMU_FTR_LOCKLE
On 28/04/17 19:52, Anshuman Khandual wrote:
On 04/28/2017 11:12 AM, Rashmica Gupta wrote:
Some powerpc hardware features may want to gain access to a chunk of
What kind of features ? Please add specifics.
undisturbed real memory. This update provides a means to unplug said memory
Undisturbe
On 28/04/17 19:39, Anshuman Khandual wrote:
On 04/28/2017 11:12 AM, Rashmica Gupta wrote:
Signed-off-by: Rashmica Gupta
Please describe a bit about the function/feature you are trying
to add with this new config option. The subject says " Add config
option for removal of memory" but I guess i
On Tue, 2017-05-02 at 14:43 +0200, Juergen Schindele wrote:
> Dear Scott,
> sorry for the delay but i am not very familiar with the formating.
> I passed the patch trough checkpatch.pl and there was no more error.
> pease find patch in attached file.
> Thanks
Documentation/process/submitting-patch
Commit 616badd2fb49 ("powerpc/powernv: Use OPAL call for TCE kill on
NVLink2") forced all TCE kills to go via the OPAL call for
NVLink2. However the PHB3 implementation of TCE kill was still being
called directly from some functions which in some circumstances caused
a machine check.
This patch ad
On Thu, Apr 27, 2017 at 10:02:26PM +1000, Michael Ellerman wrote:
> The SLB miss handler calls slb_allocate_realmode() in order to create an
> SLB entry for the faulting address. At the very start of that function
> we check that the faulting Effective Address (EA) is less than
> PGTABLE_RANGE (ign
Hi all,
On Tue, 2 May 2017 18:21:12 -0400 Paul Gortmaker
wrote:
>
> In commit 461a6946b1f9 ("iommu: Remove pci.h include from
> trace/events/iommu.h") that header shuffle uncovered an implicit
> include in this driver, manifesting as:
>
> CC drivers/soc/fsl/qbman/qman_portal.o
> dr
In commit 461a6946b1f9 ("iommu: Remove pci.h include from
trace/events/iommu.h") that header shuffle uncovered an implicit
include in this driver, manifesting as:
CC drivers/soc/fsl/qbman/qman_portal.o
drivers/soc/fsl/qbman/qman_portal.c: In function 'qman_portal_probe':
drivers/s
On Friday 28 April 2017 09:59 AM, Liu ping fan wrote:
On Fri, Apr 28, 2017 at 2:06 AM, Hari Bathini
wrote:
Hi Pingfan,
On Thursday 27 April 2017 01:13 PM, Pingfan Liu wrote:
E.g after fadump reserves mem regions, these regions should not be removed
before fadump explicitly free them.
Signed
Hi Michal,
On Tuesday 02 May 2017 09:26 PM, Michal Suchanek wrote:
With fadump (dump capture) kernel booting like a regular kernel, it almost
needs the same amount of memory to boot as the production kernel, which is
unwarranted for a dump capture kernel. But with no option to disable some
of t
With the introduction of 'fadump_append=' parameter to pass additional
parameters to fadump (capture) kernel, update documentation about it.
Signed-off-by: Hari Bathini
Signed-off-by: Michal Suchanek
---
Documentation/powerpc/firmware-assisted-dump.txt | 8 +++-
1 file changed, 7 insertions
With fadump (dump capture) kernel booting like a regular kernel, it almost
needs the same amount of memory to boot as the production kernel, which is
unwarranted for a dump capture kernel. But with no option to disable some
of the unnecessary subsystems in fadump kernel, that much memory is wasted
There are two cases outside the normal address space management
where a CPU's local TLB is to be flushed:
1. Host boot; in case something has left stale entries in the
TLB (e.g., kexec).
2. Host machine check; to clean corrupted TLB entries.
CPU state restore from an idle state incurrin
On 5/2/2017 4:38 PM, Martin Hicks wrote:
>
> An updated patch that also handles the additional key length requirements
> for the AEAD algorithms.
>
> The max keysize is not 96. For SHA384/512 it's 128, and for the AEAD
> algorithms it's longer still. Extend the max keysize for the
> AEAD size f
An updated patch that also handles the additional key length requirements
for the AEAD algorithms.
The max keysize is not 96. For SHA384/512 it's 128, and for the AEAD
algorithms it's longer still. Extend the max keysize for the
AEAD size for AES256 + HMAC(SHA512).
Cc: # 3.6+
Fixes: 357fb6050
Stephen Rothwell writes:
> On Tue, 02 May 2017 19:53:25 +1000 Michael Ellerman
> wrote:
>>
>> Though we are supposed to be building with -Werror, so those should be
>> breaking the build. I assume you have turned Werror off?
>
> I assume that allyesconfig turns on CONFIG_PPC_DISABLE_WERROR ...
Dear Scott,
sorry for the delay but i am not very familiar with the formating.
I passed the patch trough checkpatch.pl and there was no more error.
pease find patch in attached file.
Thanks
--
i. A.
Jürgen Schindele
Softwareentwicklung
PSI Nentec GmbH
Greschbachstraße 12
76229 Karlsruhe
Deutschla
Le 01/05/2017 à 05:00, Nicholas Piggin a écrit :
On Fri, 28 Apr 2017 08:13:01 +0200 (CEST)
Christophe Leroy wrote:
Commit a7a9dcd882a67 ("powerpc: Avoid taking a data miss on every
userspace instruction miss") has shown that limiting the read of
faulting instruction to likely cases improves
Commit a7a9dcd882a67 ("powerpc: Avoid taking a data miss on every
userspace instruction miss") has shown that limiting the read of
faulting instruction to likely cases improves performance.
This patch goes further into this direction by limiting the read
of the faulting instruction to the only cas
OCC provides historical minimum and maximum value for the sensor
readings. This patch exports them as highest and lowest attributes
for the inband sensors copied by OCC to main memory.
Signed-off-by: Shilpasri G Bhat
---
Changes from V2:
- Dropped "curr" type of sensors to fix the compatible stri
Hi Michael,
On Tue, 2 May 2017 21:17:01 +1000 Stephen Rothwell
wrote:
>
> On Tue, 02 May 2017 19:53:25 +1000 Michael Ellerman
> wrote:
> >
> > Though we are supposed to be building with -Werror, so those should be
> > breaking the build. I assume you have turned Werror off?
>
> I assume tha
Hi Michael,
On Tue, 02 May 2017 19:53:25 +1000 Michael Ellerman wrote:
>
> Though we are supposed to be building with -Werror, so those should be
> breaking the build. I assume you have turned Werror off?
I assume that allyesconfig turns on CONFIG_PPC_DISABLE_WERROR ...
--
Cheers,
Stephen Rothw
Stephen Rothwell writes:
> Hi all,
>
> The linux-next build (powerpc allyesconfig) produced these warnings
> (and have for a while):
>
> arch/powerpc/kvm/book3s_pr_papr.c: In function 'kvmppc_h_pr_enter':
> arch/powerpc/kvm/book3s_pr_papr.c:53:2: warning: ignoring return value of
> 'copy_from_us
Le 01/05/2017 à 02:53, Alastair D'Silva a écrit :
From: Alastair D'Silva
In some situations, a faulty AFU slice may create an interrupt storm of
slice errors, rendering the machine unusable. Since these interrupts are
informational only, present the interrupt once, then mask it off to
prevent
27 matches
Mail list logo
