linux-kernel - Re: [PATCH] paravirt.h

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: <1156323394.2829.24.camel@laptopd505.fenrus.org>
Date:	Wed, 23 Aug 2006 10:56:34 +0200
From:	Arjan van de Ven <arjan@...radead.org>
To:	Zachary Amsden <zach@...are.com>
Cc:	Andi Kleen <ak@...e.de>, virtualization@...ts.osdl.org,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Andrew Morton <akpm@...l.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] paravirt.h

On Wed, 2006-08-23 at 01:44 -0700, Zachary Amsden wrote:
> Arjan van de Ven wrote:
> >> Since this code is so rather, um, custom, I was going to reimplement 
> >> stop_machine in the module.
> >>     
> >
> > that sounds like a big mistake. I assume you want your VMI module to be
> > part of mainline for one.
> >
> > And this is the sort of thing that if we want to support it, we better
> > support it inside the main kernel, eg provide an api to modules to use
> > it, rather than having each module hack their own....
> >   
> 
> Yes, after discussion with Rusty, it appears that beefing up 
> stop_machine_run is the right way to go.  And it has benefits for 
> non-paravirt code as well, such as allowing plug-in kprobes or oprofile 
> extension modules to be loaded without having to deal with a debug 
> exception or NMI during module load/unload.


it's more than stop_machine; If we do allow this I think this has to be
a register_virtualization() function that does the lot. In common code.


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