Skip to contentSkip to conversation

When switching to real-mode, pass SS in a GP register

PATCH In review Anthony Liguori 3 participants 5 messages Sep 30, 2007 – Oct 11, 2007 4 messages not in the archive KVM

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 When switching to real-mode, pass SS in a GP register

Hi Steffen,

As Avi pointed out, VT requires that SS.RPL == CS.RPL. We're seeing gfxboot fail under KVM because ss = 0x5761 while cs = 0x4004 during the transition from real mode to protected mode. The attached patch passes the value of ss through ebx since KVM has to sanitize the value of ss to make VT happy.

I've tested this with a remastered Ubuntu Gutsy install CD. I couldn't find the right gfxboot theme for the openSuSE install CD I have so I wasn't able to test it.

I suspect that Xen should have a very similar problem as I can't think of a possible way to work around this.

Regards,

Anthony Liguori

Subject: [PATCH] Fix gfxboot under VT
From: Anthony Liguori <[email protected]>

This patch lets gfxboot-3.3.38 work under KVM. The fix was suggested by Avi Kivity.

bincode.asm +8 -1
diff -ur a/bincode.asm b/bincode.asm
@@ -15519,6 +15519,7 @@
 switch_to_pm:
 		pushf
 		push eax
+		push ebx
 
 		mov eax,cr0
 
@@ -15534,6 +15535,11 @@
 		mov word [cs:rm_seg.fs],fs
 		mov word [cs:rm_seg.gs],gs
 
+		;; ss:rpl must equal cs:rpl in PM for VT.  we can't rely on ss
+		;; maintaining it's value after the transition so we have to
+		;; pass it in a GP register
+		mov ebx,ss
+	
 		or al,1
 		o32 lgdt [cs:pm_gdt]
 		o32 lidt [cs:pm_idt]
@@ -15546,7 +15552,7 @@
 		mov ax,pm_seg.prog_d16
 		mov ds,ax
 
-		mov eax,ss
+		mov eax,ebx
 		and esp,0ffffh
 		shl eax,4
 		add esp,eax
@@ -15557,6 +15563,7 @@
 		mov fs,ax
 		mov gs,ax
 
+		pop ebx
 		pop eax
 		popfw
 		o16 ret

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
kvm-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 40 lines · Anthony Liguori

Hi Steffen,

As Avi pointed out, VT requires that SS.RPL == CS.RPL. We're seeing gfxboot fail under KVM because ss = 0x5761 while cs = 0x4004 during the transition from real mode to protected mode. The attached patch passes the value of ss through ebx since KVM has to sanitize the value of ss to make VT happy.

I've tested this with a remastered Ubuntu Gutsy install CD. I couldn't find the right gfxboot theme for the openSuSE install CD I have so I wasn't able to test it.

I suspect that Xen should have a very similar problem as I can't think of a possible way to work around this.

diff -ur a/bincode.asm b/bincode.asm

bincode.asm +6 -0
@@ -15519,6 +15519,7 @@
 switch_to_pm:
 		pushf
 		push eax
+		push ebx
 
 		mov eax,cr0
 
@@ -15534,6 +15535,11 @@
 		mov word [cs:rm_seg.fs],fs
 		mov word [cs:rm_seg.gs],gs
 
+		;; ss:rpl must equal cs:rpl in PM for VT.  we can't rely on ss
+		;; maintaining it's value after the transition so we have to
+		;; pass it in a GP register
+		mov ebx,ss
+	
 		or al,1
 		o32 lgdt [cs:pm_gdt]
 		o32 lidt [cs:pm_idt]

bincode.asm line 15558

Quoted 8 lines
bincode.asm +1 -1
@@ -15546,7 +15552,7 @@
 		mov ax,pm_seg.prog_d16
 		mov ds,ax
 
-		mov eax,ss
+		mov eax,ebx
 		and esp,0ffffh
 		shl eax,4
 

This is subtly wrong, I think. First, note that 'mov eax,ss' only affects ax, not the high 16 bits. The note that the original code happily shifts eax which is half ss, half garbage left by 4 bits and uses that to generate a 32-bit result.

