From: Jim Houston <jim.houston@attbi.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>,
linux-kernel@vger.kernel.org,
high-res-timers-discourse@lists.sourceforge.net
Subject: Re: posix timers patch comments.
Date: Tue, 21 Jan 2003 18:33:31 -0500 [thread overview]
Message-ID: <3E2DD8CB.5B984772@attbi.com> (raw)
In-Reply-To: Pine.LNX.4.33L2.0301210952330.30777-100000@dragon.pdx.osdl.net
"Randy.Dunlap" wrote:
>
> Hi Jim,
>
> I'm reviewing both George's and your POSIX/high-res-timers patches.
> I might not send you comments every time that I come across something,
> and I might not cc lkml on every comment (unless you want me to).
>
> Anyway, here's a beginning.
>
> In functions get_eip(), check_expiry(), and run_posix_timers(),
> the <regs> parameter is a void *. Linus generally doesn't like
> void * parameters, so they should be avoided as much as possible,
> and I don't see any reason that <regs> in all of these can't be
> declared as <struct pt_regs *> instead of <void *>. Is there a
> good reason?
>
> BTW, when do expect to have any updated patches?
>
> Is your email address changing to @comcast.net?
Hi Randy,
It makes sense to include lkml in the discussion. It's an
interesting balancing act. If you openly criticize code that you
hope will be included in the kernel, you risk having your arguments
used as a reason for its rejection. If there is no visible discussion,
the patch will be perceived as un-reviewed.
The code that uses get_eip() is just debug. It may go away soon.
I was feeling lazy and didn't want to chase down the header files needed
to for "struct pt_regs". I just made the change and it was easy.
It turns out that pt_regs was already defined. I also found the
instruction_pointer() macro so I can get rid of the get_eip() function I
added. The timer code has to deal with timer overruns so it always
calculates the amount of time that a time interrupt is delayed. I'm logging
the EIP values which correspond to these long interrupt lockouts.
I'm not sure when I will do the next patch. I only have a few small
changes in the queue. I'm tempted to put it off a few days.
I'm hoping that Comcast won't make me change email addresses.
Jim Houston
next parent reply other threads:[~2003-01-21 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.33L2.0301210952330.30777-100000@dragon.pdx.osdl.net>
2003-01-21 23:33 ` Jim Houston [this message]
2003-01-22 0:51 ` posix timers patch comments Randy.Dunlap
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=3E2DD8CB.5B984772@attbi.com \
--to=jim.houston@attbi.com \
--cc=high-res-timers-discourse@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@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