linux-kernel - Re: [PATCH v4 03/12] Add async PF initialization to PV guest.

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, 8 Jul 2010 16:24:43 +0300
From:	Gleb Natapov <gleb@...hat.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	kvm@...r.kernel.org, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, avi@...hat.com, mingo@...e.hu,
	tglx@...utronix.de, hpa@...or.com, riel@...hat.com,
	cl@...ux-foundation.org, mtosatti@...hat.com
Subject: Re: [PATCH v4 03/12] Add async PF initialization to PV guest.

On Wed, Jul 07, 2010 at 05:41:01PM +0200, Peter Zijlstra wrote:
> On Tue, 2010-07-06 at 19:24 +0300, Gleb Natapov wrote:
> > @@ -329,6 +330,8 @@ notrace static void __cpuinit start_secondary(void *unused)
> >         per_cpu(cpu_state, smp_processor_id()) = CPU_ONLINE;
> >         x86_platform.nmi_init();
> >  
> > +       kvm_guest_cpu_init();
> > +
> >         /* enable local interrupts */
> >         local_irq_enable(); 
> 
> CPU_STARTING hotplug notifier is too early?
> 
Actually no. I will move this call into cpu notifier.

> called from:
>    start_secondary()
>      smp_callin()
>        notify_cpu_starting() 
> 
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@...ck.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@...ck.org"> email@...ck.org </a>

--
			Gleb.
--
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/