The reason it worked before was that bits 16-29 of eax are already clear by virtue of having come from cr0. But now you're using ebx which hasn't had that magic clearing.

In your comment to the kvm bug you say that the patch allows you to boot, so perhaps bits 16-29 of ebx are already clear here, or my analysis is mistaken.

Quoted 10 lines
bincode.asm +1 -0
 		add esp,eax
@@ -15557,6 +15563,7 @@
 		mov fs,ax
 		mov gs,ax
 
+		pop ebx
 		pop eax
 		popfw
 		o16 ret
Signature · 7 lines
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

A message that is not in the archive (sent off-list or not yet received): 46FF3DF3.7040503-atKUWr5tajBWk0Htik3J/[email protected]

#4 lore raw
Quoted 59 lines · Avi Kivity
Quoted 43 lines · Anthony Liguori

Hi Steffen,

As Avi pointed out, VT requires that SS.RPL == CS.RPL. We're seeing gfxboot fail under KVM because ss = 0x5761 while cs = 0x4004 during the transition from real mode to protected mode. The attached patch passes the value of ss through ebx since KVM has to sanitize the value of ss to make VT happy.

I've tested this with a remastered Ubuntu Gutsy install CD. I couldn't find the right gfxboot theme for the openSuSE install CD I have so I wasn't able to test it.

I suspect that Xen should have a very similar problem as I can't think of a possible way to work around this.

diff -ur a/bincode.asm b/bincode.asm

bincode.asm +6 -0
@@ -15519,6 +15519,7 @@
 switch_to_pm:
 		pushf
 		push eax
+		push ebx
 
 		mov eax,cr0
 
@@ -15534,6 +15535,11 @@
 		mov word [cs:rm_seg.fs],fs
 		mov word [cs:rm_seg.gs],gs
 
+		;; ss:rpl must equal cs:rpl in PM for VT.  we can't rely on ss
+		;; maintaining it's value after the transition so we have to
+		;; pass it in a GP register
+		mov ebx,ss
+	
 		or al,1
 		o32 lgdt [cs:pm_gdt]
 		o32 lidt [cs:pm_idt]

bincode.asm line 15558

Quoted 8 lines
bincode.asm +1 -1
@@ -15546,7 +15552,7 @@
 		mov ax,pm_seg.prog_d16
 		mov ds,ax
 
-		mov eax,ss
+		mov eax,ebx
 		and esp,0ffffh
 		shl eax,4
 

This is subtly wrong, I think. First, note that 'mov eax,ss' only affects ax, not the high 16 bits. The note that the original code happily shifts eax which is half ss, half garbage left by 4 bits and uses that to generate a 32-bit result.

Quoted 4 lines

The reason it worked before was that bits 16-29 of eax are already clear by virtue of having come from cr0. But now you're using ebx which hasn't had that magic clearing.

You're right. Good catch!

Quoted 4 lines

In your comment to the kvm bug you say that the patch allows you to boot, so perhaps bits 16-29 of ebx are already clear here, or my analysis is mistaken.

Yeah, I just got lucky with ebx I guess :-) Attached is an updated patch that fixes this problem.

Regards,

Anthony Liguori

Quoted 5 lines
Quoted 5 lines
bincode.asm +0 -0
 		add esp,eax
@@ -15557,6 +15563,7 @@
 		mov fs,ax
 		mov gs,ax
 
Quoted 10 lines

bincode.asm line 15569

Quoted 6 lines
bincode.asm +1 -0
+		pop ebx
 		pop eax
 		popfw
 		o16 ret
bincode.asm +8 -1
diff -ur a/bincode.asm b/bincode.asm
@@ -15519,6 +15519,7 @@
 switch_to_pm:
 		pushf
 		push eax
+		push ebx
 
 		mov eax,cr0
 
@@ -15534,6 +15535,11 @@
 		mov word [cs:rm_seg.fs],fs
 		mov word [cs:rm_seg.gs],gs
 
