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:	Tue, 24 Apr 2007 00:50:06 +0200
From:	Andi Kleen <ak@...e.de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	virtualization@...ts.osdl.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/25] xen: Xen implementation for paravirt_ops

On Monday 23 April 2007 23:56:38 Jeremy Fitzhardinge wrote:
> Hi Andi,
> 
> It applies to 2.6.21-rc7 + your patches + the last batch of pv_ops
> patches 

I got most of those except for the broken sched_clock change.

> I posted. 

How much testing outside Jeremylabs has it gotten? Some beta
testing before merging would be good, otherwise we'll just have
a flood of fixes shortly when it is exposed to users.

> This patch generally restricts itself to Xen-specific parts of the tree,
> though it does make a few small changes elsewhere.

The general problem is that it is much more than just an architecture update.

> These patches include:
>  - some helper routines for allocating address space and walking pagetables

Needs review from mm people.

>  - Xen interface header files
>  - Core Xen implementation
>  - Efficient late-pinning/early-unpinning pagetable handling 

The number of new paravirt hooks makes me thing of renaming it to
everything_ops @|

>  - Virtualized time, including stolen time

Can you let it be reviewed by the time people? (Thomas, Ingo, John, Roman etc.)

>  - SMP support
>  - Preemption support
>  - Batched pagetable updates

>  - Xen console, based on hvc console
>  - Xenbus

That one would need to be reviewed first. It's so much code that I can't
do it all myself.

>  - Netfront, the paravirtualized network device

That one should go through the network device maintainer/netdev.

>  - Blockfront, the paravirtualized block device

And that needs a block device review and whoever maintains that (Jens?) 

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