Re: [PATCH v10 1/9] powerpc: detect the secure boot mode of the system

On 10/30/19 10:31 PM, Mimi Zohar wrote: > From: Nayna Jain > > This patch defines a function to detect the secure boot state of a > PowerNV system. > > The PPC_SECURE_BOOT config represents the base enablement of secure boot > for powerpc. > > Signed-off-by: Nayna Jain > --- > arch/powerpc/Kc

[PATCH v6 0/4] powerpc: expose secure variables to the kernel and userspace

In order to verify the OS kernel on PowerNV systems, secure boot requires X.509 certificates trusted by the platform. These are stored in secure variables controlled by OPAL, called OPAL secure variables. In order to enable users to manage the keys, the secure variables need to be exposed to usersp

[PATCH v6 1/4] powerpc/powernv: Add OPAL API interface to access secure variable

From: Nayna Jain The X.509 certificates trusted by the platform and required to secure boot the OS kernel are wrapped in secure variables, which are controlled by OPAL. This patch adds firmware/kernel interface to read and write OPAL secure variables based on the unique key. This support can be

[PATCH v6 2/4] powerpc: expose secure variables to userspace via sysfs

From: Nayna Jain PowerNV secure variables, which store the keys used for OS kernel verification, are managed by the firmware. These secure variables need to be accessed by the userspace for addition/deletion of the certificates. This patch adds the sysfs interface to expose secure variables for

[PATCH v6 3/4] x86/efi: move common keyring handler functions to new file

From: Nayna Jain The handlers to add the keys to the .platform keyring and blacklisted hashes to the .blacklist keyring is common for both the uefi and powerpc mechanisms of loading the keys/hashes from the firmware. This patch moves the common code from load_uefi.c to keyring_handler.c Signed-

[PATCH v6 4/4] powerpc: load firmware trusted keys/hashes into kernel keyring

From: Nayna Jain The keys used to verify the Host OS kernel are managed by firmware as secure variables. This patch loads the verification keys into the .platform keyring and revocation hashes into .blacklist keyring. This enables verification and loading of the kernels signed by the boot time ke

Re: [PATCH v2 3/4] Documentation/ABI: mark /sys/kernel/fadump_* sysfs files deprecated

On 10/21/19 1:11 PM, Hari Bathini wrote: > > > On 18/10/19 6:35 PM, Sourabh Jain wrote: >> The /sys/kernel/fadump_* sysfs files are replicated under > > [...] > >> +Note: The following FADump sysfs files are deprecated. >> + >> +Deprecated Alternative >> + >> --

[PATCH v15 0/9] open: introduce openat2(2) syscall

This patchset is being developed here: Patch changelog: v15: * Fix code style for LOOKUP_IN_ROOT handling in path_init(). [Linus Torvalds] * Split out patches for each individual LOOKUP flag. * Reword commit messages to give more backg

[PATCH v15 1/9] namei: LOOKUP_NO_SYMLINKS: block symlink resolution

/* Background. */ Userspace cannot easily resolve a path without resolving symlinks, and would have to manually resolve each path component with O_PATH and O_NOFOLLOW. This is clearly inefficient, and can be fairly easy to screw up (resulting in possible security bugs). Linus has mentioned that Git

[PATCH v15 2/9] namei: LOOKUP_NO_MAGICLINKS: block magic-link resolution

/* Background. */ There has always been a special class of symlink-like objects in procfs (and a few other pseudo-filesystems) which allow for non-lexical resolution of paths using nd_jump_link(). These "magic-links" do not follow traditional mount namespace boundaries, and have been used consisten

[PATCH v15 3/9] namei: LOOKUP_NO_XDEV: block mountpoint crossing

/* Background. */ The need to contain path operations within a mountpoint has been a long-standing usecase that userspace has historically implemented manually with liberal usage of stat(). find, rsync, tar and many other programs implement these semantics -- but it'd be much simpler to have a fool

[PATCH v15 4/9] namei: LOOKUP_BENEATH: O_BENEATH-like scoped resolution

/* Background. */ There are many circumstances when userspace wants to resolve a path and ensure that it doesn't go outside of a particular root directory during resolution. Obvious examples include archive extraction tools, as well as other security-conscious userspace programs. FreeBSD spun out O

[PATCH v15 5/9] namei: LOOKUP_IN_ROOT: chroot-like scoped resolution

/* Background. */ Container runtimes or other administrative management processes will often interact with root filesystems while in the host mount namespace, because the cost of doing a chroot(2) on every operation is too prohibitive (especially in Go, which cannot safely use vfork). However, a ma

[PATCH v15 6/9] namei: LOOKUP_{IN_ROOT, BENEATH}: permit limited ".." resolution

