linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
 messages from 2020-01-30 11:01:25 to 2020-02-07 11:40:10 UTC [more...]

[PATCH 00/35] KVM: s390: Add support for protected VMs
 2020-02-07 11:39 UTC  (34+ messages)
` [PATCH 01/35] mm:gup/writeback: add callbacks for inaccessible pages
` [PATCH 02/35] KVM: s390/interrupt: do not pin adapter interrupt pages
` [PATCH 03/35] s390/protvirt: introduce host side setup
` [PATCH 04/35] s390/protvirt: add ultravisor initialization
` [PATCH 05/35] s390/mm: provide memory management functions for protected KVM guests
` [PATCH 06/35] s390/mm: add (non)secure page access exceptions handlers
` [PATCH 07/35] KVM: s390: add new variants of UV CALL
` [PATCH 09/35] KVM: s390: protvirt: Add KVM api documentation
` [PATCH 10/35] KVM: s390: protvirt: Secure memory is not mergeable
` [PATCH 11/35] KVM: s390/mm: Make pages accessible before destroying the guest
` [PATCH 12/35] KVM: s390: protvirt: Handle SE notification interceptions
` [PATCH 13/35] KVM: s390: protvirt: Instruction emulation
` [PATCH 14/35] KVM: s390: protvirt: Add interruption injection controls
` [PATCH 15/35] KVM: s390: protvirt: Implement interruption injection
` [PATCH 16/35] KVM: s390: protvirt: Add SCLP interrupt handling
` [PATCH 17/35] KVM: s390: protvirt: Handle spec exception loops
` [PATCH 18/35] KVM: s390: protvirt: Add new gprs location handling
` [PATCH 19/35] KVM: S390: protvirt: Introduce instruction data area bounce buffer
` [PATCH 20/35] KVM: s390: protvirt: handle secure guest prefix pages
` [PATCH 21/35] KVM: s390/mm: handle guest unpin events
` [PATCH 23/35] KVM: s390: protvirt: STSI handling
` [PATCH 24/35] KVM: s390: protvirt: disallow one_reg
` [PATCH 25/35] KVM: s390: protvirt: Only sync fmt4 registers
` [PATCH 26/35] KVM: s390: protvirt: Add program exception injection
` [PATCH 27/35] KVM: s390: protvirt: Add diag 308 subcode 8 - 10 handling
` [PATCH 28/35] KVM: s390: protvirt: UV calls diag308 0, 1
` [PATCH 29/35] KVM: s390: protvirt: Report CPU state to Ultravisor
` [PATCH 30/35] KVM: s390: protvirt: Support cmd 5 operation state
` [PATCH 31/35] KVM: s390: protvirt: Add UV debug trace
` [PATCH 32/35] KVM: s390: protvirt: Mask PSW interrupt bits for interception 104 and 112
` [PATCH 33/35] KVM: s390: protvirt: do not inject interrupts after start
` [PATCH 34/35] KVM: s390: protvirt: Add UV cpu reset calls
` [PATCH 35/35] DOCUMENTATION: Protected virtual machine introduction and IPL

[RFC PATCH v2 0/9] s390x/vfio-ccw: Channel Path Handling
 2020-02-07  9:12 UTC  (11+ messages)
` [RFC PATCH v2 1/9] vfio-ccw: Introduce new helper functions to free/destroy regions
` [RFC PATCH v2 2/9] vfio-ccw: Register a chp_event callback for vfio-ccw
` [RFC PATCH v2 3/9] vfio-ccw: Refactor the unregister of the async regions
` [RFC PATCH v2 4/9] vfio-ccw: Introduce a new schib region
` [RFC PATCH v2 5/9] vfio-ccw: Introduce a new CRW region
` [RFC PATCH v2 6/9] vfio-ccw: Refactor IRQ handlers
` [RFC PATCH v2 7/9] vfio-ccw: Wire up the CRW irq and CRW region
` [RFC PATCH v2 8/9] vfio-ccw: Add trace for CRW event
` [RFC PATCH v2 9/9] vfio-ccw: Remove inline get_schid() routine

[PULL 0/1] one vfio-ccw patch for 5.6
 2020-02-06 17:03 UTC  (2+ messages)
` [PULL 1/1] vfio-ccw: Use the correct style for SPDX License Identifier

[PATCH 0/1] s390: seq_file .next functions should increase position index
 2020-02-06  6:11 UTC  (3+ messages)

[PATCH v6 06/10] mm/memory_hotplug: Poison memmap in remove_pfn_range_from_zone()
 2020-02-05 23:34 UTC  (42+ messages)
` [PATCH v6 07/10] mm/memory_hotplug: We always have a zone in find_(smallest|biggest)_section_pfn
` [PATCH v6 08/10] mm/memory_hotplug: Don't check for "all holes" in shrink_zone_span()
` [PATCH v6 09/10] mm/memory_hotplug: Drop local variables "
` [PATCH v6 10/10] mm/memory_hotplug: Cleanup __remove_pages()

[GIT PULL] s390 patches for the 5.6 merge window #2
 2020-02-05 18:20 UTC  (2+ messages)

[GIT PULL 0/7] KVM: s390: Fixes and cleanups for 5.6
 2020-02-05 15:15 UTC  (9+ messages)
` [GIT PULL 1/7] KVM: s390: ENOTSUPP -> EOPNOTSUPP fixups
` [GIT PULL 2/7] KVM: s390: do not clobber registers during guest reset/store status
` [GIT PULL 3/7] KVM: s390: Cleanup initial cpu reset
` [GIT PULL 4/7] KVM: s390: Add new reset vcpu API
` [GIT PULL 5/7] selftests: KVM: Add fpu and one reg set/get library functions
` [GIT PULL 6/7] selftests: KVM: s390x: Add reset tests
` [GIT PULL 7/7] selftests: KVM: testing the local IRQs resets

