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: <4A10EBDD.7030304@goop.org>
Date:	Sun, 17 May 2009 22:02:21 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Ingo Molnar <mingo@...e.hu>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: [GIT PULL] xen /proc/mtrr implementation

Jesse Barnes wrote:
> This is really about what software Xen wants to support though.  You
> can say, "it would be easier for you to just support new software that
> doesn't use MTRRs," and you might be right, but supporting older stuff
> doesn't appear that difficult, and it sounds like something they want
> to do.
>   

My rough target is that you should be able to take a pvops-dom0 kernel 
and use it to replace the 2.6.18-xen (or other patched up -xen) kernel 
on an existing server installation without having to replace very much 
(or anything) else.  In practise that means making it work in something 
like RHEL 5 or SLES 10(?) environment.  That seems to be what at least 
some of my testers are doing.

Of course, most of the deployments will be with whatever new distro 
ships with the kernel.  But that doesn't mean we can write-off the old 
stuff.  (I think AKPM still tests current kernels on something like FC1 
or 2 to check for general kernel/distro regressions.)

    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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