From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Pavel Machek <pavel@ucw.cz>, Alan <alan@lxorguk.ukuu.org.uk>,
Rusty Russell <rusty@rustcorp.com.au>, Andi Kleen <ak@muc.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 9/11] Panic delay fix
Date: Thu, 15 Feb 2007 15:50:25 -0800 [thread overview]
Message-ID: <45D4F1C1.7060103@goop.org> (raw)
In-Reply-To: <45D4F003.4030502@vmware.com>
Zachary Amsden wrote:
> So Rusty, Chris, Jeremy, any objections to killing udelay() and
> friends in paravirt-ops? It would simplify things a bit. The only
> thing we lose is a slightly faster boot time in the 100% emulated
> device case. I'm ok with losing that. Even the PIT fast paths don't
> use udelay, so I don't think we care for runtime performance at all.
Fine with me. That always seemed a bit warty to me.
J
next prev parent reply other threads:[~2007-02-15 23:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 3:53 [PATCH 9/11] Panic delay fix Zachary Amsden
2007-02-06 12:27 ` Andi Kleen
2007-02-06 21:59 ` Zachary Amsden
2007-02-07 12:35 ` Pavel Machek
2007-02-07 20:36 ` Rusty Russell
2007-02-07 22:23 ` Zachary Amsden
2007-02-08 14:43 ` Dmitry Torokhov
2007-02-08 21:26 ` Zachary Amsden
2007-02-08 21:37 ` Dmitry Torokhov
2007-02-14 12:26 ` Pavel Machek
2007-02-14 19:47 ` Zachary Amsden
2007-02-14 12:52 ` Alan
2007-02-14 20:04 ` Zachary Amsden
2007-02-14 21:34 ` Alan
2007-02-14 21:53 ` Zachary Amsden
2007-02-15 0:33 ` Alan
2007-02-15 10:17 ` Pavel Machek
2007-02-15 23:42 ` Zachary Amsden
2007-02-15 23:49 ` Pavel Machek
2007-02-15 23:50 ` Jeremy Fitzhardinge [this message]
2007-02-16 3:22 ` Rusty Russell
2007-02-07 14:58 ` Dmitry Torokhov
2007-02-07 22:31 ` Zachary Amsden
2007-02-08 8:24 ` Andi Kleen
2007-02-08 9:08 ` Zachary Amsden
2007-02-08 13:33 ` Andi Kleen
2007-02-08 14:41 ` Dmitry Torokhov
2007-02-14 12:49 ` Alan
2007-02-14 22:51 ` Rusty Russell
2007-02-15 0:28 ` Alan
2007-02-15 13:35 ` Dmitry Torokhov
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=45D4F1C1.7060103@goop.org \
--to=jeremy@goop.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rusty@rustcorp.com.au \
--cc=zach@vmware.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.