[PATCH v2 0/2] microblaze: Enable CMA
 2020-02-04 10:30 UTC  (2+ messages)

[PATCH V12] mm/debug: Add tests validating architecture page table helpers
 2020-02-03 15:48 UTC  (19+ messages)

[kvm-unit-tests PATCH v5 0/7] s390x: smp: Improve smp code and reset checks
 2020-02-03 11:19 UTC  (15+ messages)
` [kvm-unit-tests PATCH v5 1/7] s390x: smp: Cleanup smp.c
` [kvm-unit-tests PATCH v5 2/7] s390x: smp: Fix ecall and emcall report strings
` [kvm-unit-tests PATCH v5 3/7] s390x: Stop the cpu that is executing exit()
` [kvm-unit-tests PATCH v5 4/7] s390x: Add cpu id to interrupt error prints
` [kvm-unit-tests PATCH v5 5/7] s390x: smp: Only use smp_cpu_setup once
` [kvm-unit-tests PATCH v5 6/7] s390x: smp: Rework cpu start and active tracking
` [kvm-unit-tests PATCH v5 7/7] s390x: smp: Wait for cpu setup to finish

[kvms390:protvirtv2 12/42] arch/s390/kvm/interrupt.c:2383:9: error: implicit declaration of function 'uv_convert_to_secure_pinned'; did you mean 'uv_convert_to_secure'?
 2020-02-02  7:40 UTC 

[PULL 00/12] s390x qemu updates 20190930
 2020-01-31 15:03 UTC  (14+ messages)
` [PULL 01/12] MAINTAINERS: Update S390 PCI Maintainer
` [PULL 02/12] s390: PCI: fix IOMMU region init
` [PULL 03/12] s390x: sclp: refactor invalid command check
` [PULL 04/12] s390x: sclp: boundary check
` [PULL 05/12] s390x: sclp: fix error handling for oversize control blocks
` [PULL 06/12] s390x: sclp: Report insufficient SCCB length
` [PULL 07/12] configure: Remove s390 (31-bit mode) from the list of supported CPUs
` [PULL 08/12] kvm: extract kvm_log_clear_one_slot
` [PULL 09/12] kvm: clear dirty bitmaps from all overlapping memslots
` [PULL 10/12] kvm: split too big memory section on several memslots
` [PULL 11/12] s390: do not call memory_region_allocate_system_memory() multiple times
` [PULL 12/12] s390/kvm: split kvm mem slots at 4TB

[PATCH v10 0/6] KVM: s390: Add new reset vcpu API
 2020-01-31 13:59 UTC  (18+ messages)
` [PATCH v10 1/6] KVM: s390: do not clobber registers during guest reset/store status
` [PATCH v10 2/6] KVM: s390: Cleanup initial cpu reset
` [PATCH v10 3/6] KVM: s390: Add new reset vcpu API
` [PATCH v10 4/6] selftests: KVM: Add fpu and one reg set/get library functions
` [PATCH v10 5/6] selftests: KVM: s390x: Add reset tests
` [PATCH v10 6/6] selftests: KVM: testing the local IRQs resets

[PATCH] s390: Cleanup removed IOSCHED_DEADLINE
 2020-01-30 19:25 UTC 

[PATCH v9 0/6] KVM: s390: Add new reset vcpu API
 2020-01-30 16:27 UTC  (21+ messages)
` [PATCH v9 1/6] KVM: s390: do not clobber registers during guest reset/store status
` [PATCH v9 2/6] KVM: s390: Cleanup initial cpu reset
` [PATCH v9 3/6] KVM: s390: Add new reset vcpu API
    ` [PATCH v9] "
` [PATCH v9 4/6] selftests: KVM: Add fpu and one reg set/get library functions
` [PATCH v9 5/6] selftests: KVM: s390x: Add reset tests
` [PATCH v9 6/6] selftests: KVM: testing the local IRQs resets

[PATCH v8 0/4] KVM: s390: Add new reset vcpu API
 2020-01-30 15:04 UTC  (19+ messages)
` [PATCH v8 2/4] selftests: KVM: Add fpu and one reg set/get library functions
` [PATCH v8 3/4] selftests: KVM: s390x: Add reset tests
` [PATCH v8 4/4] selftests: KVM: testing the local IRQs resets

[PATCH v8 1/4] KVM: s390: Add new reset vcpu API
 2020-01-30 12:38 UTC  (14+ messages)
` [PATCH/FIXUP FOR STABLE BEFORE THIS SERIES] KVM: s390: do not clobber user space fpc during guest reset
            ` [PATCH v2] KVM: s390: do not clobber user space registers during guest reset/store status


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).