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:	Sun, 05 Nov 2006 15:43:35 +1100
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Andi Kleen <ak@...e.de>
Cc:	Zachary Amsden <zach@...are.com>,
	Chris Wright <chrisw@...s-sol.org>,
	virtualization@...ts.osdl.org, linux-kernel@...r.kernel.org,
	akpm@...l.org
Subject: Re: [PATCH 1/7] paravirtualization: header and stubs
	for	paravirtualizing critical operations

On Fri, 2006-11-03 at 22:09 +0100, Andi Kleen wrote:
> > 
> > Sounds like desc.h got reordered.  Somewhere, there was a broken patch 
> > once that did this, I thought we fixed that.
> 
> I think I got Rusty's latest patches that I found in my mailbox.
> 
> I haven't looked at desc.h, but at least processor.h ordering was totally
> b0rken (e.g. #define __cpuid native_cpuid was after several uses). I fixed
> that to make at least the CONFIG_PARAVIRT not set case compile.
> 
> I can't see how this ever worked either.
> 
> Haven't attempted the CONFIG_PARAVIRT case which apparently needs more work
> (it is currently marked CONFIG_BROKEN) 
> 
> Can someone double check this is the correct patchkit?
> 
> ftp://ftp.frstfloor.org/pub/ak/x86_64/quilt/patches/paravirt*

Andi, the patches work against Andrew's tree, and he's merged them in
rc4-mm2.  There are a few warnings to clean up, but it seems basically
sound.

At this point I our think time is better spent on beating those patches
up, rather than going back and figuring out why they don't work in your
tree.

Sorry,
Rusty.


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

Powered by blists - more mailing lists