On Wed, Sep 13, 2023 at 06:55:08PM -0700, Sean Christopherson wrote:
> Add flags to "struct kvm_gfn_range" to let notifier events target only
> shared and only private mappings, and write up the existing mmu_notifier
> events to be shared-only (private memory is never associated with a
> userspace
On Wed, Sep 13, 2023 at 06:55:12PM -0700, Sean Christopherson wrote:
> TODO
>
> Cc: Fuad Tabba
> Cc: Vishal Annapurve
> Cc: Ackerley Tng
> Cc: Jarkko Sakkinen
> Cc: Maciej Szmigiero
> Cc: Vlastimil Babka
> Cc: David Hildenbrand
> Cc: Quentin Perret
> C
n
Cc: Cedric Le Goater
Cc: Greg Kurz
Cc: Nathan Lynch
Signed-off-by: Michael Roth
---
changes from v1:
- renamed from "powerpc/pseries/hotplug-cpu: increase wait time for vCPU death"
- wait indefinitely, but issue cond_resched() when RTAS reports that CPU
hasn't stopped (Michael
Quoting Nathan Lynch (2020-08-07 02:05:09)
> Hi everyone,
>
> Michael Ellerman writes:
> > Greg Kurz writes:
> >> On Tue, 04 Aug 2020 23:35:10 +1000
> >> Michael Ellerman wrote:
> >>> Spinning forever seems like a bad idea, but as has been demonstrated at
> >>> least twice now, continuing when
Quoting Michael Roth (2020-08-05 17:29:28)
> Quoting Michael Roth (2020-08-04 23:37:32)
> > Quoting Michael Ellerman (2020-08-04 22:07:08)
> > > Greg Kurz writes:
> > > > On Tue, 04 Aug 2020 23:35:10 +1000
> > > > Michael Ellerman wrote:
>
Quoting Michael Roth (2020-08-04 23:37:32)
> Quoting Michael Ellerman (2020-08-04 22:07:08)
> > Greg Kurz writes:
> > > On Tue, 04 Aug 2020 23:35:10 +1000
> > > Michael Ellerman wrote:
> > >> Spinning forever seems like a bad idea, but as has been
Quoting Michael Ellerman (2020-08-04 22:07:08)
> Greg Kurz writes:
> > On Tue, 04 Aug 2020 23:35:10 +1000
> > Michael Ellerman wrote:
> >> There is a bit of history to this code, but not in a good way :)
> >>
> >> Michael Roth writes:
> >>
zilla.redhat.com/show_bug.cgi?id=1856588
Cc: Michael Ellerman
Cc: Cedric Le Goater
Cc: Greg Kurz
Cc: Nathan Lynch
Signed-off-by: Michael Roth
---
arch/powerpc/platforms/pseries/hotplug-cpu.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/platforms/pseries/hotpl
far.
Fix this by setting r3 to 0 after we finish processing the H_CEDE.
RHBZ: 1778556
Fixes: 4bad77799fed ("KVM: PPC: Book3S HV: Handle hypercalls correctly when
nested")
Cc: linuxppc-...@ozlabs.org
Cc: David Gibson
Cc: Paul Mackerras
Signed-off-by: Michael Roth
---
arch/powerpc/kvm/
Quoting Alexey Kardashevskiy (2019-12-11 16:47:30)
>
>
> On 12/12/2019 07:31, Michael Roth wrote:
> > Quoting Alexey Kardashevskiy (2019-12-11 02:15:44)
> >>
> >>
> >> On 11/12/2019 02:35, Ram Pai wrote:
> >>> On Tue, Dec 10
Quoting Ram Pai (2019-12-12 00:45:02)
> On Tue, Dec 10, 2019 at 07:43:24PM -0600, Michael Roth wrote:
> > Quoting Ram Pai (2019-12-06 19:12:39)
> > > Commit edea902c1c1e ("powerpc/pseries/iommu: Don't use dma_iommu_ops on
> > > secure guests&quo
Quoting Alexey Kardashevskiy (2019-12-11 02:15:44)
>
>
> On 11/12/2019 02:35, Ram Pai wrote:
> > On Tue, Dec 10, 2019 at 04:32:10PM +1100, Alexey Kardashevskiy wrote:
> >>
> >>
> >> On 10/12/2019 16:12, Ram Pai wrote:
> >>> On Tue, Dec 10, 2019 at 02:07:36PM +1100, Alexey Kardashevskiy wrote:
>
Quoting Alexey Kardashevskiy (2019-12-11 02:36:29)
>
>
> On 11/12/2019 12:43, Michael Roth wrote:
> > Quoting Ram Pai (2019-12-06 19:12:39)
> >> Commit edea902c1c1e ("powerpc/pseries/iommu: Don't use dma_iommu_ops on
> >> secure gue
Quoting Ram Pai (2019-12-06 19:12:39)
> Commit edea902c1c1e ("powerpc/pseries/iommu: Don't use dma_iommu_ops on
> secure guests")
> disabled dma_iommu_ops path, for secure VMs. Disabling dma_iommu_ops
> path for secure VMs, helped enable dma_direct path. This enabled
> support for
Quoting Michael S. Tsirkin (2019-11-06 12:06:37)
> On Wed, Nov 06, 2019 at 12:59:50PM +1100, Alexey Kardashevskiy wrote:
> >
> >
> > On 05/11/2019 08:28, Ram Pai wrote:
> > > This patch series enables IOMMU support for pseries Secure VMs.
> > >
> > >
> > > Tested using QEMU command line
change in place the above workload ran for 20 hours without
triggering any lock-ups.
Fixes: 755563bc79c7 ("powerpc/powernv: Fixes for hypervisor doorbell handling")
# v4.0
Cc: Michael Ellerman
Cc: Paul Mackerras
Cc: Nicholas Piggin
Cc: kvm-...@vger.kernel.org
Signed-off-by: Micha
Quoting Michael Roth (2019-09-05 18:21:22)
> Quoting Michael Ellerman (2019-09-04 22:04:48)
> > That raises the question of whether this needs to be a full barrier or
> > just a write barrier, and where is the matching barrier on the reading
> > side?
>
> For this parti
Quoting Michael Ellerman (2019-09-04 22:04:48)
> Hi Mike,
>
> Thanks for the patch & great change log, just a few comments.
Hi Michael,
Thank you for the suggestions. I will roll them into v2 unless otherwise
noted below.
>
> Michael Roth writes:
> > On a 2-socket Wi
an for 6 hours (so far) without
triggering any lock-ups.
Cc: Paul Mackerras
Cc: Nicholas Piggin
Cc: kvm-...@vger.kernel.org
Signed-off-by: Michael Roth
---
arch/powerpc/include/asm/kvm_ppc.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/include/asm/kvm_ppc.h
b/arch/powerpc/in
Quoting Daniel Borkmann (2018-12-10 08:26:31)
> On 12/07/2018 04:36 PM, Michael Roth wrote:
> > Quoting Michael Ellerman (2018-12-07 06:31:13)
> >> Michael Roth writes:
> >>
> >>> Commit ede95a63b5 introduced a bpf_jit_limit tuneable to limit BPF
> >&g
Quoting Michael Ellerman (2018-12-07 06:31:13)
> Michael Roth writes:
>
> > Commit ede95a63b5 introduced a bpf_jit_limit tuneable to limit BPF
> > JIT allocations. At compile time it defaults to PAGE_SIZE * 4,
> > and is adjusted again at init time if
")
Cc: linuxppc-...@ozlabs.org
Cc: Daniel Borkmann
Cc: Sandipan Das
Cc: Alexei Starovoitov
Signed-off-by: Michael Roth
---
kernel/bpf/core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/kernel/bpf/core.c b/kernel/bpf/core.c
index b1a3545d0ec8..55de4746cdfd 100644
--- a/
Quoting Sandipan Das (2018-12-06 03:27:32)
> When using a large page size, the default value of the bpf_jit_limit
> knob becomes invalid and users are not able to run unprivileged bpf
> programs.
>
> The bpf_jit_limit knob is represented internally as a 32-bit signed
> integer because of which
DAR 772f9539 DSISR 4200
Fix this by setting vcpu->arch.hcall_needed = 0 to indicate completion
of H_ENTER_NESTED before we exit to L0 userspace.
Cc: linuxppc-...@ozlabs.org
Cc: David Gibson
Cc: Paul Mackerras
Cc: Suraj Jitindar Singh
Signed-off-by: Michael Roth
---
arch/powerpc
only need to advertise it via CAS and do not need a corresponding
FW_FEATURE_* value to test for.
Cc: Michael Ellerman <m...@ellerman.id.au>
Cc: Nathan Fontenot <nf...@linux.vnet.ibm.com>
Cc: David Gibson <da...@gibson.dropbear.id.au>
Signed-off-by: Michael Roth <mdr...@linux.vnet.ibm
Quoting Nathan Fontenot (2016-10-18 12:21:06)
> From: Sahil Mehta
>
> Indexed-count remove for memory hotplug guarantees that a contiguous block
> of lmbs beginning at a specified will be unassigned (NOT
> that lmbs will be removed). Because of Qemu's per-DIMM memory
>
Quoting Sahil Mehta (2016-08-01 12:23:16)
> Indexed-count remove for memory hotplug guarantees that a contiguous block
> of lmbs beginning at a specified will be unassigned (NOT
> that lmbs will be removed). Because of Qemu's per-DIMM memory
> management, the removal of a contiguous block of
27 matches
Mail list logo