From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [GIT PULL] xen /proc/mtrr implementation
Date: Sun, 17 May 2009 22:02:21 -0700 [thread overview]
Message-ID: <4A10EBDD.7030304@goop.org> (raw)
In-Reply-To: <20090516112233.5cb085c8@jbarnes-g45>
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
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Ingo Molnar <mingo@elte.hu>,
the arch/x86 maintainers <x86@kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] xen /proc/mtrr implementation
Date: Sun, 17 May 2009 22:02:21 -0700 [thread overview]
Message-ID: <4A10EBDD.7030304@goop.org> (raw)
In-Reply-To: <20090516112233.5cb085c8@jbarnes-g45>
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
next prev parent reply other threads:[~2009-05-18 5:02 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 23:27 [GIT PULL] xen /proc/mtrr implementation Jeremy Fitzhardinge
2009-05-12 23:27 ` [PATCH 1/6] xen: set cpu_callout_mask to make mtrr work Jeremy Fitzhardinge
2009-05-12 23:27 ` [PATCH 2/6] xen mtrr: Use specific cpu_has_foo macros instead of generic cpu_has() Jeremy Fitzhardinge
2009-05-12 23:27 ` [PATCH 3/6] xen mtrr: Use generic_validate_add_page() Jeremy Fitzhardinge
2009-05-12 23:27 ` [PATCH 4/6] xen mtrr: Implement xen_get_free_region() Jeremy Fitzhardinge
2009-05-12 23:27 ` [PATCH 5/6] xen mtrr: Add xen_{get,set}_mtrr() implementations Jeremy Fitzhardinge
2009-05-12 23:27 ` [PATCH 6/6] xen mtrr: Kill some unnecessary includes Jeremy Fitzhardinge
2009-05-13 13:30 ` [GIT PULL] xen /proc/mtrr implementation Ingo Molnar
2009-05-13 13:30 ` Ingo Molnar
2009-05-13 14:39 ` Jeremy Fitzhardinge
2009-05-13 14:39 ` Jeremy Fitzhardinge
2009-05-15 18:27 ` Ingo Molnar
2009-05-15 18:27 ` Ingo Molnar
2009-05-15 20:09 ` Jeremy Fitzhardinge
2009-05-15 20:09 ` Jeremy Fitzhardinge
2009-05-15 23:26 ` Eric W. Biederman
2009-05-15 23:49 ` Jeremy Fitzhardinge
2009-05-15 23:49 ` Jeremy Fitzhardinge
2009-05-16 3:22 ` Jesse Barnes
2009-05-16 3:22 ` Jesse Barnes
2009-05-16 4:26 ` Eric W. Biederman
2009-05-16 18:22 ` Jesse Barnes
2009-05-16 18:22 ` Jesse Barnes
2009-05-18 5:02 ` Jeremy Fitzhardinge [this message]
2009-05-18 5:02 ` Jeremy Fitzhardinge
2009-05-18 4:57 ` Jeremy Fitzhardinge
2009-05-18 4:57 ` Jeremy Fitzhardinge
2009-05-18 8:59 ` Ingo Molnar
2009-05-18 8:59 ` Ingo Molnar
2009-05-18 13:17 ` [Xen-devel] " Jan Beulich
2009-05-18 17:51 ` Chris Wright
2009-05-18 18:07 ` Jeremy Fitzhardinge
2009-05-18 18:07 ` Jeremy Fitzhardinge
2009-05-19 9:59 ` Ingo Molnar
2009-05-19 9:59 ` Ingo Molnar
2009-05-19 10:22 ` [Xen-devel] " Jan Beulich
2009-05-19 10:22 ` Jan Beulich
2009-05-19 11:08 ` [Xen-devel] " Ingo Molnar
2009-05-19 11:08 ` Ingo Molnar
2009-05-19 12:04 ` [Xen-devel] " Gerd Hoffmann
2009-05-19 12:04 ` Gerd Hoffmann
2009-05-19 12:26 ` [Xen-devel] " Ingo Molnar
2009-05-19 12:26 ` Ingo Molnar
2009-05-19 12:32 ` [Xen-devel] " Alan Cox
2009-05-19 12:32 ` Alan Cox
2009-05-19 12:37 ` [Xen-devel] " Ingo Molnar
2009-05-19 12:37 ` Ingo Molnar
2009-05-19 13:21 ` [Xen-devel] " Gerd Hoffmann
2009-05-19 13:21 ` Gerd Hoffmann
2009-05-19 13:31 ` [Xen-devel] " Ingo Molnar
2009-05-19 13:31 ` Ingo Molnar
2009-05-19 13:51 ` [Xen-devel] " Gerd Hoffmann
2009-05-19 13:51 ` Gerd Hoffmann
2009-05-19 14:17 ` [Xen-devel] " Ingo Molnar
2009-05-19 14:17 ` Ingo Molnar
2009-05-19 14:55 ` [Xen-devel] " Gerd Hoffmann
2009-05-19 14:55 ` Gerd Hoffmann
2009-05-19 15:24 ` [Xen-devel] " Ingo Molnar
2009-05-19 15:24 ` Ingo Molnar
2009-05-20 8:01 ` [Xen-devel] " Gerd Hoffmann
2009-05-20 8:01 ` Gerd Hoffmann
2009-05-20 16:35 ` [Xen-devel] " Jeremy Fitzhardinge
2009-05-20 16:35 ` Jeremy Fitzhardinge
2009-05-20 16:12 ` Jeremy Fitzhardinge
2009-05-20 16:12 ` Jeremy Fitzhardinge
2009-05-20 8:16 ` Andi Kleen
2009-05-20 16:39 ` Jeremy Fitzhardinge
2009-05-20 16:39 ` Jeremy Fitzhardinge
2009-05-20 22:52 ` Andi Kleen
2009-05-20 22:49 ` Jeremy Fitzhardinge
2009-05-20 22:49 ` Jeremy Fitzhardinge
2009-05-20 23:03 ` H. Peter Anvin
2009-05-20 23:03 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A10EBDD.7030304@goop.org \
--to=jeremy@goop.org \
--cc=ebiederm@xmission.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.