From: Rusty Russell <rusty@rustcorp.com.au>
To: Zachary Amsden <zach@vmware.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: RFC: const_udelay in 018-delay functions patch
Date: Thu, 26 Oct 2006 09:01:02 +1000 [thread overview]
Message-ID: <1161817262.27354.3.camel@localhost.localdomain> (raw)
In-Reply-To: <453F027E.2020704@vmware.com>
On Tue, 2006-10-24 at 23:21 -0700, Zachary Amsden wrote:
> Rusty Russell wrote:
> > On Tue, 2006-10-24 at 22:11 -0700, Zachary Amsden wrote:
> >> +#if defined(CONFIG_PARAVIRT) && !defined(USE_REAL_IO)
> >> +#include <asm/paravirt.h>
> >> +#else
> >>
> >
> > USE_REAL_IO? Is this defined anywhere? Or just future-proofing?
> >
>
> It has to be used for SMP bootstrapping - IPI acceptance requires real
> time cross-processor delay, even in a VM
No, that's USE_REAL_TIME_DELAY: USE_REAL_IO is not currently defined
anywhere AFAICT.
> - and also can be added by a
> top-level define to kernel compiles for driver domains for Xen to give
> real time device delays.
Makes sense...
Rusty.
--
Help! Save Australia from the worst of the DMCA: http://linux.org.au/law
prev parent reply other threads:[~2006-10-25 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 5:11 RFC: const_udelay in 018-delay functions patch Zachary Amsden
2006-10-25 6:03 ` Rusty Russell
2006-10-25 6:21 ` Zachary Amsden
2006-10-25 23:01 ` Rusty Russell [this message]
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=1161817262.27354.3.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=chrisw@sous-sol.org \
--cc=virtualization@lists.osdl.org \
--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 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).