[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] tools/tests: Add EIP check to test_x86_emulator.c


  • To: Jan Beulich <JBeulich@xxxxxxxx>
  • From: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
  • Date: Thu, 07 Aug 2014 11:53:35 +0300
  • Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, stefano.stabellini@xxxxxxxxxxxxx, ian.jackson@xxxxxxxxxxxxx, ian.campbell@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxx
  • Comment: DomainKeys? See http://domainkeys.sourceforge.net/
  • Delivery-date: Thu, 07 Aug 2014 08:53:56 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bitdefender.com; b=GBfEbFGE9ZXDHJW9C9QWDdhK67RJAuMpa5dvmpZwvP1yF1hYyfGtRnw1pEYJXcaUNOB6ffKwt4v8wLk+jWMBmHTlhIDMYUeRjr60iJijWGBYElM7R0huFWXptQYmh6G4u/c8mqklJ0AaEJLAJCqSL7FNAEr2J3IFLF/yrs6YPCVesOnPifjdOPmsfmeAnlTHWnuwQ2a8uz028AVgeqc/jdGR3RZRXk8JrzGeHC0gv/fFaq6EWBk7LAnKZll05815KT7BxrQP9crBemWbj3qcps/FlxkkTJFNh0s2AyMN0KGbMV/tRASK1bdWN0JBYBCb7j2K3Rla7+TkDJQ3YWm/fg==; h=Received:Received:Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-BitDefender-Scanner:X-BitDefender-Spam:X-BitDefender-SpamStamp:X-BitDefender-CF-Stamp;
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 08/07/2014 11:45 AM, Jan Beulich wrote:
>>>> On 07.08.14 at 10:35, <rcojocaru@xxxxxxxxxxxxxxx> wrote:
>> On 08/07/2014 11:32 AM, Jan Beulich wrote:
>>>>>> On 07.08.14 at 10:18, <andrew.cooper3@xxxxxxxxxx> wrote:
>>>> On 07/08/2014 09:16, Razvan Cojocaru wrote:
>>>>> The test now also checks that EIP was modified after emulating
>>>>> instructions after (and including) the "movq %mm3,(%ecx)..."
>>>>> code block.
>>>>>
>>>>> Signed-off-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
>>>>
>>>> These checks do check that the instruction pointer has changed, which
>>>> catches your problem, but doesn't check that it has changed correctly. 
>>>> You need to work out exactly how long the instruction is a verify that
>>>> eip points to first byte of the next instruction.
>>>
>>> And apart from that this should be done for all tests, not just the
>>> MMX/SSE/AVX ones.
>>
>> The other tests already do this, but there it's simpler to check.
> 
> Ah, my bad then (both in not having checked the code before
> replying, and in not having added these checks back when I
> added those tests) - I'm sorry.

Absolutely no problem at all, we're all friends here.


Thanks,
Razvan Cojocaru

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.