From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>
Subject: Re: [PATCH 2/5] Paravirt cpu batching.patch
Date: Tue, 12 Dec 2006 16:30:44 -0800 [thread overview]
Message-ID: <457F49B4.5000801@goop.org> (raw)
In-Reply-To: <200612121853_MC3-1-D4D2-191A@compuserve.com>
Chuck Ebbert wrote:
> This whole thing needs a proper fix IMO. I posted something a while back
> but Andi didn't like it, I guess.
>
What's a quick summary of the issue again?
J
next prev parent reply other threads:[~2006-12-13 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 23:49 [PATCH 2/5] Paravirt cpu batching.patch Chuck Ebbert
2006-12-13 0:30 ` Jeremy Fitzhardinge [this message]
2006-12-13 0:38 ` Zachary Amsden
-- strict thread matches above, loose matches on Subject: below --
2006-12-12 22:34 Zachary Amsden
2006-12-12 22:54 ` Chris Wright
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=457F49B4.5000801@goop.org \
--to=jeremy@goop.org \
--cc=76306.1226@compuserve.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).