Stewart Smith writes:
> According to the OPAL docs:
> https://github.com/open-power/skiboot/blob/skiboot-5.2.5/doc/opal-api/opal-rtc-read-3.txt
> https://github.com/open-power/skiboot/blob/skiboot-5.2.5/doc/opal-api/opal-rtc-write-4.txt
> OPAL_HARDWARE may be returned from OPAL_RTC_READ or OPAL_R
Quoting Jack Miller (2016-08-02 06:50:35)
> Skiboot will place the flash device tree node at ibm,opal/flash/flash@0
> on P9 and later systems, so Linux needs to search for it there as well
> as ibm,opal/flash@0 for backwards compatibility.
>
> Signed-off-by: Jack Miller
> ---
> arch/powerpc/plat
On Wednesday, August 3, 2016 10:23:24 AM CEST Stephen Rothwell wrote:
> Hi Luis,
>
> On Wed, 3 Aug 2016 00:02:43 +0200 "Luis R. Rodriguez"
> wrote:
> >
> > Thanks for the confirmation. For how long is it known this is broken?
> > Does anyone care and fix these ? Or is this best effort?
>
> This
When decoding the perf_regs mask in perf_output_sample_regs(),
we loop through the mask using find_first_bit and find_next_bit functions.
While the exisitng code works fine in most of the case,
the logic is broken for 32bit kernel (Big Endian).
When reading u64 mask using (u32 *)(&val)[0], find_*_b
When decoding the perf_regs mask in regs_dump__printf(),
we loop through the mask using find_first_bit and find_next_bit functions.
"mask" is of type "u64", but sent as a "unsigned long *" to
lib functions along with sizeof().
While the exisitng code works fine in most of the case,
the logic is br
This adds a capability number for in-kernel support for VFIO on
SPAPR platform.
The capability will tell the user space whether in-kernel handlers of
H_PUT_TCE can handle VFIO-targeted requests or not. If not, the user space
must not attempt allocating a TCE table in the host kernel via
the KVM_CR
"powerpc/powernv/pci: Rework accessing the TCE invalidate register"
broke TCE invalidation on IODA2/PHB3 for real mode.
This makes invalidate work again.
Fixes: fd141d1a99a3
Signed-off-by: Alexey Kardashevskiy
---
arch/powerpc/platforms/powernv/pci-ioda.c | 4 +++-
1 file changed, 3 insertions(
In some situations the userspace memory context may live longer than
the userspace process itself so if we need to do proper memory context
cleanup, we better cache @mm and use it later when the process is gone
(@current or @current->mm are NULL).
This changes mm_iommu_xxx API to receive mm_struct
At the moment VFIO IOMMU SPAPR v2 driver pins all guest RAM pages when
the userspace starts using VFIO. When the userspace process finishes,
all the pinned pages need to be put; this is done as a part of
the userspace memory context (MM) destruction which happens on
the very last mmdrop().
This ap
VFIO on sPAPR already implements guest memory pre-registration
when the entire guest RAM gets pinned. This can be used to translate
the physical address of a guest page containing the TCE list
from H_PUT_TCE_INDIRECT.
This makes use of the pre-registrered memory API to access TCE list
pages in ord
In real mode, TCE tables are invalidated using special
cache-inhibited store instructions which are not available in
virtual mode
This defines and implements exchange_rm() callback. This does not
define set_rm/clear_rm/flush_rm callbacks as there is no user for those -
exchange/exchange_rm are onl
This is my current queue of patches to add acceleration of TCE
updates in KVM. This has a long history and was rewritten pretty
much completely again, this time I am teaching KVM about VFIO
containers. Some patches (such as 01/15) could be posted
separately but I keep all of them here to make revi
It does not make much sense to have KVM in book3s-64 and
not to have IOMMU bits for PCI pass through support as it costs little
and allows VFIO to function on book3s KVM.
Having IOMMU_API always enabled makes it unnecessary to have a lot of
"#ifdef IOMMU_API" in arch/powerpc/kvm/book3s_64_vio*. Wi
This reverts commit aa16bea929ae
("iommu: Add a function to find an iommu group by id")
as the iommu_group_get_by_id() helper has never been used
and it is unlikely it will in foreseeable future. Dead code
is broken code.
Signed-off-by: Alexey Kardashevskiy
---
drivers/iommu/iommu.c | 29 ---
The guest view TCE tables are per KVM anyway (not per VCPU) so pass kvm*
there. This will be used in the following patches where we will be
attaching VFIO containers to LIOBNs via ioctl() to KVM (rather than
to VCPU).
Signed-off-by: Alexey Kardashevskiy
---
arch/powerpc/include/asm/kvm_ppc.h |
178a787502 "vfio: Enable VFIO device for powerpc" made an attempt to
enable VFIO KVM device on POWER.
However as CONFIG_KVM_BOOK3S_64 does not use "common-objs-y",
VFIO KVM device was not enabled for Book3s KVM, this adds VFIO to
the kvm-book3s_64-objs-y list.
While we are here, enforce KVM_VFIO
This exports helpers which are needed to keep a VFIO container in
memory while there are external users such as KVM.
Signed-off-by: Alexey Kardashevskiy
---
drivers/vfio/vfio.c | 30 ++
drivers/vfio/vfio_iommu_spapr_tce.c | 16 +++-
include
This allows the host kernel to handle H_PUT_TCE, H_PUT_TCE_INDIRECT
and H_STUFF_TCE requests targeted an IOMMU TCE table used for VFIO
without passing them to user space which saves time on switching
to user space and back.
Both real and virtual modes are supported. The kernel tries to
handle a TC
At the moment iommu_table could be disposed by either calling
iommu_table_free() directly or it_ops::free() which only implementation
for IODA2 calls iommu_table_free() anyway.
As we are going to have reference counting on tables, we need an unified
way of disposing tables.
This moves it_ops::fre
So far iommu_table obejcts were only used in virtual mode and had
a single owner. We are going to change by implementing in-kernel
acceleration of DMA mapping requests, including real mode.
This adds a kref to iommu_table and defines new helpers to update it.
This replaces iommu_free_table() with
This makes mm_iommu_lookup() able to work in realmode by replacing
list_for_each_entry_rcu() (which can do debug stuff which can fail in
real mode) with list_for_each_entry_lockless().
This adds realmode version of mm_iommu_ua_to_hpa() which adds
explicit vmalloc'd-to-linear address conversion.
Un
Hello,
I tried to compile the latest Git kernel today. It boots but Xorg
doesn't work anymore.
[41.210] (++) using VT number 7
[41.341] (II) [KMS] Kernel modesetting enabled.
[41.341] (EE) No devices detected.
[41.341] (EE)
Fatal server error:
[41.3
On Wed, 3 Aug 2016 18:40:46 +1000
Alexey Kardashevskiy wrote:
> In some situations the userspace memory context may live longer than
> the userspace process itself so if we need to do proper memory context
> cleanup, we better cache @mm and use it later when the process is gone
> (@current or @c
On Wed, 3 Aug 2016 18:40:47 +1000
Alexey Kardashevskiy wrote:
> At the moment VFIO IOMMU SPAPR v2 driver pins all guest RAM pages when
> the userspace starts using VFIO. When the userspace process finishes,
> all the pinned pages need to be put; this is done as a part of
> the userspace memory c
On Wed, 2016-08-03 at 11:03 +0200, Christian Zigotzky wrote:
> I reverted the commit "powerpc-4.8-1" and Xorg works. The commit
> "powerpc-4.8-1" is the problem.
>
> Link:
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=bad60e6f259a01cf9f29a1ef8d435ab6c60b2de9
>
> W
Vlastimil Babka writes:
> On 08/03/2016 07:20 AM, Balbir Singh wrote:
>> On Tue, 2016-08-02 at 18:49 +0530, Srikar Dronamraju wrote:
>>> Fadump kernel reserves significant number of memory blocks. On a multi-node
>>> machine, with CONFIG_DEFFERRED_STRUCT_PAGE support, fadump kernel fails to
>>> b
hmi.c functions are unused unless sibling_subcore_state is nonzero, and
that in turn happens only if KVM is in use. So move the code to
arch/powerpc/kvm/, putting it under CONFIG_KVM_BOOK3S_64_HANDLER
rather than CONFIG_PPC_BOOK3S_64. The sibling_subcore_state is also
included in struct paca_stru
"Luis R. Rodriguez" writes:
> I've run into a few compilation issues with linker tables support [0]
> [1] on only a few architectures:
>
> blackfin - compiler issue it seems, I have a work around now in place
> arm - some alignment issue - still need to iron this out
> powerpc - issue with inclu
Hi Arnd,
On Wed, 03 Aug 2016 09:52:23 +0200 Arnd Bergmann wrote:
>
> Using a different way to link the kernel would also help us with
> the remaining allyesconfig problem on ARM, as the problem is only in
> 'ld -r' not producing trampolines for symbols that later cannot get
> them any more. It wo
On Wednesday, August 3, 2016 10:19:11 PM CEST Stephen Rothwell wrote:
> Hi Arnd,
>
> On Wed, 03 Aug 2016 09:52:23 +0200 Arnd Bergmann wrote:
> >
> > Using a different way to link the kernel would also help us with
> > the remaining allyesconfig problem on ARM, as the problem is only in
> > 'ld -r
On 07/24/2016 10:46 PM, Gavin Shan wrote:
On Mon, Jul 25, 2016 at 10:47:13AM +1000, Michael Ellerman wrote:
"Guilherme G. Piccoli" writes:
This is a very minor/trivial fix for the output of PCI address on EEH logs.
The PCI address on "OF node" field currently is using ":" as a separator
for t
On Wednesday 03 August 2016 01:27 AM, Scott Wood wrote:
On 08/02/2016 10:34 AM, arvind Yadav wrote:
On Tuesday 02 August 2016 01:15 PM, Arnd Bergmann wrote:
On Monday, August 1, 2016 4:55:43 PM CEST Scott Wood wrote:
On 08/01/2016 02:02 AM, Arnd Bergmann wrote:
diff --git a/include/linux/e
On Wed, 03 Aug 2016 14:29:13 +0200
Arnd Bergmann wrote:
> On Wednesday, August 3, 2016 10:19:11 PM CEST Stephen Rothwell wrote:
> > Hi Arnd,
> >
> > On Wed, 03 Aug 2016 09:52:23 +0200 Arnd Bergmann wrote:
> > >
> > > Using a different way to link the kernel would also help us with
> > > the r
On Wed, Aug 03, 2016 at 05:16:34PM +1000, Michael Ellerman wrote:
> We could instead just search for all nodes that are compatible with
> "ibm,opal-flash". We do that for i2c, see opal_i2c_create_devs().
>
> Is there a particular reason not to do that?
I'm actually surprised that this is preferre
This condenses the opal node searching into a single function that finds
all compatible nodes, instead of just searching the ibm,opal children,
for ipmi, flash, and prd similar to how opal-i2c nodes are found.
Signed-off-by: Jack Miller
---
arch/powerpc/platforms/powernv/opal.c | 22 ++--
(rebased on powerpc/next)
This condenses the opal node searching into a single function that finds
all compatible nodes, instead of just searching the ibm,opal children,
for ipmi, flash, and prd similar to how opal-i2c nodes are found.
Signed-off-by: Jack Miller
---
arch/powerpc/platforms/power
On 08/02/2016 11:38 PM, Srikar Dronamraju wrote:
> * Dave Hansen [2016-08-02 11:09:21]:
>> On 08/02/2016 06:19 AM, Srikar Dronamraju wrote:
>>> Kernels compiled with CONFIG_DEFERRED_STRUCT_PAGE_INIT will initialise
>>> only certain size memory per node. The certain size takes into account
>>> the
On Thursday, August 4, 2016 1:37:29 AM CEST Nicholas Piggin wrote:
>
> I've attached what I'm using, which builds and runs for me without
> any work. Your arch obviously has to select the option to use it.
>
> text data bss dec hex filename
> 11196784 1185024 192
On Tue, Aug 2, 2016 at 9:59 PM, Michael Ellerman wrote:
> lkdtm_rodata_do_nothing() is an empty function which is generated in
> order to test the non-executability of rodata.
>
> Currently if function tracing is enabled then an mcount callsite will be
> generated for lkdtm_rodata_do_nothing(), an
This patchset adds support to input system memory range based memory size
for fadump reservation. The crashkernel parameter already supports such
syntax. The first patch refactors the parsing code of crashkernel parameter
for reuse. The second patch uses the newly refactored parsing code to reserve
crashkernel parameter supports different syntaxes to specify the amount
of memory to be reserved for kdump kernel. Below is one of the supported
syntaxes that needs parsing to find the memory size to reserve, based on
memory range:
crashkernel=:[,:,...]
While such parsing is implemented f
Currently, memory for fadump can be specified with fadump_reserve_mem=size,
where only a fixed size can be specified. Add the below syntax as well, to
support conditional reservation based on system memory size:
fadump_reserve_mem=:[,:,...]
This syntax helps using the same commandline par
Hi Ben,
On 06/13/2016 06:26 PM, Benjamin Herrenschmidt wrote:
Another option would be to use a dma_attr for silencing mapping errors
which NVME could use provided it does handle them gracefully ...
I recently submitted patches that implement your suggestion [1].
May you please review/comment i
Hi Arnd,
On Wed, Aug 03, 2016 at 08:52:48PM +0200, Arnd Bergmann wrote:
> From my first look, it seems that all of lib/*.o is now getting linked
> into vmlinux, while we traditionally leave out everything from lib/
> that is not referenced.
>
> I also see a noticeable overhead in link time, the n
On Wednesday, August 3, 2016 2:44:29 PM CEST Segher Boessenkool wrote:
> Hi Arnd,
>
> On Wed, Aug 03, 2016 at 08:52:48PM +0200, Arnd Bergmann wrote:
> > From my first look, it seems that all of lib/*.o is now getting linked
> > into vmlinux, while we traditionally leave out everything from lib/
>
On Wed, 2016-08-03 at 16:39 -0300, Mauricio Faria de Oliveira wrote:
> Hi Ben,
>
> On 06/13/2016 06:26 PM, Benjamin Herrenschmidt wrote:
> >
> > Another option would be to use a dma_attr for silencing mapping
> > errors
> > which NVME could use provided it does handle them gracefully ...
>
> I r
This patchset introduces optional FC-TAPE/FC Class 3 Error Recovery to the
ibmvfc client driver.
Tyrel Datwyler (2):
ibmvfc: Set READ FCP_XFER_READY DISABLED bit in PRLI
ibmvfc: add FC Class 3 Error Recovery support
drivers/scsi/ibmvscsi/ibmvfc.c | 11 +++
drivers/scsi/ibmvscsi/ibmvf
The ibmvfc driver currently doesn't support FC Class 3 Error Recovery.
However, it is simply a matter of informing the VIOS that the payload
expects to use sequence level error recovery via a bit flag in the
ibmvfc_cmd structure.
This patch adds a module parameter to enable error recovery support
The READ FCP_XFER_READY DISABLED bit is required to always be set to
one since FCP-3. Set it in the service parameter page frame during
process login.
Signed-off-by: Tyrel Datwyler
---
drivers/scsi/ibmvscsi/ibmvfc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/scsi/ibmvscsi/ibmvfc
On 08/03/2016 06:34 PM, Benjamin Herrenschmidt wrote:
I think this is best done by the relevant community maintainer,
I just threw an idea but I'm not that familiar with the details:-)
Ok, sure; got it.
Did you send them to the lkml list ?
Yup, plus a few others lists from get_maintainer.pl
Hello,
I'm trying the systemtap approach and it looks promising. The script is
annotating strace-like output with capability, device access and RLIMIT
information. In the end there's a summary. Here's sample output from
wpa_supplicant run:
mprotect(0x7efebf14, 16384, PROT_READ) = 0 [DATA 5488
Hi Arnd,
On Wed, 03 Aug 2016 20:52:48 +0200 Arnd Bergmann wrote:
>
> Most of the difference appears to be in branch trampolines (634 added,
> 559 removed, 14837 unchanged) as you suspect, but I also see a couple
> of symbols show up in vmlinux that were not there before:
>
> -A __crc_dma_noop_op
Paolo Bonzini writes:
> hmi.c functions are unused unless sibling_subcore_state is nonzero, and
> that in turn happens only if KVM is in use. So move the code to
> arch/powerpc/kvm/, putting it under CONFIG_KVM_BOOK3S_64_HANDLER
> rather than CONFIG_PPC_BOOK3S_64. The sibling_subcore_state is a
Jack Miller writes:
> On Wed, Aug 03, 2016 at 05:16:34PM +1000, Michael Ellerman wrote:
>> We could instead just search for all nodes that are compatible with
>> "ibm,opal-flash". We do that for i2c, see opal_i2c_create_devs().
>>
>> Is there a particular reason not to do that?
>
> I'm actually
I am just testing the interaction of the mailing list with DKIM after removing
the footer.
--
Cheers,
Stephen Rothwell
Just like last time.
--
Cheers,
Stephen Rothwell
Hi all,
For some time we have been coping with DMARC by rewriting the sender address
for any email sent from a site with a restrictive DMARC policy. This was
because the DKIM verification would fail for such an email once it had been
processed by the mailing list software and so sites (like Yahoo
On Tue, 2016-08-02 at 10:07 +0200, Christophe Leroy wrote:
> commit 7aef4136566b0 ("powerpc32: rewrite csum_partial_copy_generic()
> based on copy_tofrom_user()") introduced a bug when destination
> address is odd and initial csum is not null
>
> In that (rare) case the initial csum value has to b
Mahesh J Salgaonkar writes:
> From: Mahesh Salgaonkar
>
> The current implementation of MCE early handling modifies CR0/1 registers
> without saving its old values. Fix this by moving early check for
> powersaving mode to machine_check_handle_early().
>From (internal bug report) it seems as thou
Benjamin Herrenschmidt writes:
> This sets the type of the interrupt appropriately. We set it as follow:
>
> - If not mapped from the device-tree, we use edge. This is the case
> of the virtual interrupts and PCI MSIs for example.
>
> - If mapped from the device-tree and #interrupt-cells is 2 (
From: Mahesh Salgaonkar
When machine check occurs with MSR(RI=0), it means MC interrupt is
unrecoverable and kernel goes down to panic path. But the console
message still shows it as recovered. This patch fixes the MCE console
messages.
Signed-off-by: Mahesh Salgaonkar
---
arch/powerpc/kernel/
Hi Michael,
> The optimised crc32c implementation depends on VMX (aka. Altivec)
> instructions, so the kernel must be built with Altivec support in
> order for the crc32c code to build.
Thanks for that, looks good.
Acked-by: Anton Blanchard
> Fixes: 6dd7a82cc54e ("crypto: powerpc - Add POWER8
The slot location code as part of EEH has never functioned perfectly on
every powerpc system. The device node properties "ibm,slot-loc",
"ibm,slot-location-code" and "ibm,io-base-loc-code" have all been
presented in different cases, and in some situations, there are legacy
platforms not conforming
This time with a PGP signature
--
Cheers,
Stephen Rothwell
pgpxkiMyeBowX.pgp
Description: OpenPGP digital signature
* Dave Hansen [2016-08-03 11:17:43]:
> On 08/02/2016 11:38 PM, Srikar Dronamraju wrote:
> > * Dave Hansen [2016-08-02 11:09:21]:
> >> On 08/02/2016 06:19 AM, Srikar Dronamraju wrote:
> >>> Kernels compiled with CONFIG_DEFERRED_STRUCT_PAGE_INIT will initialise
> >>> only certain size memory per n
We should set the error code here. Otherwise static checkers complain.
Signed-off-by: Dan Carpenter
diff --git a/arch/powerpc/sysdev/fsl_rio.c b/arch/powerpc/sysdev/fsl_rio.c
index 984e816..68e7c0d 100644
--- a/arch/powerpc/sysdev/fsl_rio.c
+++ b/arch/powerpc/sysdev/fsl_rio.c
@@ -491,6 +491,7 @
We should return -ENOMEM if alloc_spu_gang() fails.
Signed-off-by: Dan Carpenter
diff --git a/arch/powerpc/platforms/cell/spufs/inode.c
b/arch/powerpc/platforms/cell/spufs/inode.c
index 5be15cf..2975754 100644
--- a/arch/powerpc/platforms/cell/spufs/inode.c
+++ b/arch/powerpc/platforms/cell/spu
On Wed, Aug 03, 2016 at 06:40:43PM +1000, Alexey Kardashevskiy wrote:
> 178a787502 "vfio: Enable VFIO device for powerpc" made an attempt to
> enable VFIO KVM device on POWER.
>
> However as CONFIG_KVM_BOOK3S_64 does not use "common-objs-y",
> VFIO KVM device was not enabled for Book3s KVM, this a
On Wed, Aug 03, 2016 at 06:40:45PM +1000, Alexey Kardashevskiy wrote:
> "powerpc/powernv/pci: Rework accessing the TCE invalidate register"
> broke TCE invalidation on IODA2/PHB3 for real mode.
>
> This makes invalidate work again.
>
> Fixes: fd141d1a99a3
> Signed-off-by: Alexey Kardashevskiy
>
Scott,
On 4 August 2016 at 05:53, Scott Wood wrote:
> On Tue, 2016-08-02 at 10:07 +0200, Christophe Leroy wrote:
>> commit 7aef4136566b0 ("powerpc32: rewrite csum_partial_copy_generic()
>> based on copy_tofrom_user()") introduced a bug when destination
>> address is odd and initial csum is not nu
Hi all,
This is causing cppcheck warnings (having just landed in next):
[arch/powerpc/kernel/ptrace.c:2062]: (error) Uninitialized variable: ckpt_regs
[arch/powerpc/kernel/ptrace.c:2130]: (error) Uninitialized variable: ckpt_regs
This is from...
> -static int gpr32_get(struct task_struct *target
From: Anton Blanchard
This patch utilises the GENERIC_CPU_AUTOPROBE infrastructure
to automatically load the crc32c-vpmsum module if the CPU supports
it.
Signed-off-by: Anton Blanchard
---
arch/powerpc/crypto/crc32c-vpmsum_glue.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --
It appears that commit 75ef71840539 ("mm, vmstat: add infrastructure
for per-node vmstats", 2016-07-28) has introduced a regression on
machines that have nodes which have no memory, such as the POWER8
server that I use for testing. When I boot current upstream, I get a
splat like this:
[1.713
From: Anton Blanchard
Align the hot loops in our assembly implementation of memset()
and backwards_memcpy().
backwards_memcpy() is called from tcp_v4_rcv(), so we might
want to optimise this a little more.
Signed-off-by: Anton Blanchard
---
arch/powerpc/lib/mem_64.S | 2 ++
1 file changed, 2
74 matches
Mail list logo
