linux-kernel - Re: [PATCH] disable interrupt shadow state for emulated instruction

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 09 Apr 2009 10:41:19 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Glauber Costa <glommer@...hat.com>
CC:	"H. Peter Anvin" <hpa@...or.com>, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] disable interrupt shadow state for emulated instruction

Glauber Costa wrote:
>> How does this logic work when the instruction emulated is an STI or MOV  
>> SS instruction?  In particular, when does GUEST_INTERRUPTIBILITY_INFO  
>> sets set to reflect the *blocking* operation?
>>     
> mov ss is a non-issue, since it is executed natively.
>   

Except in big real mode (needs emulate_invalid_guest_state = 1).

> As for sti, I'm not sure. I see code for emulating sti, but in my testings,
> this code was never ever touched, under a number of different scenarios.
> Avi, can you clarify if sti can be in fact emulated, and under which
> circunstamces? 
>   

big real mode only.



-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/