Le 22/06/2021 à 08:04, Nicholas Piggin a écrit :
The PPC_RFI_SRR_DEBUG check added by patch "powerpc/64s: avoid reloading
(H)SRR registers if they are still valid" has a few deficiencies. It
does not fix the actual problem, it's not enabled by default, and it
causes a program check interrupt w
On 22/06/21 07:25, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
include/uapi/linux/kvm.h
between commit:
9bb4a6f38fd4 ("KVM: PPC: Book3S HV: Add KVM_CAP_PPC_RPT_INVALIDATE
capability")
from the powerpc tree and commits:
644f706719f0 (
The PPC_RFI_SRR_DEBUG check added by patch "powerpc/64s: avoid reloading
(H)SRR registers if they are still valid" has a few deficiencies. It
does not fix the actual problem, it's not enabled by default, and it
causes a program check interrupt which can cause more difficulties.
However there are a
This picks up a bunch of srr invalidation cases missed, and tries to
convert the entire tree including 64e and 32-bit to use the accessors,
to save headaches in future. It also avoids doing the general clobber
after changing several things, to always using the accessors (a few
extra stores to paca
These are a couple of improvements to the fast interrupt exits series
that fit after patch 4. The first patch is incremental to patch 4 and
should be folded in, the second could go anywhere in the series but I
based it on top.
I can rebase it or resend the series if needed.
Thanks,
Nick
Nicholas
copy-paste contains implicit "copy buffer" state that can contain
arbitrary user data (if the user process executes a copy instruction).
This could be snooped by another process if a context switch hits while
the state is live. So cp_abort is executed on context switch to clear
out possible sensiti
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
include/uapi/linux/kvm.h
between commit:
9bb4a6f38fd4 ("KVM: PPC: Book3S HV: Add KVM_CAP_PPC_RPT_INVALIDATE
capability")
from the powerpc tree and commits:
644f706719f0 ("KVM: x86: hyper-v: Introduce KVM_CAP_HYPERV_ENF
On Mon, Jun 21, 2021 at 10:12:42AM -0700, Nathan Chancellor wrote:
> > +long do_h_rpt_invalidate_pat(struct kvm_vcpu *vcpu, unsigned long lpid,
> > +unsigned long type, unsigned long pg_sizes,
> > +unsigned long start, unsigned long end)
> > +{
> > +
ig
powerpc allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a002-20210621
x86_64 randconfig-a001-20210621
x86_64 randconfig-a003-20210621
x86_64 randconfig-a00
Hi all,
After merging the irqchip tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
arch/powerpc/platforms/pseries/vas.c: In function 'allocate_setup_window':
arch/powerpc/platforms/pseries/vas.c:219:22: error: implicit declaration of
function 'irq_create_mapping' [-Werr
Daniel Axtens writes:
> Hi
>
>> -static char __init *prom_strcpy(char *dest, const char *src)
>> +static ssize_t __init prom_strscpy_pad(char *dest, const char *src, size_t
>> n)
>> {
>> -char *tmp = dest;
>> +ssize_t rc;
>> +size_t i;
>>
>> -while ((*dest++ = *src++) != '\0')
Clean up the following includecheck warning:
./arch/powerpc/kernel/interrupt.c: asm/interrupt.h is included more than
once.
No functional change.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Chong
---
arch/powerpc/kernel/interrupt.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/p
Hi!
On Mon, Jun 21, 2021 at 04:11:04PM +0200, Christophe Leroy wrote:
> Le 19/06/2021 à 17:02, Segher Boessenkool a écrit :
> >The point of the twi in the I/O accessors was to make things easier to
> >debug if the accesses fail: for the twi insn to complete the load will
> >have to have completed
On 6/17/21 1:51 PM, Aneesh Kumar K.V wrote:
PAPR interface currently supports two different ways of communicating resource
grouping details to the OS. These are referred to as Form 0 and Form 1
associativity grouping. Form 0 is the older format and is now considered
deprecated. This patch adds
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Mon, 21 Jun 2021 14:35:09 -0700 you wrote:
> Since these strings are expected to be NUL-terminated and the buffers
> are exactly sized (in vnic_client_data_len()) with no padding, strncpy()
> can be safely replaced with
Hi all,
Commit
77bbbc0cf848 ("KVM: PPC: Book3S HV: Fix TLB management on SMT8 POWER9 and
POWER10 processors")
is missing a Signed-off-by from its author.
--
Cheers,
Stephen Rothwell
pgpxXwMax8acq.pgp
Description: OpenPGP digital signature
Since these strings are expected to be NUL-terminated and the buffers
are exactly sized (in vnic_client_data_len()) with no padding, strncpy()
can be safely replaced with strscpy() here, as strncpy() on
NUL-terminated string is considered deprecated[1]. This has the
side-effect of silencing a -Warr
On Mon, Jun 21, 2021 at 10:59:20AM -0700, Stefano Stabellini wrote:
> Just as a clarification: I was referring to the zeroing of "mem" in
> swiotlb_late_init_with_tbl and swiotlb_init_with_tbl. While it looks
> like Tom and Christoph are talking about the zeroing of "tlb".
Indeed.
>
> The zeroi
On Tue, 15 Jun 2021 09:39:13 +0800, Yang Yingliang wrote:
> patch #1 ~ #8:
> Use devm_platform_get_and_ioremap_resource()
>
> patch #9
> check return value of platform_get_resource_byname()
>
> v2:
> change error message in patch #9
>
> [...]
Applied to
https://git.kernel.org/pub/scm/
LLVM does not emit optimal byteswap assembly, which results in high
stack usage in kvmhv_enter_nested_guest() due to the inlining of
byteswap_pt_regs(). With LLVM 12.0.0:
arch/powerpc/kvm/book3s_hv_nested.c:289:6: error: stack frame size of
2512 bytes in function 'kvmhv_enter_nested_guest' [-Werro
On Mon, Jun 21, 2021 at 07:46:03PM +1000, Michael Ellerman wrote:
> Nathan Chancellor writes:
> > On 6/20/2021 4:59 PM, Nicholas Piggin wrote:
> >> Excerpts from kernel test robot's message of April 3, 2021 8:47 pm:
> >>> tree:
> >>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linu
On Fri, 18 Jun 2021, Christoph Hellwig wrote:
> On Fri, Jun 18, 2021 at 09:09:17AM -0500, Tom Lendacky wrote:
> > > swiotlb_init_with_tbl uses memblock_alloc to allocate the io_tlb_mem
> > > and memblock_alloc[1] will do memset in memblock_alloc_try_nid[2], so
> > > swiotlb_init_with_tbl is also go
On Mon, 21 Jun 2021 at 19:32, Sachin Sant wrote:
>
> >>> Any thoughts Vincent?
> >>
> >>
> >> I would prefer that we use the reason of adding the cfs in the list
> >> instead.
> >>
> >> Something like the below should also fixed the problem. It is based on a
> >> proposal I made to Rik sometimes
>>> Any thoughts Vincent?
>>
>>
>> I would prefer that we use the reason of adding the cfs in the list instead.
>>
>> Something like the below should also fixed the problem. It is based on a
>> proposal I made to Rik sometimes ago when he tried to flatten the rq:
>> https://lore.kernel.org/lkml/
On Mon, Jun 21, 2021 at 02:20:01PM +0530, Bharata B Rao wrote:
> Enable support for process-scoped invalidations from nested
> guests and partition-scoped invalidations for nested guests.
>
> Process-scoped invalidations for any level of nested guests
> are handled by implementing H_RPT_INVALIDATE
Hi Sacha
On Mon, 21 Jun 2021 at 18:22, Vincent Guittot
wrote:
>
> Le lundi 21 juin 2021 à 14:42:23 (+0200), Odin Ugedal a écrit :
> > Hi,
> >
> > Did some more research, and it looks like this is what happens:
> >
> > $ tree /sys/fs/cgroup/ltp/ -d --charset=ascii
> > /sys/fs/cgroup/ltp/
> > |-- d
On Mon, 21 Jun 2021 at 18:45, Odin Ugedal wrote:
>
> man. 21. jun. 2021 kl. 18:22 skrev Vincent Guittot
> :
> > I would prefer that we use the reason of adding the cfs in the list instead.
> >
> > Something like the below should also fixed the problem. It is based on a
> > proposal I made to Rik
man. 21. jun. 2021 kl. 18:22 skrev Vincent Guittot :
> I would prefer that we use the reason of adding the cfs in the list instead.
>
> Something like the below should also fixed the problem. It is based on a
> proposal I made to Rik sometimes ago when he tried to flatten the rq:
> https://lore.ker
Le lundi 21 juin 2021 à 14:42:23 (+0200), Odin Ugedal a écrit :
> Hi,
>
> Did some more research, and it looks like this is what happens:
>
> $ tree /sys/fs/cgroup/ltp/ -d --charset=ascii
> /sys/fs/cgroup/ltp/
> |-- drain
> `-- test-6851
> `-- level2
> |-- level3a
> | |-- wo
Hello Fabiano,
Thank you for your review.
On 19/06/21 2:28 am, Fabiano Rosas wrote:
"Pratik R. Sampat" writes:
Adds a generic interface to represent the energy and frequency related
PAPR attributes on the system using the new H_CALL
"H_GET_ENERGY_SCALE_INFO".
H_GET_EM_PARMS H_CALL was previ
Le 19/06/2021 à 17:02, Segher Boessenkool a écrit :
On Sat, Jun 19, 2021 at 11:35:34AM +0200, Christophe Leroy wrote:
Le 18/06/2021 à 19:26, Mathieu Desnoyers a écrit :
- On Jun 18, 2021, at 1:13 PM, Christophe Leroy
christophe.le...@csgroup.eu wrote:
[...]
I don't understand all tha
On Sun, Jun 20, 2021 at 10:08:58PM +1000, Paul Mackerras wrote:
> On Sat, Jun 19, 2021 at 09:26:16AM -0500, Segher Boessenkool wrote:
> > On Fri, Jun 18, 2021 at 01:44:16PM +1000, Paul Mackerras wrote:
> > > Microwatt currently runs with MSR[HV] = 0,
> >
> > That isn't compliant though? If your i
Hi
> -static char __init *prom_strcpy(char *dest, const char *src)
> +static ssize_t __init prom_strscpy_pad(char *dest, const char *src, size_t n)
> {
> - char *tmp = dest;
> + ssize_t rc;
> + size_t i;
>
> - while ((*dest++ = *src++) != '\0')
> - /* nothing */;
> -
Hi,
Did some more research, and it looks like this is what happens:
$ tree /sys/fs/cgroup/ltp/ -d --charset=ascii
/sys/fs/cgroup/ltp/
|-- drain
`-- test-6851
`-- level2
|-- level3a
| |-- worker1
| `-- worker2
`-- level3b
`-- worker3
Timeline (i
On Mon, Jun 21, 2021 at 11:46 AM Michael Ellerman wrote:
> Nathan Chancellor writes:
> > On 6/20/2021 4:59 PM, Nicholas Piggin wrote:
> >> Excerpts from kernel test robot's message of April 3, 2021 8:47 pm:
> >>>
> >>> vim +/kvmhv_enter_nested_guest +264 arch/powerpc/kvm/book3s_hv_nested.c
> >>
>
man. 21. jun. 2021 kl. 12:57 skrev Sachin Sant :
>
> Unfortunately this does not help. I can still recreate the failure.
>
> Have attached the o/p from test run.
>
> Thanks
> -Sachin
Yes, thanks!
I am able to reproduce it locally now, so will keep looking to see if
I find the cause. Thanks!
Odin
> On 21-Jun-2021, at 3:24 PM, Odin Ugedal wrote:
>
> man. 21. jun. 2021 kl. 11:50 skrev Vincent Guittot
> :
>> This means that a child's load was not null and it was inserted
>> whereas parent's load was null. This should not happen unless the
>> propagation failed somewhere
>
> My initial th
man. 21. jun. 2021 kl. 11:50 skrev Vincent Guittot :
> This means that a child's load was not null and it was inserted
> whereas parent's load was null. This should not happen unless the
> propagation failed somewhere
My initial thought is that the patch below will fix it, if that is the
issue (th
man. 21. jun. 2021 kl. 08:33 skrev Sachin Sant :
>
> While running LTP tests (cfs_bandwidth01) against 5.13.0-rc7 kernel on a
> powerpc box
> following warning is seen
>
> [ 6611.331827] [ cut here ]
> [ 6611.331855] rq->tmp_alone_branch != &rq->leaf_cfs_rq_list
> [ 6611.33
On Mon, 21 Jun 2021 at 11:39, Odin Ugedal wrote:
>
> man. 21. jun. 2021 kl. 08:33 skrev Sachin Sant :
> >
> > While running LTP tests (cfs_bandwidth01) against 5.13.0-rc7 kernel on a
> > powerpc box
> > following warning is seen
> >
> > [ 6611.331827] [ cut here ]
> > [ 66
Nathan Chancellor writes:
> On 6/20/2021 4:59 PM, Nicholas Piggin wrote:
>> Excerpts from kernel test robot's message of April 3, 2021 8:47 pm:
>>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>> master
>>> head: d93a0d43e3d0ba9e19387be4dae4a8d5b175a8d7
>>> commit
On Wed, Jun 16, 2021 at 10:51:18AM +0200, Ondrej Mosnacek wrote:
> Commit 59438b46471a ("security,lockdown,selinux: implement SELinux
> lockdown") added an implementation of the locked_down LSM hook to
> SELinux, with the aim to restrict which domains are allowed to perform
> operations that would
In the nested KVM case, replace H_TLB_INVALIDATE by the new hcall
H_RPT_INVALIDATE if available. The availability of this hcall
is determined from "hcall-rpt-invalidate" string in ibm,hypertas-functions
DT property.
Signed-off-by: Bharata B Rao
Reviewed-by: Fabiano Rosas
Reviewed-by: David Gibso
Now that we have H_RPT_INVALIDATE fully implemented, enable
support for the same via KVM_CAP_PPC_RPT_INVALIDATE KVM capability
Signed-off-by: Bharata B Rao
Reviewed-by: David Gibson
---
Documentation/virt/kvm/api.rst | 18 ++
arch/powerpc/kvm/powerpc.c | 3 +++
include/uapi
Enable support for process-scoped invalidations from nested
guests and partition-scoped invalidations for nested guests.
Process-scoped invalidations for any level of nested guests
are handled by implementing H_RPT_INVALIDATE handler in the
nested guest exit path in L0.
Partition-scoped invalidat
This patchset adds support for the new hcall H_RPT_INVALIDATE
and replaces the nested tlb flush calls with this new hcall
if support for the same exists.
Changes in v8:
-
- Used tlb_single_page_flush_ceiling in the process-scoped range
flush routine to switch to full PID invalation i
H_RPT_INVALIDATE does two types of TLB invalidations:
1. Process-scoped invalidations for guests when LPCR[GTSE]=0.
This is currently not used in KVM as GTSE is not usually
disabled in KVM.
2. Partition-scoped invalidations that an L1 hypervisor does on
behalf of an L2 guest. This is curr
From: "Aneesh Kumar K.V"
The type values H_RPTI_TYPE_PRT and H_RPTI_TYPE_PAT indicate
invalidating the caching of process and partition scoped entries
respectively.
Signed-off-by: Aneesh Kumar K.V
Signed-off-by: Bharata B Rao
Reviewed-by: David Gibson
---
arch/powerpc/include/asm/hvcall.h |
Add a field to mmu_psize_def to store the page size encodings
of H_RPT_INVALIDATE hcall. Initialize this while scanning the radix
AP encodings. This will be used when invalidating with required
page size encoding in the hcall.
Signed-off-by: Bharata B Rao
Reviewed-by: David Gibson
---
arch/powe
49 matches
Mail list logo
