Re: [PATCH 2/6] KVM: x86: Wrong error code on limit violation during emulation

2014-10-27 Thread Paolo Bonzini
On 09/30/2014 07:49 PM, Nadav Amit wrote: GP and SS exceptions deliver as error-code the segment selector if the exception occurred when the segment is loaded. However, if the exception occurs during the memory access itself, due to limit violations, the error-code should be zero. Fix

Re: [PATCH 2/6] KVM: x86: Wrong error code on limit violation during emulation

2014-10-27 Thread Paolo Bonzini
On 10/27/2014 03:46 PM, Nadav Amit wrote: So I've dropped this patch, and posted a simpler alternative that just uses error code 0 in __linearize. Can you look at it? It looks fine. I noticed these mistakes also... Please wait with the other emulator fixes I posted. I run some further

Re: [PATCH 2/6] KVM: x86: Wrong error code on limit violation during emulation

2014-10-27 Thread Nadav Amit
On Oct 27, 2014, at 16:37, Paolo Bonzini pbonz...@redhat.com wrote: On 09/30/2014 07:49 PM, Nadav Amit wrote: GP and SS exceptions deliver as error-code the segment selector if the exception occurred when the segment is loaded. However, if the exception occurs during the memory access

Re: [PATCH 2/6] KVM: x86: Wrong error code on limit violation during emulation

2014-10-01 Thread Radim Krčmář
2014-09-30 20:49+0300, Nadav Amit: GP and SS exceptions deliver as error-code the segment selector if the exception occurred when the segment is loaded. However, if the exception occurs during the memory access itself, due to limit violations, the error-code should be zero. Fix it.

[PATCH 2/6] KVM: x86: Wrong error code on limit violation during emulation

2014-09-30 Thread Nadav Amit
GP and SS exceptions deliver as error-code the segment selector if the exception occurred when the segment is loaded. However, if the exception occurs during the memory access itself, due to limit violations, the error-code should be zero. Fix it. Signed-off-by: Nadav Amit