Allow LOOKUP_BENEATH and LOOKUP_IN_ROOT to safely permit ".." resolution (in the case of LOOKUP_BENEATH the resolution will still fail if ".." resolution would resolve a path outside of the root -- while LOOKUP_IN_ROOT will chroot(2)-style scope it). Magic-link jumps are still disallowed entirely[*

[PATCH v15 8/9] selftests: add openat2(2) selftests

Test all of the various openat2(2) flags. A small stress-test of a symlink-rename attack is included to show that the protections against ".."-based attacks are sufficient. The main things these self-tests are enforcing are: * The struct+usize ABI for openat2(2) and copy_struct_from_user() to

[PATCH v15 7/9] open: introduce openat2(2) syscall

/* Background. */ For a very long time, extending openat(2) with new features has been incredibly frustrating. This stems from the fact that openat(2) is possibly the most famous counter-example to the mantra "don't silently accept garbage from userspace" -- it doesn't check whether unknown flags a

[PATCH v15 9/9] Documentation: path-lookup: mention LOOKUP_MAGICLINK_JUMPED

Now that we have a special flag to signify magic-link jumps, mention it within the path-lookup docs. And now that "magic link" is the correct term for nd_jump_link()-style symlinks, clean up references to this type of "symlink". Signed-off-by: Aleksa Sarai --- Documentation/filesystems/path-look

[tip: x86/build] x86/mm: Report actual image regions in /proc/iomem

The following commit has been merged into the x86/build branch of tip: Commit-ID: a329975491aafcb1fb6e2fad0de22cae5c16154f Gitweb: https://git.kernel.org/tip/a329975491aafcb1fb6e2fad0de22cae5c16154f Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:50 -07:00 Committer:

[tip: x86/build] x86/vmlinux: Move EXCEPTION_TABLE to RO_DATA segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: f0d7ee17d57c7a8510518a1e60366d053e2f3ff5 Gitweb: https://git.kernel.org/tip/f0d7ee17d57c7a8510518a1e60366d053e2f3ff5 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:38 -07:00 Committer:

[tip: x86/build] vmlinux.lds.h: Move NOTES into RO_DATA

The following commit has been merged into the x86/build branch of tip: Commit-ID: eaf937075c9a42eb8ba51eb3050773d7205d3595 Gitweb: https://git.kernel.org/tip/eaf937075c9a42eb8ba51eb3050773d7205d3595 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:32 -07:00 Committer:

[tip: x86/build] vmlinux.lds.h: Allow EXCEPTION_TABLE to live in RO_DATA

The following commit has been merged into the x86/build branch of tip: Commit-ID: b8c2f776164c8f74ac31c5e370ca3f029be0aa19 Gitweb: https://git.kernel.org/tip/b8c2f776164c8f74ac31c5e370ca3f029be0aa19 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:36 -07:00 Committer:

[tip: x86/build] microblaze: Move EXCEPTION_TABLE to RO_DATA segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: 3bda6f37a7949c803b84cf27e11a3995d900a179 Gitweb: https://git.kernel.org/tip/3bda6f37a7949c803b84cf27e11a3995d900a179 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:44 -07:00 Committer:

[tip: x86/build] vmlinux.lds.h: Replace RO_DATA_SECTION with RO_DATA

The following commit has been merged into the x86/build branch of tip: Commit-ID: 93240b327929ff03c1878ea8badc5c6bd86f053f Gitweb: https://git.kernel.org/tip/93240b327929ff03c1878ea8badc5c6bd86f053f Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:34 -07:00 Committer:

[tip: x86/build] ia64: Rename PT_LOAD identifier "code" to "text"

The following commit has been merged into the x86/build branch of tip: Commit-ID: 430c6b2647e215c4129f36646ad28a725996b410 Gitweb: https://git.kernel.org/tip/430c6b2647e215c4129f36646ad28a725996b410 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:27 -07:00 Committer:

[tip: x86/build] vmlinux.lds.h: Replace RW_DATA_SECTION with RW_DATA

The following commit has been merged into the x86/build branch of tip: Commit-ID: c9174047b48d700a785b633319dd7d27288b86be Gitweb: https://git.kernel.org/tip/c9174047b48d700a785b633319dd7d27288b86be Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:35 -07:00 Committer:

[tip: x86/build] powerpc: Rename "notes" PT_NOTE to "note"

The following commit has been merged into the x86/build branch of tip: Commit-ID: ec556271bbb33809b73cdb238f8cb357345908e8 Gitweb: https://git.kernel.org/tip/ec556271bbb33809b73cdb238f8cb357345908e8 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:23 -07:00 Committer:

[tip: x86/build] powerpc: Rename PT_LOAD identifier "kernel" to "text"

The following commit has been merged into the x86/build branch of tip: Commit-ID: af0f3e9e205c3d1bad91ad83e06bfd04df9712b2 Gitweb: https://git.kernel.org/tip/af0f3e9e205c3d1bad91ad83e06bfd04df9712b2 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:25 -07:00 Committer:

[tip: x86/build] alpha: Rename PT_LOAD identifier "kernel" to "text"

The following commit has been merged into the x86/build branch of tip: Commit-ID: 65182e6e36195fbf9340808ac4a00d1c146bc05c Gitweb: https://git.kernel.org/tip/65182e6e36195fbf9340808ac4a00d1c146bc05c Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:26 -07:00 Committer:

[tip: x86/build] powerpc: Remove PT_NOTE workaround

The following commit has been merged into the x86/build branch of tip: Commit-ID: 6fc4000656a10fb679ab6566dcd516ee672f1706 Gitweb: https://git.kernel.org/tip/6fc4000656a10fb679ab6566dcd516ee672f1706 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:24 -07:00 Committer:

[tip: x86/build] vmlinux.lds.h: Provide EMIT_PT_NOTE to indicate export of .notes

The following commit has been merged into the x86/build branch of tip: Commit-ID: 441110a547f86a2fd0c40bf04b274853622c53cc Gitweb: https://git.kernel.org/tip/441110a547f86a2fd0c40bf04b274853622c53cc Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:30 -07:00 Committer:

[tip: x86/build] vmlinux.lds.h: Move Program Header restoration into NOTES macro

The following commit has been merged into the x86/build branch of tip: Commit-ID: fbe6a8e618a2d70621cff277e24f6eb338d3d149 Gitweb: https://git.kernel.org/tip/fbe6a8e618a2d70621cff277e24f6eb338d3d149 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:31 -07:00 Committer:

Re: [PATCH 09/19] drm/via: set FOLL_PIN via pin_user_pages_fast()

On Mon, Nov 04, 2019 at 11:20:38AM -0800, John Hubbard wrote: > On 11/4/19 10:10 AM, Daniel Vetter wrote: > > On Thu, Oct 31, 2019 at 04:36:28PM -0700, Ira Weiny wrote: > >> On Wed, Oct 30, 2019 at 03:49:20PM -0700, John Hubbard wrote: > >>> Convert drm/via to use the new pin_user_pages_fast() call

[tip: x86/build] s390: Move RO_DATA into "text" PT_LOAD Program Header

The following commit has been merged into the x86/build branch of tip: Commit-ID: 6434efbd9aefa3786b446c8e4745d1f49d2983b4 Gitweb: https://git.kernel.org/tip/6434efbd9aefa3786b446c8e4745d1f49d2983b4 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:28 -07:00 Committer:

[tip: x86/build] powerpc: Move EXCEPTION_TABLE to RO_DATA segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: 4e9e559a0385930649c1c9cad703d475ee030206 Gitweb: https://git.kernel.org/tip/4e9e559a0385930649c1c9cad703d475ee030206 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:46 -07:00 Committer:

[tip: x86/build] x86/vmlinux: Use INT3 instead of NOP for linker fill bytes

The following commit has been merged into the x86/build branch of tip: Commit-ID: 7705dc8557973d8ad8f10840f61d8ec805695e9e Gitweb: https://git.kernel.org/tip/7705dc8557973d8ad8f10840f61d8ec805695e9e Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:51 -07:00 Committer:

[tip: x86/build] x86/vmlinux: Actually use _etext for the end of the text segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: b907693883fdcff5b492cf0cd02a0e264623055e Gitweb: https://git.kernel.org/tip/b907693883fdcff5b492cf0cd02a0e264623055e Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:37 -07:00 Committer:

[tip: x86/build] x86/mm: Report which part of kernel image is freed

The following commit has been merged into the x86/build branch of tip: Commit-ID: 5494c3a6a0b965906ffdcb620d94079ea4cb69ea Gitweb: https://git.kernel.org/tip/5494c3a6a0b965906ffdcb620d94079ea4cb69ea Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:49 -07:00 Committer:

[tip: x86/build] parisc: Move EXCEPTION_TABLE to RO_DATA segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: 6e85e23ef2d004def8e1acd36eb155411499b7cc Gitweb: https://git.kernel.org/tip/6e85e23ef2d004def8e1acd36eb155411499b7cc Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:45 -07:00 Committer:

[tip: x86/build] c6x: Move EXCEPTION_TABLE to RO_DATA segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: 1e51cd538809112a6ac702a48e9719a75152c902 Gitweb: https://git.kernel.org/tip/1e51cd538809112a6ac702a48e9719a75152c902 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:41 -07:00 Committer:

[tip: x86/build] alpha: Move EXCEPTION_TABLE to RO_DATA segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: 172c8b85dccf331826deda9ef6d7e75fa4f2b3e2 Gitweb: https://git.kernel.org/tip/172c8b85dccf331826deda9ef6d7e75fa4f2b3e2 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:39 -07:00 Committer:

[tip: x86/build] arm64: Move EXCEPTION_TABLE to RO_DATA segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: 19f6bc32c6f4216e099963f416de91eba7ca1430 Gitweb: https://git.kernel.org/tip/19f6bc32c6f4216e099963f416de91eba7ca1430 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:40 -07:00 Committer:

[tip: x86/build] vmlinux.lds.h: Replace RODATA with RO_DATA

The following commit has been merged into the x86/build branch of tip: Commit-ID: c82318254d15e5f83c75f60aedf2bb9eb408308f Gitweb: https://git.kernel.org/tip/c82318254d15e5f83c75f60aedf2bb9eb408308f Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:33 -07:00 Committer:

[tip: x86/build] x86/mm: Remove redundant address-of operators on addresses

The following commit has been merged into the x86/build branch of tip: Commit-ID: 2d0004d19829c84aaf2c7d48b5e2892d548970b6 Gitweb: https://git.kernel.org/tip/2d0004d19829c84aaf2c7d48b5e2892d548970b6 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:48 -07:00 Committer:

[tip: x86/build] ia64: Move EXCEPTION_TABLE to RO_DATA segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: 9b30e704dd0d9ef9d99c7f88712318840cc8a338 Gitweb: https://git.kernel.org/tip/9b30e704dd0d9ef9d99c7f88712318840cc8a338 Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:43 -07:00 Committer:

[tip: x86/build] xtensa: Move EXCEPTION_TABLE to RO_DATA segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: 94174c9b71c62a0e1a4364c2594e1422ba8fffcd Gitweb: https://git.kernel.org/tip/94174c9b71c62a0e1a4364c2594e1422ba8fffcd Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:47 -07:00 Committer:

[tip: x86/build] x86/vmlinux: Restore "text" Program Header with dummy section

The following commit has been merged into the x86/build branch of tip: Commit-ID: 7a42d41d9dc2829bdf589db855ce3f948de2da6b Gitweb: https://git.kernel.org/tip/7a42d41d9dc2829bdf589db855ce3f948de2da6b Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:29 -07:00 Committer:

[tip: x86/build] h8300: Move EXCEPTION_TABLE to RO_DATA segment

The following commit has been merged into the x86/build branch of tip: Commit-ID: 380e57e2d41e9631132beccac30058228dfd376f Gitweb: https://git.kernel.org/tip/380e57e2d41e9631132beccac30058228dfd376f Author:Kees Cook AuthorDate:Tue, 29 Oct 2019 14:13:42 -07:00 Committer:

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On 05.11.19 05:38, Dan Williams wrote: On Thu, Oct 24, 2019 at 5:11 AM David Hildenbrand wrote: Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. KVM has this weird use case that you can map anything from /dev/mem into the guest. pfn_valid() is not a reliable ch

Re: [PATCH v1 01/10] mm/memory_hotplug: Don't allow to online/offline memory blocks with holes

On 05.11.19 02:30, Dan Williams wrote: On Thu, Oct 24, 2019 at 5:10 AM David Hildenbrand wrote: Our onlining/offlining code is unnecessarily complicated. Only memory blocks added during boot can have holes (a range that is not IORESOURCE_SYSTEM_RAM). Hotplugged memory never has holes (e.g., se

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On 05.11.19 10:17, David Hildenbrand wrote: On 05.11.19 05:38, Dan Williams wrote: On Thu, Oct 24, 2019 at 5:11 AM David Hildenbrand wrote: Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. KVM has this weird use case that you can map anything from /dev/mem int

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On 05.11.19 10:49, David Hildenbrand wrote: On 05.11.19 10:17, David Hildenbrand wrote: On 05.11.19 05:38, Dan Williams wrote: On Thu, Oct 24, 2019 at 5:11 AM David Hildenbrand wrote: Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. KVM has this weird use cas

Re: [PATCH v1 09/10] mm/memory_hotplug: Don't mark pages PG_reserved when initializing the memmap

On 04.11.19 23:44, Boris Ostrovsky wrote: On 10/24/19 8:09 AM, David Hildenbrand wrote: diff --git a/drivers/xen/balloon.c b/drivers/xen/balloon.c index 4f2e78a5e4db..af69f057913a 100644 --- a/drivers/xen/balloon.c +++ b/drivers/xen/balloon.c @@ -374,6 +374,13 @@ static void xen_online_page(stru

[Bug 205201] Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M

https://bugzilla.kernel.org/show_bug.cgi?id=205201 Christophe Leroy (christophe.le...@c-s.fr) changed: What|Removed |Added CC||christophe.le

Re: [PATCH v1 02/10] KVM: x86/mmu: Prepare kvm_is_mmio_pfn() for PG_reserved changes

On 05.11.19 02:37, Dan Williams wrote: On Thu, Oct 24, 2019 at 5:10 AM David Hildenbrand wrote: Right now, ZONE_DEVICE memory is always set PG_reserved. We want to change that. KVM has this weird use case that you can map anything from /dev/mem into the guest. pfn_valid() is not a reliable ch

Re: [PATCH v2 05/18] mm/gup: introduce pin_user_pages*() and FOLL_PIN

On Sun, Nov 03, 2019 at 01:18:00PM -0800, John Hubbard wrote: > Introduce pin_user_pages*() variations of get_user_pages*() calls, > and also pin_longterm_pages*() variations. > > These variants all set FOLL_PIN, which is also introduced, and > thoroughly documented. > > The pin_longterm*() varia

[Bug 205201] Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M

https://bugzilla.kernel.org/show_bug.cgi?id=205201 --- Comment #4 from Christian Zigotzky (chzigot...@xenosoft.de) --- Yes, I can. Could you please post the correct commits for starting bisect? git bisect start git bisect good ? git bisect bad ? Thanks -- You are receiving this mail because:

[Bug 205201] Booting halts if Dawicontrol DC-2976 UW SCSI board installed, unless RAM size limited to 3500M

https://bugzilla.kernel.org/show_bug.cgi?id=205201 --- Comment #5 from Christophe Leroy (christophe.le...@c-s.fr) --- I guess: git bisect bad 8d6973327 git bisect good v4.20 -- You are receiving this mail because: You are watching the assignee of the bug.

[PATCH 0/9] Fixes and Enablement of ibm,drc-info property

There was a previous effort to add support for the PAPR architected ibm,drc-info property. This property provides a more memory compact representation of a paritions Dynamic Reconfig Connectors (DRC). These can otherwise be thought of as currently partitioned, or available but yet to be partitioned

[PATCH 5/9] PCI: rpaphp: Don't rely on firmware feature to imply drc-info support

In the event that the partition is migrated to a platform with older firmware that doesn't support the ibm,drc-info property the device tree is modified to remove the ibm,drc-info property and replace it with the older style ibm,drc-* properties for types, names, indexes, and power-domains. One of

[PATCH 3/9] powerpc/pseries: Add cpu DLPAR support for drc-info property

From: Tyrel Datwyler Older firmwares provided information about Dynamic Reconfig Connectors (DRC) through several device tree properties, namely ibm,drc-types, ibm,drc-indexes, ibm,drc-names, and ibm,drc-power-domains. New firmwares have the ability to present this same information in a much cond

[PATCH 1/9] powerpc/pseries: Fix bad drc_index_start value parsing of drc-info entry

The ibm,drc-info property is an array property that contains drc-info entries such that each entry is made up of 2 string encoded elements followed by 5 int encoded elements. The of_read_drc_info_cell() helper contains comments that correctly name the expected elements and their encoding. However,

[PATCH 6/9] PCI: rpaphp: Add drc-info support for hotplug slot registration

Split physical PCI slot registration scanning into seperate routines that support the old ibm,drc-* properties and one that supports the new compressed ibm,drc-info property. Signed-off-by: Tyrel Datwyler --- drivers/pci/hotplug/rpaphp_core.c | 89 ++- 1 file

[PATCH 4/9] PCI: rpaphp: Fix up pointer to first drc-info entry

The first entry of the ibm,drc-info property is an int encoded count of the number of drc-info entries that follow. The "value" pointer returned by of_prop_next_u32() is still pointing at the this value when we call of_read_drc_info_cell(), but the helper function expects that value to be pointing

[PATCH 7/9] PCI: rpaphp: annotate and correctly byte swap DRC properties

The device tree is in big endian format and any properties directly retrieved using OF helpers that don't explicitly byte swap should be annotated. In particular there are several places where we grab the opaque property value for the old ibm,drc-* properties and the ibm,my-drc-index property. Fix

[PATCH 9/9] powerpc/pseries: Enable support for ibm, drc-info property

Advertise client support for the PAPR architected ibm,drc-info device tree property during CAS handshake. Signed-off-by: Tyrel Datwyler --- arch/powerpc/kernel/prom_init.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/pr

[PATCH 8/9] PCI: rpaphp: Correctly match ibm, my-drc-index to drc-name when using drc-info

The newer ibm,drc-info property is a condensed description of the old ibm,drc-* properties (ie. names, types, indexes, and power-domains). When matching a drc-index to a drc-name we need to verify that the index is within the start and last drc-index range and map it to a drc-name using the drc-nam

[PATCH 2/9] powerpc/pseries: Fix drc-info mappings of logical cpus to drc-index

There are a couple subtle errors in the mapping between cpu-ids and a cpus associated drc-index when using the new ibm,drc-info property. The first is that while drc-info may have been a supported firmware feature at boot it is possible we have migrated to a CEC with older firmware that doesn't su

Re: [PATCH 3/9] powerpc/pseries: Add cpu DLPAR support for drc-info property

On 11/5/19 9:24 AM, Tyrel Datwyler wrote: From: Tyrel Datwyler Older firmwares provided information about Dynamic Reconfig Connectors (DRC) through several device tree properties, namely ibm,drc-types, ibm,drc-indexes, ibm,drc-names, and ibm,drc-power-domains. New firmwares have the ability t

Re: [PATCH v2 3/4] Documentation/ABI: mark /sys/kernel/fadump_* sysfs files deprecated

On 05/11/19 2:24 PM, Sourabh Jain wrote: > > > On 10/21/19 1:11 PM, Hari Bathini wrote: >> >> >> On 18/10/19 6:35 PM, Sourabh Jain wrote: >>> The /sys/kernel/fadump_* sysfs files are replicated under >> >> [...] >> >>> +Note: The following FADump sysfs files are deprecated. >>> + >>> +Depr

Re: [PATCH 0/9] Fixes and Enablement of ibm,drc-info property

On 11/5/19 9:24 AM, Tyrel Datwyler wrote: Hi, just pointing out a few typos... There was a previous effort to add support for the PAPR architected ibm,drc-info property. This property provides a more memory compact representation of a paritions Dynamic Reconfig s/paritions/partition's Connec

Re: [PATCH 09/19] drm/via: set FOLL_PIN via pin_user_pages_fast()

On 11/5/19 1:49 AM, Daniel Vetter wrote: > On Mon, Nov 04, 2019 at 11:20:38AM -0800, John Hubbard wrote: >> On 11/4/19 10:10 AM, Daniel Vetter wrote: >>> On Thu, Oct 31, 2019 at 04:36:28PM -0700, Ira Weiny wrote: On Wed, Oct 30, 2019 at 03:49:20PM -0700, John Hubbard wrote: > Convert drm/v

Re: [PATCH v2 05/18] mm/gup: introduce pin_user_pages*() and FOLL_PIN

On 11/5/19 5:10 AM, Mike Rapoport wrote: ... >> --- >> Documentation/vm/index.rst | 1 + >> Documentation/vm/pin_user_pages.rst | 212 ++ > > I think it belongs to Documentation/core-api. Done: diff --git a/Documentation/core-api/index.rst b/Documentation/core-api/

Re: [PATCH V8] mm/debug: Add tests validating architecture page table helpers

On Mon, 28 Oct 2019 10:59:22 +0530 Anshuman Khandual wrote: > This adds tests which will validate architecture page table helpers and > other accessors in their compliance with expected generic MM semantics. > This will help various architectures in validating changes to existing > page table hel

Re: [PATCH V8] mm/debug: Add tests validating architecture page table helpers

On 10/28/2019 10:59 AM, Anshuman Khandual wrote: > This adds tests which will validate architecture page table helpers and > other accessors in their compliance with expected generic MM semantics. > This will help various architectures in validating changes to existing > page table helpers or addit

Re: [PATCH v1 09/10] mm/memory_hotplug: Don't mark pages PG_reserved when initializing the memmap

On 11/5/19 5:18 AM, David Hildenbrand wrote: > On 04.11.19 23:44, Boris Ostrovsky wrote: >> On 10/24/19 8:09 AM, David Hildenbrand wrote: >>> diff --git a/drivers/xen/balloon.c b/drivers/xen/balloon.c >>> index 4f2e78a5e4db..af69f057913a 100644 >>> --- a/drivers/xen/balloon.c >>> +++ b/drivers/xen/

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On Tue, Nov 05, 2019 at 11:02:46AM +0100, David Hildenbrand wrote: > On 05.11.19 10:49, David Hildenbrand wrote: > >On 05.11.19 10:17, David Hildenbrand wrote: > >>On 05.11.19 05:38, Dan Williams wrote: > >>>On Thu, Oct 24, 2019 at 5:11 AM David Hildenbrand wrote: > > Right now, ZONE_DEVI

Re: [PATCH v6 1/3] dt-bindings: pci: layerscape-pci: add compatible strings "fsl,ls1028a-pcie"

On Mon, Sep 02, 2019 at 11:43:17AM +0800, Xiaowei Bao wrote: > Add the PCIe compatible string for LS1028A > > Signed-off-by: Xiaowei Bao > Signed-off-by: Hou Zhiqiang > Reviewed-by: Rob Herring > --- Reviewed-by: Andrew Murray > v2: > - No change. > v3: > - No change. > v4: > - No change.

Re: [PATCH v6 3/3] PCI: layerscape: Add LS1028a support

On Mon, Sep 02, 2019 at 11:43:19AM +0800, Xiaowei Bao wrote: > Add support for the LS1028a PCIe controller. > > Signed-off-by: Xiaowei Bao > Signed-off-by: Hou Zhiqiang > --- > v2: > - No change. > v3: > - Reuse the ls2088 driver data structurt. > v4: > - No change. > v5: > - No change. > v6

Re: [PATCH V8] mm/debug: Add tests validating architecture page table helpers

On 10/28/2019 10:59 AM, Anshuman Khandual wrote: > This adds tests which will validate architecture page table helpers and > other accessors in their compliance with expected generic MM semantics. > This will help various architectures in validating changes to existing > page table helpers or ad

Re: [PATCH v6 3/3] PCI: layerscape: Add LS1028a support

On Mon, Sep 02, 2019 at 11:43:19AM +0800, Xiaowei Bao wrote: > Add support for the LS1028a PCIe controller. > > Signed-off-by: Xiaowei Bao > Signed-off-by: Hou Zhiqiang > --- > v2: > - No change. > v3: > - Reuse the ls2088 driver data structurt. > v4: > - No change. > v5: > - No change. > v6

Re: [PATCH v2 07/10] PCI: layerscape: Modify the MSIX to the doorbell way

On Thu, Aug 29, 2019 at 10:43:18AM +0530, Kishon Vijay Abraham I wrote: > Gustavo, > > On 27/08/19 6:55 PM, Andrew Murray wrote: > > On Sat, Aug 24, 2019 at 12:08:40AM +, Xiaowei Bao wrote: > >> > >> > >>> -Original Message- > >>> From: Andrew Murray > >>> Sent: 2019年8月23日 21:58 > >>>

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

I think I know what's going wrong: Pages that are pinned via gfn_to_pfn() and friends take a references, however are often released via kvm_release_pfn_clean()/kvm_release_pfn_dirty()/kvm_release_page_clean()... E.g., in arch/x86/kvm/x86.c:reexecute_instruction() ... pfn = gfn_to_pfn(vcpu->kvm

Re: [PATCH V2 1/2] ASoC: dt-bindings: fsl_asrc: add compatible string for imx8qm

On Wed, Oct 30, 2019 at 07:41:26PM +0800, Shengjiu Wang wrote: > In order to support the two asrc modules in imx8qm, we need to > add compatible string "fsl,imx8qm-asrc0" and "fsl,imx8qm-asrc1" Are the blocks different in some way? If not, why do you need to distinguish them? > Signed-off-by: Sh

Re: [PATCH V8] mm/debug: Add tests validating architecture page table helpers

Hi Anshuman, On 11/4/19 4:00 PM, Anshuman Khandual wrote: > On 10/28/2019 10:59 AM, Anshuman Khandual wrote: >> This adds tests which will validate architecture page table helpers and >> other accessors in their compliance with expected generic MM semantics. >> This will help various architectures

Re: [PATCH v3 35/36] net/wan: make FSL_UCC_HDLC explicitly depend on PPC32

On 04/11/2019 21.56, Li Yang wrote: >> No, this patch cannot be dropped. Please see the kbuild complaints for >> v2,23/23 about use of IS_ERR_VALUE on not-sizeof(long) entities. I see >> kbuild has complained about the same thing for v3 since apparently the >> same thing appears in ucc_slow.c. So

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On Tue, Nov 05, 2019 at 09:30:53PM +0100, David Hildenbrand wrote: > >>>I think I know what's going wrong: > >>> > >>>Pages that are pinned via gfn_to_pfn() and friends take a references, > >>>however are often released via > >>>kvm_release_pfn_clean()/kvm_release_pfn_dirty()/kvm_release_page_clean

[PATCH v10a 1/9] powerpc: detect the secure boot mode of the system

From: Nayna Jain This patch defines a function to detect the secure boot state of a PowerNV system. The PPC_SECURE_BOOT config represents the base enablement of secure boot for powerpc. Signed-off-by: Nayna Jain Signed-off-by: Eric Richter --- v10a: - moved get_ppc_fw_sb_node to this patch -

[PATCH v10a 3/9] powerpc: detect the trusted boot state of the system

From: Nayna Jain While secure boot permits only properly verified signed kernels to be booted, trusted boot calculates the file hash of the kernel image and stores the measurement prior to boot, that can be subsequently compared against good known values via attestation services. This patch read

Re: [PATCH v3 35/36] net/wan: make FSL_UCC_HDLC explicitly depend on PPC32

On Tue, Nov 5, 2019 at 4:47 PM Rasmus Villemoes wrote: > > On 04/11/2019 21.56, Li Yang wrote: > > >> No, this patch cannot be dropped. Please see the kbuild complaints for > >> v2,23/23 about use of IS_ERR_VALUE on not-sizeof(long) entities. I see > >> kbuild has complained about the same thing f

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On Tue, Nov 5, 2019 at 12:31 PM David Hildenbrand wrote: > > >>> I think I know what's going wrong: > >>> > >>> Pages that are pinned via gfn_to_pfn() and friends take a references, > >>> however are often released via > >>> kvm_release_pfn_clean()/kvm_release_pfn_dirty()/kvm_release_page_clean().

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On Tue, Nov 05, 2019 at 03:02:40PM -0800, Dan Williams wrote: > On Tue, Nov 5, 2019 at 12:31 PM David Hildenbrand wrote: > > > The scarier code (for me) is transparent_hugepage_adjust() and > > > kvm_mmu_zap_collapsible_spte(), as I don't at all understand the > > > interaction between THP and _PA

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On Tue, Nov 5, 2019 at 3:13 PM Sean Christopherson wrote: > > On Tue, Nov 05, 2019 at 03:02:40PM -0800, Dan Williams wrote: > > On Tue, Nov 5, 2019 at 12:31 PM David Hildenbrand wrote: > > > > The scarier code (for me) is transparent_hugepage_adjust() and > > > > kvm_mmu_zap_collapsible_spte(), a

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On Tue, Nov 05, 2019 at 03:30:00PM -0800, Dan Williams wrote: > On Tue, Nov 5, 2019 at 3:13 PM Sean Christopherson > wrote: > > > > On Tue, Nov 05, 2019 at 03:02:40PM -0800, Dan Williams wrote: > > > On Tue, Nov 5, 2019 at 12:31 PM David Hildenbrand > > > wrote: > > > > > The scarier code (for m

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On Tue, Nov 5, 2019 at 3:30 PM Dan Williams wrote: > > On Tue, Nov 5, 2019 at 3:13 PM Sean Christopherson > wrote: > > > > On Tue, Nov 05, 2019 at 03:02:40PM -0800, Dan Williams wrote: > > > On Tue, Nov 5, 2019 at 12:31 PM David Hildenbrand > > > wrote: > > > > > The scarier code (for me) is tr

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On Tue, Nov 05, 2019 at 03:43:29PM -0800, Dan Williams wrote: > On Tue, Nov 5, 2019 at 3:30 PM Dan Williams wrote: > > > > On Tue, Nov 5, 2019 at 3:13 PM Sean Christopherson > > wrote: > > > > > > On Tue, Nov 05, 2019 at 03:02:40PM -0800, Dan Williams wrote: > > > > On Tue, Nov 5, 2019 at 12:31 P

[RFC PATCH] powerpc/pseries/mobility: notify network peers after migration

After a migration, it is necessary to send a gratuitous ARP from all running interfaces so that the rest of the network is aware of its new location. However, some supported network devices are unaware that they have been migrated. To avoid network interruptions and other unwanted behavior, force a

Re: [PATCH v1 03/10] KVM: Prepare kvm_is_reserved_pfn() for PG_reserved changes

On Tue, Nov 5, 2019 at 4:03 PM Sean Christopherson wrote: > > On Tue, Nov 05, 2019 at 03:43:29PM -0800, Dan Williams wrote: > > On Tue, Nov 5, 2019 at 3:30 PM Dan Williams > > wrote: > > > > > > On Tue, Nov 5, 2019 at 3:13 PM Sean Christopherson > > > wrote: > > > > > > > > On Tue, Nov 05, 2019

RE: [EXT] Re: [PATCH V2 1/2] ASoC: dt-bindings: fsl_asrc: add compatible string for imx8qm

Hi > > On Wed, Oct 30, 2019 at 07:41:26PM +0800, Shengjiu Wang wrote: > > In order to support the two asrc modules in imx8qm, we need to add > > compatible string "fsl,imx8qm-asrc0" and "fsl,imx8qm-asrc1" > > Are the blocks different in some way? > > If not, why do you need to distinguish them?

Re: [RFC v1 1/2] powerpc/pseries/iommu: Share the per-cpu TCE page with the hypervisor.

On 05/11/2019 08:28, Ram Pai wrote: > The hypervisor needs to access the contents of the page holding the TCE > entries while setting up the TCE entries in the IOMMU's TCE table. For > SecureVMs, since this page is encrypted, the hypervisor cannot access > valid entries. Share the page with the

Re: [RFC v1 0/2] Enable IOMMU support for pseries Secure VMs

On 05/11/2019 08:28, Ram Pai wrote: > This patch series enables IOMMU support for pseries Secure VMs. > > > Tested using QEMU command line option: > > "-device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4, > iommu_platform=on,disable-modern=off,disable-legacy=on" > and > > "-device

  1   2   >