similar to: [PATCH] x86: fix early option scanning

Thomas Schmitt said: > I am wondering about the meaning or reason of "+20" in this assembler line: > > movl (32+20)(%si), %ecx > > Why that extra offset 20 on the byte offset 32 which is specified by > GPT specs (UEFI 2.4, 5.3.3) ? (Do i get the language wrong ?) Well I've been looking at this. It seems gptmbr.S

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

OK, at least two patches got dropped on the way from the mm tree to Andi's tree: the desc.h cleanup, and the processor.h rearrangement. Merging into Andi's tree without these patches must have been a nightmare 8( Andi then tried to fix it with x86_64-mm-paravirt-compile.patch but then it didn't boot so he disabled it in x86_64-mm-paravirt-broken.patch This patch undoes those two

OK, at least two patches got dropped on the way from the mm tree to Andi's tree: the desc.h cleanup, and the processor.h rearrangement. Merging into Andi's tree without these patches must have been a nightmare 8( Andi then tried to fix it with x86_64-mm-paravirt-compile.patch but then it didn't boot so he disabled it in x86_64-mm-paravirt-broken.patch This patch undoes those two

As suggested, I checked that I was getting wine of the right vintage, and as you see below, I indeed seem to have the version designated by the codeweavers rpm name I downloaded (codeweavers-wine-20011108-5.i386.rpm): [cafl@emma cafl]$ which wine /usr/bin/wine [cafl@emma cafl]$ /usr/bin/wine --version Wine release 20011108 Wine exited with a successful status [cafl@emma

--- mbr/Makefile | 6 +- mbr/mbr-diag.S | 377 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 382 insertions(+), 1 deletions(-) create mode 100644 mbr/mbr-diag.S diff --git a/mbr/Makefile b/mbr/Makefile index 0bdf7e3..b9d743d 100644 --- a/mbr/Makefile +++ b/mbr/Makefile @@ -17,7 +17,7 @@ topdir = .. include $(topdir)/MCONFIG.embedded -all: mbr.bin gptmbr.bin

Illustration of how VMI inlines are used to greatly limit the impact of code change in low level assembler code. Spinlocks, system calls, and the fault handling paths are affected by adding some padding bytes to convert the native instructions into a hook point for the hypervisor to insert shim code. These changes are sufficient to glue the Linux low level entry points to hypervisor event

Illustration of how VMI inlines are used to greatly limit the impact of code change in low level assembler code. Spinlocks, system calls, and the fault handling paths are affected by adding some padding bytes to convert the native instructions into a hook point for the hypervisor to insert shim code. These changes are sufficient to glue the Linux low level entry points to hypervisor event

The parts of klibc specific to the i386 architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit bd0599e5290ca1a16bb7a68f7c362d395c612eb3 tree 8f33afdd02a14c22e7a3984da2bad13184e3f729 parent 84f6a72f42cf41e32daa59871a0b5424572093e4 author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:21 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

--- mbr/Makefile | 6 +- mbr/mbr-diag.S | 371 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 376 insertions(+), 1 deletions(-) create mode 100644 mbr/mbr-diag.S diff --git a/mbr/Makefile b/mbr/Makefile index 0bdf7e3..b9d743d 100644 --- a/mbr/Makefile +++ b/mbr/Makefile @@ -17,7 +17,7 @@ topdir = .. include $(topdir)/MCONFIG.embedded -all: mbr.bin gptmbr.bin

On Fri, Feb 10, 2017 at 12:00:43PM -0500, Waiman Long wrote: > >> +asm( > >> +".pushsection .text;" > >> +".global __raw_callee_save___kvm_vcpu_is_preempted;" > >> +".type __raw_callee_save___kvm_vcpu_is_preempted, @function;" > >> +"__raw_callee_save___kvm_vcpu_is_preempted:" > >> +FRAME_BEGIN >

On Fri, Feb 10, 2017 at 12:00:43PM -0500, Waiman Long wrote: > >> +asm( > >> +".pushsection .text;" > >> +".global __raw_callee_save___kvm_vcpu_is_preempted;" > >> +".type __raw_callee_save___kvm_vcpu_is_preempted, @function;" > >> +"__raw_callee_save___kvm_vcpu_is_preempted:" > >> +FRAME_BEGIN >

On 02/13/2017 05:53 AM, Peter Zijlstra wrote: > On Mon, Feb 13, 2017 at 11:47:16AM +0100, Peter Zijlstra wrote: >> That way we'd end up with something like: >> >> asm(" >> push %rdi; >> movslq %edi, %rdi; >> movq __per_cpu_offset(,%rdi,8), %rax; >> cmpb $0, %[offset](%rax); >> setne %al; >> pop %rdi; >> " : : [offset]

On 02/13/2017 05:53 AM, Peter Zijlstra wrote: > On Mon, Feb 13, 2017 at 11:47:16AM +0100, Peter Zijlstra wrote: >> That way we'd end up with something like: >> >> asm(" >> push %rdi; >> movslq %edi, %rdi; >> movq __per_cpu_offset(,%rdi,8), %rax; >> cmpb $0, %[offset](%rax); >> setne %al; >> pop %rdi; >> " : : [offset]

This oops manifests itself on the following hardware: 01:00.0 VGA compatible controller: NVIDIA Corporation G98M [GeForce G 103M] (rev a1) Oct 09 14:17:46 lp-sasha kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 Oct 09 14:17:46 lp-sasha kernel: #PF: supervisor read access in kernel mode Oct 09 14:17:46 lp-sasha kernel: #PF: error_code(0x0000) - not-present page Oct 09

On February 13, 2017 2:53:43 AM PST, Peter Zijlstra <peterz at infradead.org> wrote: >On Mon, Feb 13, 2017 at 11:47:16AM +0100, Peter Zijlstra wrote: >> That way we'd end up with something like: >> >> asm(" >> push %rdi; >> movslq %edi, %rdi; >> movq __per_cpu_offset(,%rdi,8), %rax; >> cmpb $0, %[offset](%rax); >> setne %al;

On February 13, 2017 2:53:43 AM PST, Peter Zijlstra <peterz at infradead.org> wrote: >On Mon, Feb 13, 2017 at 11:47:16AM +0100, Peter Zijlstra wrote: >> That way we'd end up with something like: >> >> asm(" >> push %rdi; >> movslq %edi, %rdi; >> movq __per_cpu_offset(,%rdi,8), %rax; >> cmpb $0, %[offset](%rax); >> setne %al;

git://git.zytor.com/users/genec/syslinux.git Branch handoff-mbr-for-hpa This is a piece of code that can be used in place of a MBR or VBR/PBR (master boot record; volume/partition) in order to examine the data handed to the respective boot code. AX, SS, and SP are destroyed before examining anything. I set an internal restriction that limits it to 420 bytes such that it could be used with a

This oops manifests itself on the following hardware: 01:00.0 VGA compatible controller: NVIDIA Corporation G98M [GeForce G 103M] (rev a1) Oct 09 14:17:46 lp-sasha kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000 Oct 09 14:17:46 lp-sasha kernel: #PF: supervisor read access in kernel mode Oct 09 14:17:46 lp-sasha kernel: #PF: error_code(0x0000) - not-present page Oct 09

On Tue, May 30, 2023 at 12:30:06AM -0700, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: 933174ae28ba Merge tag 'spi-fix-v6.4-rc3' of git://git.ker.. > git tree: upstream > console output: https://syzkaller.appspot.com/x/log.txt?x=138d4ae5280000 > kernel config: https://syzkaller.appspot.com/x/.config?x=f389ffdf4e9ba3f0