+		;; ss:rpl must equal cs:rpl in PM for VT.  we can't rely on ss
+		;; maintaining it's value after the transition so we have to
+		;; pass it in a GP register
+		mov ebx,ss
+	
 		or al,1
 		o32 lgdt [cs:pm_gdt]
 		o32 lidt [cs:pm_idt]
@@ -15546,7 +15552,7 @@
 		mov ax,pm_seg.prog_d16
 		mov ds,ax
 
-		mov eax,ss
+		mov ax,bx
 		and esp,0ffffh
 		shl eax,4
 		add esp,eax
@@ -15557,6 +15563,7 @@
 		mov fs,ax
 		mov gs,ax
 
+		pop ebx
 		pop eax
 		popfw
 		o16 ret

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
kvm-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel

A message that is not in the archive (sent off-list or not yet received): [email protected]

#6 lore raw

Hi,

sorry for the delay, but I've been on vacation. :-)

Quoted 8 lines · Anthony Liguori
Quoted 7 lines · Avi Kivity
Quoted 5 lines · Anthony Liguori

As Avi pointed out, VT requires that SS.RPL == CS.RPL. We're seeing gfxboot fail under KVM because ss = 0x5761 while cs = 0x4004 during the transition from real mode to protected mode. The attached patch passes the value of ss through ebx since KVM has to sanitize the value of ss to make VT happy.

Uh, that's weird! Thanks for pointing this out.

[patch]

Quoted 11 lines
Quoted 9 lines

This is subtly wrong, I think. First, note that 'mov eax,ss' only affects ax, not the high 16 bits. The note that the original code happily shifts eax which is half ss, half garbage left by 4 bits and uses that to generate a 32-bit result.

The reason it worked before was that bits 16-29 of eax are already clear by virtue of having come from cr0. But now you're using ebx which hasn't had that magic clearing.

You're right. Good catch!

Actually that is not true. 'mov eax,ss' does implicitly clear the upper 16 bits (both processor docs and hardware agree here).

Quoted 7 lines
Quoted 4 lines

In your comment to the kvm bug you say that the patch allows you to boot, so perhaps bits 16-29 of ebx are already clear here, or my analysis is mistaken.

Yeah, I just got lucky with ebx I guess :-) Attached is an updated patch that fixes this problem.

Anyway, ss is already saved, so no need for an extra register. Here is my version (tested and works on my machine):

bincode.asm +5 -1
@@ -15546,7 +15546,11 @@
 		mov ax,pm_seg.prog_d16
 		mov ds,ax
 
-		mov eax,ss
+		; needed for KVM:
+		; ss:rpl must equal cs:rpl in PM for VT. We can't rely on ss
+		; maintaining its value after the transition.
+
+		movzx eax,word [rm_seg.ss]
 		and esp,0ffffh
 		shl eax,4
 		add esp,eax

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/

A message that is not in the archive (sent off-list or not yet received): Pine.LNX.4.64.0710081237050.22177-128n8RpADxRbpigZmTR7Iw@public.gmane.org

#8 lore raw
Quoted 4 lines · Steffen Winterfeldt

Hi,

sorry for the delay, but I've been on vacation. :-)

No worries :-)

Quoted 6 lines
Quoted 2 lines

You're right. Good catch!

Actually that is not true. 'mov eax,ss' does implicitly clear the upper 16 bits (both processor docs and hardware agree here).

I wasn't able to find anything definitive in my manuals but I didn't look very hard. I figured that erring on the safe side is better anyway.

Quoted 3 lines

Anyway, ss is already saved, so no need for an extra register. Here is my version (tested and works on my machine):

This patch works for me under KVM. Thanks!

Regards,

Anthony Liguori

Quoted 7 lines
bincode.asm +0 -0
@@ -15546,7 +15546,11 @@
 		mov ax,pm_seg.prog_d16
 		mov ds,ax

bincode.asm line 15556

Quoted 10 lines
bincode.asm +5 -1
 
-		mov eax,ss
+		; needed for KVM:
+		; ss:rpl must equal cs:rpl in PM for VT. We can't rely on ss
+		; maintaining its value after the transition.
+
+		movzx eax,word [rm_seg.ss]
 		and esp,0ffffh
 		shl eax,4
 		add esp,eax

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/