From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
the arch/x86 maintainers <x86@kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Airlie <airlied@linux.ie>
Subject: Re: 2.6.30 Xen merge plan (what's in xen.git)
Date: Tue, 24 Mar 2009 16:28:18 -0700 [thread overview]
Message-ID: <49C96C92.1080604@zytor.com> (raw)
In-Reply-To: <49C96728.8070808@zytor.com>
H. Peter Anvin wrote:
>
> I was mostly objecting to the apic patches -- I'm okay with the latest
> version, as long as they aren't in hot code (I never got the time to
> measure it.)
>
Talking about performance measurements... do you have mmap-perf numbers
(paravirt on native vs non-paravirt) for the latest -tip kernel? I've
lost track of the numbers after all the changes.
-hpa
next prev parent reply other threads:[~2009-03-24 23:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 17:17 2.6.30 Xen merge plan (what's in xen.git) Jeremy Fitzhardinge
2009-03-24 17:36 ` [GIT PULL] xen.git 2.6.30: push2/x86/paravirt: preemption in lazy mmu updates Jeremy Fitzhardinge
2009-03-24 17:37 ` [GIT PULL] xen.git 2.6.30: core Xen updates Jeremy Fitzhardinge
2009-03-24 17:39 ` [GIT PULL] xen.git 2.6.30: usermode control interfaces Jeremy Fitzhardinge
2009-03-24 17:40 ` [GIT PULL] xen.git 2.6.30: xen dom0 core support Jeremy Fitzhardinge
2009-03-24 17:42 ` [GIT PULL] xen.git 2.6.30: xen dom0 apic changes Jeremy Fitzhardinge
2009-03-24 17:43 ` [GIT PULL] xen.git 2.6.30: xen dom0 PCI device support Jeremy Fitzhardinge
2009-03-24 17:48 ` 2.6.30 Xen merge plan (what's in xen.git) Ingo Molnar
2009-03-24 18:08 ` Jeremy Fitzhardinge
2009-03-24 23:05 ` H. Peter Anvin
2009-03-24 23:28 ` H. Peter Anvin [this message]
2009-03-25 5:49 ` Jeremy Fitzhardinge
2009-03-29 15:58 ` Jeremy Fitzhardinge
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=49C96C92.1080604@zytor.com \
--to=hpa@zytor.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox