linux-kernel - Re: 2.6.18-rc6-mm1: GPF loop on early boot

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]

Message-ID: <4505169C.3010507@goop.org>
Date:	Mon, 11 Sep 2006 00:56:12 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Andrew Morton <akpm@...l.org>, Andi Kleen <ak@...e.de>,
	Laurent Riffard <laurent.riffard@...e.fr>,
	Arjan van de Ven <arjan@...radead.org>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	Jeremy Fitzhardinge <jeremy@...source.com>
Subject: Re: 2.6.18-rc6-mm1: GPF loop on early boot

Ingo Molnar wrote:
> btw., what's the connection of %gs based PDA to Xen and 
> paravirtualization in general - %esp based current is just as 
> Xen-friendly, or am i wrong? I guess there must be some connection, 
> given that you are working on this ;)
>   

Yep.  The goal is to put the Xen VCPU structure into the PDA, so that it 
can be easily accessed.  At present, masking events (ie, cli), is 
something along the lines of

    xen_shared_info->vcpu[smp_processor_id()].mask = 1

which comes out to something like 20 bytes of code, and is probably too 
awkward to inline.  If the vcpu is in the PDA, it would come out to:

    movb $1, %gs:xen_vcpu_mask

which has the added benefit of not needing a register.

Even without modifying Xen to allow us to place the VCPU structure, 
putting a VCPU pointer into the PDA helps a lot:

    mov %gs:xen_vcpu, %eax
    movb $1, mask(%eax)

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