Tested-by: Steve Wahl
On Thu, Apr 15, 2021 at 02:22:43PM -0700, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> There may be a kernel panic on the Haswell server and the Broadwell
> server, if the snbep_pci2phy_map_init() return error.
>
> The uncore_extra_pci_dev[H
Reviewed-by: Steve Wahl
On Fri, Apr 16, 2021 at 06:10:40PM +0800, Yang Li wrote:
> Kernel test robot throws below warning ->
>
> smatch warnings:
> arch/x86/kernel/apic/x2apic_uv_x.c:111 early_get_pnodeid() warn:
> inconsistent indenting
>
> Reported-by: Abaci Robot
fail
snbep_pci2phy_map_init if BIOS doesn't supply pcibus_to_node
information.
Fixes: 9a7832ce3d92 ("perf/x86/intel/uncore: With > 8 nodes, get pci bus die id
from NUMA info")
Signed-off-by: Steve Wahl
---
arch/x86/events/intel/uncore_snbep.c | 10 +++---
1 file changed, 7 insertions(+
Reviewed-by: Steve Wahl
On Tue, Mar 16, 2021 at 04:57:21PM +0800, Yang Li wrote:
> This fixes the following sparse warnings:
> drivers/misc/sgi-xp/xpc_main.c:210:23: warning: Using plain integer as
> NULL pointer
>
> Reported-by: Abaci Robot
> Signed-off-by: Yang Li
> --
Reviewed-By: Steve Wahl
On Sat, Jan 23, 2021 at 08:00:03AM -0800, t...@redhat.com wrote:
> From: Tom Rix
>
> This change fixes the checkpatch warning described in this commit
> commit cbacb5ab0aa0 ("docs: printk-formats: Stop encouraging use of
> unnecessary %
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 9a7832ce3d920426a36cdd78eda4b3568d4d09e3
Gitweb:
https://git.kernel.org/tip/9a7832ce3d920426a36cdd78eda4b3568d4d09e3
Author:Steve Wahl
AuthorDate:Fri, 08 Jan 2021 09:35:49 -06:00
Committer
The following commit has been merged into the perf/core branch of tip:
Commit-ID: ba9506be4e402ee597b8f41204008b97989b5eef
Gitweb:
https://git.kernel.org/tip/ba9506be4e402ee597b8f41204008b97989b5eef
Author:Steve Wahl
AuthorDate:Fri, 08 Jan 2021 09:35:48 -06:00
Committer
On Tue, Jan 12, 2021 at 04:07:15PM +0100, Peter Zijlstra wrote:
> On Mon, Jan 11, 2021 at 09:45:16AM -0600, Steve Wahl wrote:
> > On Mon, Jan 11, 2021 at 02:00:33PM +0100, Peter Zijlstra wrote:
> > > On Fri, Jan 08, 2021 at 09:35:49AM -0600
On Mon, Jan 11, 2021 at 02:00:33PM +0100, Peter Zijlstra wrote:
> On Fri, Jan 08, 2021 at 09:35:49AM -0600, Steve Wahl wrote:
>
>
> > + /*
> > +* The nodeid and idmap registers only contain enough
> > +* information to handle 8 n
hen there are more than 8 nodes.
Steve Wahl (2):
perf/x86/intel/uncore: Store the logical die id instead of the
physical die id.
perf/x86/intel/uncore: With > 8 nodes, get pci bus die id from NUMA
info
arch/x86/events/intel/uncore.c | 58 +-
arch/x86/events/intel/u
es of NUMA being disabled.
Signed-off-by: Steve Wahl
---
arch/x86/events/intel/uncore_snbep.c | 93 +++-
1 file changed, 65 insertions(+), 28 deletions(-)
diff --git a/arch/x86/events/intel/uncore_snbep.c
b/arch/x86/events/intel/uncore_snbep.c
index 2d7014dc46f6..b79951d
The phys_id isn't really used other than to map to a logical die id.
Calculate the logical die id earlier, and store that instead of the
phys_id.
Signed-off-by: Steve Wahl
---
arch/x86/events/intel/uncore.c | 58 ++--
arch/x86/events/intel/uncore.h
ink the contents in those links provide valuable information about
> cpusets.
> We have documents in Documentation/admin-guide/cgroup/ and man cpuset(7). So
> I think
> we can just remove them.
I agree, I did the archive.org lookup and it appeared that the current
version of most o
Reviewed-by: Steve Wahl
On Thu, Dec 03, 2020 at 09:22:52AM -0600, Mike Travis wrote:
> Fix UV4 Hub Revision adjustment as Hub chip starts with revision 1.
> Incorrectly identifies UV4 as UV4A and UV4A as UV5.
>
> Fixes 647128f1536ef: x86/platform/uv: Update UV MMRs for UV5
>
Reviewed-by: Steve Wahl
On Thu, Nov 19, 2020 at 11:31:51AM +0100, Sebastian Andrzej Siewior wrote:
> From: Thomas Gleixner
>
> The usage of in_interrupt() in xpc_partition_disengaged() is clearly
> intended to avoid canceling the timeout timer when the function is invoked
>
Use sizeof to remove size dependency
> on copy out length. Increase output buffer size by one character just
> in case BIOS sends an 8 character string for archtype.
>
> Fixes: 1e61f5a95f191 (Add and decode Arch Type in UVsystab)
>
> Signed-off-by: Mike Travis
Reviewed-by:
Acked-by: Steve Wahl
On Mon, Nov 09, 2020 at 10:36:53AM +0100, Jiri Slaby wrote:
> Commit 39297dde7390 ("x86/platform/uv: Remove UV BAU TLB Shootdown
> Handler") removed uv_flush_tlb_others. Its declaration was removed also
> from asm/uv/uv.h. But only for the CONFIG_X86_UV
The following commit has been merged into the x86/misc branch of tip:
Commit-ID: 632211cdd6ad0efeef32c53ac731901b4bed3b94
Gitweb:
https://git.kernel.org/tip/632211cdd6ad0efeef32c53ac731901b4bed3b94
Author:Steve Wahl
AuthorDate:Mon, 19 Oct 2020 15:35:33 -05:00
Committer
UV platforms are the only ones who currently use the XP/XPC/XPNET
Driver, so it seems fair HPE should take some responsibility as
maintainers of it; so add Mike Travis and Steve Wahl. Cliff
Whickman's email address is no longer valid, so remove it. Robin Holt
was contacted and wishes to rema
UV platforms are the only ones who currently use the XP/XPC/XPNET
Driver, so it seems fair HPE should take some responsibility as
maintainers of it; so add Mike Travis and Steve Wahl. Cliff
Whickman's email address is no longer valid, so remove it. Robin Holt
was contacted and wishes to rema
The older
> style of one-element or zero-length arrays should no longer be used[2].
I see this has already gone in, so I'm late. But for whatever it's
worth, it's a good change. Thank you.
Reviewed-by: Steve Wahl
--> Steve wahl
> struct uv_rtc_timer_head contains a one-ele
Acked-by: Steve Wahl
On Wed, Sep 16, 2020 at 02:20:39PM -0500, Mike Travis wrote:
> Add Copyrights to those files that have been updated for UV5 changes.
>
> Signed-off-by: Mike Travis
> ---
> arch/x86/include/asm/uv/bios.h | 1 +
> arch/x86/include/asm/uv/uv_hub.h
Acked-by: Steve Wahl
On Wed, Sep 16, 2020 at 02:20:27PM -0500, Mike Travis wrote:
> The Broadcast Assist Unit (BAU) TLB shootdown handler is being rewritten
> to become the UV BAU APIC driver. It is designed to speed up sending
> IPI's to selective CPUs within the system. Remo
Acked-by: Steve Wahl
On Wed, Sep 16, 2020 at 02:20:28PM -0500, Mike Travis wrote:
> UV class systems no longer use System Controller for monitoring of CPU
> activity provided by this driver. Other methods have been developed
> for BIOS and the management controller (BMC). This patc
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: d4f07268d035721dd055ceb0de98ace6ac5f858b
Gitweb:
https://git.kernel.org/tip/d4f07268d035721dd055ceb0de98ace6ac5f858b
Author:Steve Wahl
AuthorDate:Mon, 24 Aug 2020 17:14:39 -05:00
Committer
Add an entry and email addresses for people at HPE who are supporting
linux on the Superdome Flex (a.k.a) UV platform.
Signed-off-by: Steve Wahl
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index deaafb617361..4c2143d8ae45 100644
--- a
Added Darren Hart, Andy Shevchenko, Thomas Gleixner, Ingo Molnar,
Borislav Petkov, and x86.kernel.org, after being told that
get_maintainers.pl doesn't work on MAINTAINERS.
Thanks,
Steve Wahl, HPE
On Fri, Aug 21, 2020 at 10:48:49AM -0500, Steve Wahl wrote:
>
> Signed-off-by:
Signed-off-by: Steve Wahl
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index deaafb617361..4c2143d8ae45 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -18874,6 +18874,15 @@ S: Maintained
T: git git://git.kernel.org/pub/scm/linux
Reviewed-by: Steve Wahl
On Mon, Aug 03, 2020 at 01:49:48PM +0800, Pingfan Liu wrote:
> Purgatory.ro is a standalone binary that is not linked against the rest of
> the kernel. Its image is copied into an array that is linked to the
> kernel, and from there kexec relocates it wherever i
This series of patches removes support for the UV1 platform and the
efi=old_map kernel command line option.
The documentation for efi=old_map in
Documentation/admin-guide/kernel-parameters.txt was recently touched
and differs between linux-next and the mainline tree. I will send a
separate patc
As a part of UV1 platform removal, don't try to recognize the platform
through DMI to set the EFI_UV1_MEMMAP bit.
Signed-off-by: Steve Wahl
Reviewed-by: Ard Biesheuvel
---
arch/x86/platform/efi/quirks.c | 23 ---
1 file changed, 23 deletions(-)
--- linux.orig/arc
arch/x86/include/asm/uv/uv_hub.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_hub.h | 34 +++---
1 file changed, 3 insertions(+), 31 deletions(-)
--- linux.orig/arch/x86/include/asm/uv/uv_hub.h 2020-07-07 10:49:50.229510422
-0500
arch/x86/include/asm/uv/uv_bau.h: Remove UV1 support
arch/x86/platform/uv/tlb_uv.c: follow structure name change in uv_bau.h
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_bau.h | 118 ++-
arch/x86/platform/uv/tlb_uv.c|4 -
2 files changed
With UV1 removed, EFI_UV1_MEMMAP is not used. Remove code used by it
in arch/x86/platform/uv/bios_uv.c and turn off code in
arch/x86/platform/efi/efi.c that referenced this code.
Signed-off-by: Steve Wahl
Reviewed-by: Ard Biesheuvel
---
arch/x86/platform/efi/efi.c|2
arch/x86
arch/x86/platform/uv/uv_time.c: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/platform/uv/uv_time.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
--- linux.orig/arch/x86/platform/uv/uv_time.c 2020-07-07 10:49:50.565510013
-0500
+++ linux/arch/x86
With UV1 support removed, EFI_UV1_MEMMAP is no longer used.
Signed-off-by: Steve Wahl
Reviewed-by: Ard Biesheuvel
---
arch/x86/include/asm/efi.h | 20 ++--
1 file changed, 2 insertions(+), 18 deletions(-)
--- linux.orig/arch/x86/include/asm/efi.h 2020-07-07 10:49
As a part of UV1 platform removal, delete the efi=old_map option,
which should no longer be needed.
Signed-off-by: Steve Wahl
Acked-by: Ard Biesheuvel
---
arch/x86/platform/uv/bios_uv.c | 14 --
1 file changed, 14 deletions(-)
--- linux.orig/arch/x86/platform/uv/bios_uv.c 2020
arch/x86/include/asm/uv/uv.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux.orig/arch/x86/include/asm/uv/uv.h 2020-07-07 10:49:50.189510470
-0500
+++ linux/arch/x86/include/asm/uv/uv.h 2020
arch/x86/platform/uv/uv_tlb.c: remove UV1 support
Include removing unused timeout_base_ns as reported by l...@intel.com.
Signed-off-by: Steve Wahl
Reported-by: kernel test robot
---
arch/x86/platform/uv/tlb_uv.c | 237 +-
1 file changed, 31 insertions
arch/x86/include/asm/uv/uv_mmrs.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_mmrs.h | 712 --
1 file changed, 712 deletions(-)
--- linux.orig/arch/x86/include/asm/uv/uv_mmrs.h2020-07-07
10:49:50.301510334 -0500
arch/x86/include/asm/uv/bios.h: remove UV1 reference
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/bios.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux.orig/arch/x86/include/asm/uv/bios.h 2020-07-07 10:49:50.153510515
-0500
+++ linux/arch/x86/include/asm/uv
arch/x86/kernel/apic/x2apic_uv_x.c: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/kernel/apic/x2apic_uv_x.c | 122 +++--
1 file changed, 26 insertions(+), 96 deletions(-)
--- linux.orig/arch/x86/kernel/apic/x2apic_uv_x.c 2020-07-07
10:49
In removing UV1 support, efi_have_uv1_memmap is no longer used.
Signed-off-by: Steve Wahl
Reviewed-by: Ard Biesheuvel
---
arch/x86/kernel/kexec-bzimage64.c |9 -
arch/x86/platform/efi/efi.c | 14 +++---
arch/x86/platform/efi/efi_64.c| 38
On Thu, Jul 09, 2020 at 09:02:01AM -0700, Andy Lutomirski wrote:
> On Thu, Jul 9, 2020 at 7:55 AM wrote:
> >
> > As a part of UV1 platform removal, delete the efi=old_map option,
> > which should no longer be needed.
>
> Can you also update kernel_parameters.txt?
>
> --Andy
I plan to, but (I me
arch/x86/include/asm/uv/bios.h: remove UV1 reference
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/bios.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux.orig/arch/x86/include/asm/uv/bios.h 2020-07-07 10:49:50.153510515
-0500
+++ linux/arch/x86/include/asm/uv
arch/x86/platform/uv/uv_time.c: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/platform/uv/uv_time.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
--- linux.orig/arch/x86/platform/uv/uv_time.c 2020-07-07 10:49:50.565510013
-0500
+++ linux/arch/x86
With UV1 removed, EFI_UV1_MEMMAP is not used. Remove code used by it
in arch/x86/platform/uv/bios_uv.c and turn off code in
arch/x86/platform/efi/efi.c that referenced this code.
Signed-off-by: Steve Wahl
---
arch/x86/platform/efi/efi.c|2
arch/x86/platform/uv/bios_uv.c | 159
With UV1 support removed, EFI_UV1_MEMMAP is no longer used.
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/efi.h | 20 ++--
1 file changed, 2 insertions(+), 18 deletions(-)
--- linux.orig/arch/x86/include/asm/efi.h 2020-07-07 10:49:49.753511000
-0500
+++ linux/arch
arch/x86/kernel/apic/x2apic_uv_x.c: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/kernel/apic/x2apic_uv_x.c | 122 +++--
1 file changed, 26 insertions(+), 96 deletions(-)
--- linux.orig/arch/x86/kernel/apic/x2apic_uv_x.c 2020-07-07
10:49
This series of patches removes support for the UV1 platform and the
efi=old_map kernel command line option.
The documentation for efi=old_map in
Documentation/admin-guide/kernel-parameters.txt was recently touched
and differs between linux-next and the mainline tree. I will send a
separate patc
As a part of UV1 platform removal, don't try to recognize the platform
through DMI to set the EFI_UV1_MEMMAP bit.
Signed-off-by: Steve Wahl
---
arch/x86/platform/efi/quirks.c | 23 ---
1 file changed, 23 deletions(-)
--- linux.orig/arch/x86/platform/efi/quirks.c 20
arch/x86/include/asm/uv/uv.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux.orig/arch/x86/include/asm/uv/uv.h 2020-07-07 10:49:50.189510470
-0500
+++ linux/arch/x86/include/asm/uv/uv.h 2020
As a part of UV1 platform removal, delete the efi=old_map option,
which should no longer be needed.
Signed-off-by: Steve Wahl
---
arch/x86/platform/uv/bios_uv.c | 14 --
1 file changed, 14 deletions(-)
--- linux.orig/arch/x86/platform/uv/bios_uv.c 2020-07-07 10:49:50.117510557
arch/x86/platform/uv/uv_tlb.c: remove UV1 support
Include removing unused timeout_base_ns as reported by l...@intel.com.
Signed-off-by: Steve Wahl
Reported-by: kernel test robot
---
arch/x86/platform/uv/tlb_uv.c | 237 +-
1 file changed, 31 insertions
arch/x86/include/asm/uv/uv_mmrs.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_mmrs.h | 712 --
1 file changed, 712 deletions(-)
--- linux.orig/arch/x86/include/asm/uv/uv_mmrs.h2020-07-07
10:49:50.301510334 -0500
arch/x86/include/asm/uv/uv_hub.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_hub.h | 34 +++---
1 file changed, 3 insertions(+), 31 deletions(-)
--- linux.orig/arch/x86/include/asm/uv/uv_hub.h 2020-07-07 10:49:50.229510422
-0500
In removing UV1 support, efi_have_uv1_memmap is no longer used.
Signed-off-by: Steve Wahl
---
arch/x86/kernel/kexec-bzimage64.c |9 -
arch/x86/platform/efi/efi.c | 14 +++---
arch/x86/platform/efi/efi_64.c| 38 +++---
arch/x86
arch/x86/include/asm/uv/uv_bau.h: Remove UV1 support
arch/x86/platform/uv/tlb_uv.c: follow structure name change in uv_bau.h
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_bau.h | 118 ++-
arch/x86/platform/uv/tlb_uv.c|4 -
2 files changed
With UV1 support removed, EFI_UV1_MEMMAP is no longer used.
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/efi.h | 20 ++--
1 file changed, 2 insertions(+), 18 deletions(-)
--- linux.orig/arch/x86/include/asm/efi.h 2020-06-17 14:21:49.798542440
-0500
+++ linux/arch
arch/x86/include/asm/uv/bios.h: remove UV1 reference
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/bios.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/uv/bios.h b/arch/x86/include/asm/uv/bios.h
index 2fcc3ac12e76..70050d0136c3 100644
--- a
arch/x86/include/asm/uv/uv_hub.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_hub.h | 34 +++---
1 file changed, 3 insertions(+), 31 deletions(-)
diff --git a/arch/x86/include/asm/uv/uv_hub.h b/arch/x86/include/asm/uv/uv_hub.h
index
arch/x86/platform/uv/uv_tlb.c: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/platform/uv/tlb_uv.c | 228 ++
1 file changed, 33 insertions(+), 195 deletions(-)
diff --git a/arch/x86/platform/uv/tlb_uv.c b/arch/x86/platform/uv/tlb_uv.c
index
arch/x86/kernel/apic/x2apic_uv_x.c: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/kernel/apic/x2apic_uv_x.c | 121 +++--
1 file changed, 25 insertions(+), 96 deletions(-)
--- linux.orig/arch/x86/kernel/apic/x2apic_uv_x.c 2020-06-17
14:22
This series of patches removes support for the UV1 platform and the
efi=old_map kernel command line option.
The documentation for efi=old_map in
Documentation/admin-guide/kernel-parameters.txt was recently touched
and differs between linux-next and the mainline tree. I will send a
separate patc
As a part of UV1 platform removal, don't try to recognize the platform
through DMI to set the EFI_UV1_MEMMAP bit.
Signed-off-by: Steve Wahl
---
arch/x86/platform/efi/quirks.c | 23 ---
1 file changed, 23 deletions(-)
--- linux.orig/arch/x86/platform/efi/quirks.c 20
arch/x86/include/asm/uv/uv_bau.h: Remove UV1 support
arch/x86/platform/uv/tlb_uv.c: follow structure name change in uv_bau.h
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_bau.h | 118 ++-
arch/x86/platform/uv/tlb_uv.c|4 -
2 files changed
With UV1 removed, EFI_UV1_MEMMAP is not used. Remove code used by it
in arch/x86/platform/uv/bios_uv.c and turn off code in
arch/x86/platform/efi/efi.c that referenced this code.
Signed-off-by: Steve Wahl
---
arch/x86/platform/efi/efi.c|2
arch/x86/platform/uv/bios_uv.c | 159
arch/x86/include/asm/uv/uv_mmrs.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv_mmrs.h | 712 --
1 file changed, 712 deletions(-)
diff --git a/arch/x86/include/asm/uv/uv_mmrs.h
b/arch/x86/include/asm/uv/uv_mmrs.h
index
In removing UV1 support, efi_have_uv1_memmap is no longer used.
Signed-off-by: Steve Wahl
---
arch/x86/kernel/kexec-bzimage64.c |9 -
arch/x86/platform/efi/efi.c | 14 +++---
arch/x86/platform/efi/efi_64.c| 38 +++---
arch/x86
arch/x86/platform/uv/uv_time.c: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/platform/uv/uv_time.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/arch/x86/platform/uv/uv_time.c b/arch/x86/platform/uv/uv_time.c
index 7af31b245636..41e982fda86c
arch/x86/include/asm/uv/uv.h: remove UV1 support
Signed-off-by: Steve Wahl
---
arch/x86/include/asm/uv/uv.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/uv/uv.h b/arch/x86/include/asm/uv/uv.h
index ae587ce544f4..45e2e905909b 100644
--- a/arch/x86
As a part of UV1 platform removal, delete the efi=old_map option,
which should no longer be needed.
Signed-off-by: Steve Wahl
---
Documentation/admin-guide/kernel-parameters.txt |4 +---
arch/x86/platform/uv/bios_uv.c | 14 --
2 files changed, 1 insertion
nk that the memory reserved by the firmware is still
> > > memory and it should be added to memblock.memory. This way the memory
> >
> > If it's really memory that could be read/written, I think I agree.
>
> I would say some of them may not be allowed t
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 33649bf4494c1feaf1956a84895fcc0621aafd90
Gitweb:
https://git.kernel.org/tip/33649bf4494c1feaf1956a84895fcc0621aafd90
Author:Steve Wahl
AuthorDate:Wed, 13 May 2020 17:11:23 -05:00
eturn;
- }
-
base = (gru.v & mask) >> shift;
map_high("GRU", base, shift, shift, max_pnode, map_wb);
gru_start_paddr = ((u64)base << shift);
--
2.12.3
From: Steve Wahl
To:
Cc:
Bcc:
Subject:
Reply-To:
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: 1869dbe87cb94dc9a218ae1d9301dea3678bd4ff
Gitweb:
https://git.kernel.org/tip/1869dbe87cb94dc9a218ae1d9301dea3678bd4ff
Author:Steve Wahl
AuthorDate:Tue, 24 Sep 2019 16:04:31 -05:00
Committer
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: 1869dbe87cb94dc9a218ae1d9301dea3678bd4ff
Gitweb:
https://git.kernel.org/tip/1869dbe87cb94dc9a218ae1d9301dea3678bd4ff
Author:Steve Wahl
AuthorDate:Tue, 24 Sep 2019 16:04:31 -05:00
Committer
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: 2aa85f246c181b1fa89f27e8e20c5636426be624
Gitweb:
https://git.kernel.org/tip/2aa85f246c181b1fa89f27e8e20c5636426be624
Author:Steve Wahl
AuthorDate:Tue, 24 Sep 2019 16:03:55 -05:00
Committer
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: 2aa85f246c181b1fa89f27e8e20c5636426be624
Gitweb:
https://git.kernel.org/tip/2aa85f246c181b1fa89f27e8e20c5636426be624
Author:Steve Wahl
AuthorDate:Tue, 24 Sep 2019 16:03:55 -05:00
Committer
It's been a while on this patch set; two weeks ago Kirill added acks,
no movement since. Is there anything I need to be doing on my part to
move this forward?
Thanks!
--> Steve Wahl
On Tue, Sep 24, 2019 at 04:03:22PM -0500, Steve Wahl wrote:
> This patch set narrows the valid spac
ff-by: Steve Wahl
Cc: sta...@vger.kernel.org
---
Changes since v1:
* This patch is completely new to this verison.
Changes since v2:
None.
arch/x86/boot/compressed/misc.c | 25 +++--
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git a/arch/x86/boot/compressed/mis
blem on our hardware.
Signed-off-by: Steve Wahl
Cc: sta...@vger.kernel.org
---
Changes since v1:
* Added comment.
* Reworked changelog text.
Changes since v2:
* Added further inline comments.
arch/x86/kernel/head64.c | 22 --
1 file changed, 20 insertions(+), 2 deletions(-
Dave Hansen to handle the case that
the mapping of the last PMD page for the kernel image could cross a
reserved region boundary.
Changes since v2:
* Patch 1: Added further inline comments.
* Patch 2: None.
Steve Wahl (2):
x86/boot/64: Make level2_kernel_pgt pages invalid outside kernel area
On Mon, Sep 23, 2019 at 02:19:46PM -0700, Dave Hansen wrote:
> On 9/23/19 11:15 AM, Steve Wahl wrote:
> > pmd = fixup_pointer(level2_kernel_pgt, physaddr);
> > - for (i = 0; i < PTRS_PER_PMD; i++) {
> > + for (i = 0; i < pmd_index((unsigned long)_text);
On Mon, Sep 23, 2019 at 02:20:35PM -0700, Dave Hansen wrote:
> On 9/23/19 11:15 AM, Steve Wahl wrote:
> > The kernel image map is created using PMD pages, which can include
> > some extra space beyond what's actually needed. Round the size of the
> > memory hole we sea
On Mon, Sep 23, 2019 at 11:49:44AM -0700, h...@zytor.com wrote:
> On September 23, 2019 11:15:20 AM PDT, Steve Wahl wrote:
> >Our hardware (UV aka Superdome Flex) has address ranges marked
> >reserved by the BIOS. Access to these ranges is caught as an error,
> >causing
ff-by: Steve Wahl
Cc: sta...@vger.kernel.org
---
Changes since v1:
* This patch is completely new to this verison.
arch/x86/boot/compressed/misc.c | 25 +++--
1 file changed, 19 insertions(+), 6 deletions(-)
diff --git a/arch/x86/boot/compressed/misc.c b/arch/x86/boot/compr
blem on our hardware.
Signed-off-by: Steve Wahl
Cc: sta...@vger.kernel.org
---
Changes since v1:
* Added comment.
* Reworked changelog text.
arch/x86/kernel/head64.c | 18 --
1 file changed, 16 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/head64.c b/arch/x86/k
Dave Hansen to handle the case that
the mapping of the last PMD page for the kernel image could cross a
reserved region boundary.
Steve Wahl (2):
x86/boot/64: Make level2_kernel_pgt pages invalid outside kernel area.
x86/boot/64: round memory hole size up to next PMD page.
arch/x86/boot/co
not go
there because for us it is not necessary.
> Is it in the lower 1MB, by chance?
No, this is a reserved range at the top physical addresses for each
NUMA node in a collection of them.
> If this is all about avoiding EFI reserved ranges, why doesn't the
> patch *LOOK* At
On Mon, Sep 16, 2019 at 12:00:58PM +0300, Kirill A. Shutemov wrote:
> On Fri, Sep 13, 2019 at 10:14:15AM -0500, Steve Wahl wrote:
> > On Thu, Sep 12, 2019 at 01:19:17PM +0300, Kirill A. Shutemov wrote:
> > > On Wed, Sep 11, 2019 at 03:08:35PM -0500, Steve Wahl wrote:
> >
On Thu, Sep 12, 2019 at 01:19:17PM +0300, Kirill A. Shutemov wrote:
> On Wed, Sep 11, 2019 at 03:08:35PM -0500, Steve Wahl wrote:
> > Thank you for your time looking into this with me!
>
> With all this explanation the original patch looks sane to me.
>
> But I would like to
On Wed, Sep 11, 2019 at 03:28:56AM +0300, Kirill A. Shutemov wrote:
> On Tue, Sep 10, 2019 at 09:28:10AM -0500, Steve Wahl wrote:
> > On Mon, Sep 09, 2019 at 11:14:14AM +0300, Kirill A. Shutemov wrote:
> > > On Fri, Sep 06, 2019 at 04:29:50PM -0500, Steve Wahl wrote:
> > &g
On Tue, Sep 10, 2019 at 08:18:15AM +0200, Ingo Molnar wrote:
>
> * Kirill A. Shutemov wrote:
>
> > On Fri, Sep 06, 2019 at 04:29:50PM -0500, Steve Wahl wrote:
> > > Our hardware (UV aka Superdome Flex) has address ranges marked
> > > reserved by the BIOS. The
On Mon, Sep 09, 2019 at 11:14:14AM +0300, Kirill A. Shutemov wrote:
> On Fri, Sep 06, 2019 at 04:29:50PM -0500, Steve Wahl wrote:
> > ...
> > The answer is to invalidate the pages of this table outside the
> > address range occupied by the kernel before the page table is
>
ned-off-by: Steve Wahl
Cc: sta...@vger.kernel.org
---
arch/x86/kernel/head64.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/head64.c b/arch/x86/kernel/head64.c
index 29ffa495bd1c..31f89a5defa3 100644
--- a/arch/x86/kernel/head64.c
+++ b/arch/x86/kerne
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: e16c2983fba0fa6763e43ad10916be35e3d8dc05
Gitweb:
https://git.kernel.org/tip/e16c2983fba0fa6763e43ad10916be35e3d8dc05
Author:Steve Wahl
AuthorDate:Thu, 05 Sep 2019 15:23:46 -05:00
Committer
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: e16c2983fba0fa6763e43ad10916be35e3d8dc05
Gitweb:
https://git.kernel.org/tip/e16c2983fba0fa6763e43ad10916be35e3d8dc05
Author:Steve Wahl
AuthorDate:Thu, 05 Sep 2019 15:23:46 -05:00
Committer
nd then
apply them to each of the objects that have C source. Do not apply
any of these flags to kexec-purgatory.o, which is not part of the
standalone object but part of the kernel proper.
Fixes: b059f801a937 ("x86/purgatory: Use CFLAGS_REMOVE rather than reset
KBUILD_CFLAGS")
S
On Thu, Sep 05, 2019 at 11:15:14AM +0200, Borislav Petkov wrote:
> On Wed, Sep 04, 2019 at 04:45:05PM -0500, Steve Wahl wrote:
> > The last change to this Makefile caused relocation errors when loading
> > a kdump kernel.
>
> How do those relocation errors look like
1 - 100 of 105 matches
Mail list logo
