linux-kernel - Re: [PATCH 2/5] Paravirt cpu batching.patch

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] [day] [month] [year] [list]

Message-ID: <457F4BA1.4010700@vmware.com>
Date:	Tue, 12 Dec 2006 16:38:57 -0800
From:	Zachary Amsden <zach@...are.com>
To:	Chuck Ebbert <76306.1226@...puserve.com>
Cc:	Chris Wright <chrisw@...s-sol.org>, Andrew Morton <akpm@...l.org>,
	Virtualization Mailing List <virtualization@...ts.osdl.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andi Kleen <ak@....de>
Subject: Re: [PATCH 2/5] Paravirt cpu batching.patch

Chuck Ebbert wrote:
> In-Reply-To: <20061212225430.GC10475@...uoia.sous-sol.org>
>
> On Tue, 12 Dec 2006 14:54:30 -0800, Chros Wright wrote:
>
>   
>>> --- a/arch/i386/kernel/process.c    Tue Dec 12 13:50:50 2006 -0800
>>> +++ b/arch/i386/kernel/process.c    Tue Dec 12 13:50:53 2006 -0800
>>> @@ -665,6 +665,37 @@ struct task_struct fastcall * __switch_t
>>>     load_TLS(next, cpu);
>>>  
>>>     /*
>>> +    * Restore IOPL if needed.
>>> +    */
>>> +   if (unlikely(prev->iopl != next->iopl))
>>> +           set_iopl_mask(next->iopl);
>>>       
>> Small sidenote that this bit undoes a recent change from Chuck Ebbert, which
>> killed iopl_mask update via hypervisor.
>>     
>
> This whole thing needs a proper fix IMO.  I posted something a while back
> but Andi didn't like it, I guess.
>   

We can handle this one with an #ifdef CONFIG_PARAVIRT, though.

Zach
-
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/